From owner-freebsd-current Sun Oct 27 13:56:43 2002 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 3A00837B401 for ; Sun, 27 Oct 2002 13:56:42 -0800 (PST) Received: from edgemaster.zombie.org (edgemaster.creighton.edu [147.134.112.68]) by mx1.FreeBSD.org (Postfix) with ESMTP id BBF5F43E42 for ; Sun, 27 Oct 2002 13:56:41 -0800 (PST) (envelope-from smkelly@zombie.org) Received: by edgemaster.zombie.org (Postfix, from userid 1001) id CEE4B41467; Sun, 27 Oct 2002 15:56:40 -0600 (CST) Date: Sun, 27 Oct 2002 15:56:40 -0600 From: Sean Kelly To: current@freebsd.org Subject: fsck / and remount failure Message-ID: <20021027215639.GA660@edgemaster.zombie.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.5.1i 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 I just suffered a kernel panic and upon reboot, I noticed that the root filesystem isn't able to be remounted read/write after the fsck: Mounting root from ufs:/dev/ad1s1a WARNING: / was not properly dismounted ... Starting file system checks: /dev/ad1s1a: INCORRECT BLOCK COUNT I=42806 (4 should be 0) (CORRECTED) /dev/ad1s1a: UNREF FILE I=42804 OWNER=smkelly MODE=100600 /dev/ad1s1a: SIZE=8756 MTIME=Oct 27 13:48 2002 (CLEARED) /dev/ad1s1a: UNREF FILE I=42805 OWNER=smkelly MODE=100600 /dev/ad1s1a: SIZE=8630 MTIME=Oct 27 13:48 2002 (CLEARED) /dev/ad1s1a: UNREF FILE I=42806 OWNER=root MODE=100444 /dev/ad1s1a: SIZE=0 MTIME=Oct 27 15:50 2002 (CLEARED) /dev/ad1s1a: FREE BLK COUNT(S) WRONG IN SUPERBLK (SALVAGED) /dev/ad1s1a: SUMMARY INFORMATION BAD (SALVAGED) /dev/ad1s1a: BLK(S) MISSING IN BIT MAPS (SALVAGED) /dev/ad1s1a: 2231 files, 83743 used, 168240 free (424 frags, 20977 blocks, 0.2% fragmentation) /dev/ad1s1e: DEFER FOR BACKGROUND CHECKING /dev/ad1s1f: DEFER FOR BACKGROUND CHECKING /dev/ad0s1c: DEFER FOR BACKGROUND CHECKING mount: /dev/ad1s1a: Device busy mount: /dev/ad1s1a: Device busy Is this a known problem? It is rather annoying to have to come up for fscks, then reboot again to get a read/write root filesystem. Am I doing something wrong? And yes, I know my root filesystem is excessively large. -- Sean Kelly | PGP KeyID: 77042C7B smkelly@zombie.org | http://www.zombie.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message