From owner-freebsd-current Mon Jan 27 10:56:15 2003 Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 5603F37B401 for ; Mon, 27 Jan 2003 10:56:14 -0800 (PST) Received: from mgate.uni-hannover.de (mgate.uni-hannover.de [130.75.2.3]) by mx1.FreeBSD.org (Postfix) with ESMTP id A357843F3F for ; Mon, 27 Jan 2003 10:56:12 -0800 (PST) (envelope-from gerrit@pmp.uni-hannover.de) Received: from www.pmp.uni-hannover.de by mgate.uni-hannover.de with LocalSMTP (PP) with ESMTP; Mon, 27 Jan 2003 18:41:37 +0100 Received: by www.pmp.uni-hannover.de (Postfix, from userid 846) id 32FCF121; Mon, 27 Jan 2003 18:41:27 +0100 (CET) Date: Mon, 27 Jan 2003 18:41:27 +0100 From: Gerrit =?iso-8859-1?Q?K=FChn?= To: current@freebsd.org Subject: Does bg fsck have problems with large filesystems? Message-ID: <20030127174127.GD71664@pmp.uni-hannover.de> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.4i X-Operating-System: FreeBSD Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Hi all, I've just installed my first 5.0-rel system and did some "torture-testing". When resetting the machine to test the backgrounded fsck I experienced the following problem: All filesystems came back quickly and bg fsck worked fine, except for one. I had created a large (>50GB) /export filesystem on with fsck reproducively hang. I also couldn't reboot the system cleanly anymore, because of those fsck processes not going away. Finally, I commented out /export from /etc/fstab and run fsck manually in fg mode after the rest of the system had been checked cleanly. There were a few errors, and after that the check finished and marked the system as clean. However, mounting the clean system took several seconds and gave me this message from the kernel: FFS_SNAPSHOT_MOUNT: old format snapshot inode 4 Well, whatever... :) Nevertheless everything is working fine now, again. I havn't checked yet, but will this happen every time my systems reboots without unmounting the filesystems cleanly? Is anything wrong with filesystems that large, or could I have done anything else that causes this strange behaviour? cu Gerrit -- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message