Hi! on a 5.4-prerelease machine (dell 2850 dual cpu, running amd64), I have this in rc.conf: fsck_y_enable="YES" background_fsck="NO" Still, I'm not certain that fsck is really run at startup. At least, running fsck on in multiuser reveals information like below, but perhaps that is normal for an active file system? I'm having stability problems with this machine (it crashes sporadically) and I suspect it might have something to do with problems in the file system. Could this be true, or is the below stuff completely normal? Thanks, Palle # fsck (on a running multiuser system, just to check) .... ** /dev/amrd0s2g (NO WRITE) ** Last Mounted on /usr/local ** Phase 1 - Check Blocks and Sizes ** Phase 2 - Check Pathnames ** Phase 3 - Check Connectivity ** Phase 4 - Check Reference Counts ** Phase 5 - Check Cyl groups FREE BLK COUNT(S) WRONG IN SUPERBLK SALVAGE? no SUMMARY INFORMATION BAD SALVAGE? no BLK(S) MISSING IN BIT MAPS SALVAGE? no 205437 files, 4275062 used, 802012 free (109716 frags, 86537 blocks, 2.2% fragmentation) ** /dev/amrd0s2e (NO WRITE) ** Last Mounted on /var ** Phase 1 - Check Blocks and Sizes INCORRECT BLOCK COUNT I=400865 (25408 should be 25376) CORRECT? no ** Phase 2 - Check Pathnames ** Phase 3 - Check Connectivity ** Phase 4 - Check Reference Counts UNREF FILE I=402688 OWNER=root MODE=100644 SIZE=242572 MTIME=Apr 24 09:07 2005 CLEAR? no UNREF FILE I=494615 OWNER=root MODE=140666 SIZE=0 MTIME=Apr 24 05:44 2005 CLEAR? no ** Phase 5 - Check Cyl groups FREE BLK COUNT(S) WRONG IN SUPERBLK SALVAGE? no SUMMARY INFORMATION BAD SALVAGE? no BLK(S) MISSING IN BIT MAPS SALVAGE? no 9066 files, 257785 used, 1771238 free (12446 frags, 219849 blocks, 0.6% fragmentation) ** /dev/amrd0s2h (NO WRITE) ** Last Mounted on /var/spool/imap ** Phase 1 - Check Blocks and Sizes ** Phase 2 - Check Pathnames ** Phase 3 - Check Connectivity ** Phase 4 - Check Reference Counts ** Phase 5 - Check Cyl groups 234836 files, 2100748 used, 19389487 free (17959 frags, 2421441 blocks, 0.1% fragmentation)
Palle Girgensohn wrote:> Hi! > > on a 5.4-prerelease machine (dell 2850 dual cpu, running amd64), I have > this in rc.conf: > > fsck_y_enable="YES" > background_fsck="NO" > > > Still, I'm not certain that fsck is really run at startup.Are you expecting a fsck to be run at every startup, regardless of whether the filesystems are dirty? If so, that is not what these options do.> At least, > running fsck on in multiuser reveals information like below, but perhaps > that is normal for an active file system?Yes, because of the caching effect of the VM layer, the filesystem will not always be clean. Softupdates (hopefully) means that it will be consistent and recoverable, but what you're seeing here is normal and expected. Running foreground-fsck on a mounted filesystem has limited value, though.> > I'm having stability problems with this machine (it crashes > sporadically) and I suspect it might have something to do with problems > in the file system. Could this be true, or is the below stuff completely > normal?You'll need to enable DDB and KDB and post the information from your crashes. Scott
On Sun, Apr 24, 2005 at 01:45:47PM +0200, Palle Girgensohn wrote:> Hi! > > on a 5.4-prerelease machine (dell 2850 dual cpu, running amd64), I have > this in rc.conf: > > fsck_y_enable="YES" > background_fsck="NO" > > > Still, I'm not certain that fsck is really run at startup. At least, > running fsck on in multiuser reveals information like below, but perhaps > that is normal for an active file system? > > I'm having stability problems with this machine (it crashes sporadically) > and I suspect it might have something to do with problems in the file > system. Could this be true, or is the below stuff completely normal? > > Thanks, > Palle > > # fsck (on a running multiuser system, just to check) > .... > > ** /dev/amrd0s2g (NO WRITE) > ** Last Mounted on /usr/local > ** Phase 1 - Check Blocks and Sizes > ** Phase 2 - Check Pathnames > ** Phase 3 - Check Connectivity > ** Phase 4 - Check Reference Counts > ** Phase 5 - Check Cyl groups > FREE BLK COUNT(S) WRONG IN SUPERBLK > SALVAGE? no > > SUMMARY INFORMATION BAD > SALVAGE? no > > BLK(S) MISSING IN BIT MAPS > SALVAGE? noRunning fsck on a mounted filesystem will do this unless you use background fsck, because the filesystem is in use. Kris -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 187 bytes Desc: not available Url : http://lists.freebsd.org/pipermail/freebsd-stable/attachments/20050424/c7699e56/attachment.bin