Date: Sun, 24 Apr 2005 11:25:31 -0700 From: Kris Kennaway <kris@obsecurity.org> To: Palle Girgensohn <girgen@pingpong.net> Cc: stable@freebsd.org Subject: Re: background_fsck=no does not work? Message-ID: <20050424182531.GA33485@xor.obsecurity.org> In-Reply-To: <DD8197BD35BCC63A18AF62CB@palle.girgensohn.se> References: <DD8197BD35BCC63A18AF62CB@palle.girgensohn.se>
next in thread | previous in thread | raw e-mail | index | archive | help
[-- Attachment #1 --] 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? no Running fsck on a mounted filesystem will do this unless you use background fsck, because the filesystem is in use. Kris [-- Attachment #2 --] -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.0 (FreeBSD) iD8DBQFCa+SbWry0BWjoQKURAlcPAKD0FD9n9pJYpCCGYTsj1dPjvzwMhwCgjA/c fLOyO1TyrKAyndU8QZ7u1Fs= =3mIq -----END PGP SIGNATURE-----
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20050424182531.GA33485>