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 [EMAIL PROTECTED] | http://www.zombie.org To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
