Date: Sun, 27 Oct 2002 17:17:44 -0500 (EST) From: Robert Watson <rwatson@freebsd.org> To: Sean Kelly <smkelly@zombie.org> Cc: current@freebsd.org Subject: Re: fsck / and remount failure Message-ID: <Pine.NEB.3.96L.1021027171542.22105B-100000@fledge.watson.org> In-Reply-To: <20021027215639.GA660@edgemaster.zombie.org>
next in thread | previous in thread | raw e-mail | index | archive | help
Are you using UFS1 extended attributes on that box? I suspect there might be a bug involving the open flags passed to extended attribute backing vnodes such that a remount is refused because there are existing vnodes opened writable. I.e., the extended attribute backing files are opened FREAD|FWRITE, and since the file system is mounted read-only, remount refuses to upgrade to a rw mount until they are closed. My guess is that, in fact, this should be permitted, or we should re-open the backing files on a remount. I'd like to get this bug fixed, but it is another reason to recommend UFS2 over UFS1. Robert N M Watson FreeBSD Core Team, TrustedBSD Projects robert@fledge.watson.org Network Associates Laboratories On Sun, 27 Oct 2002, Sean Kelly wrote: > 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 > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?Pine.NEB.3.96L.1021027171542.22105B-100000>