Date: Fri, 17 Mar 2006 04:58:50 +0000 From: Chris <chrcoluk@gmail.com> To: RW <list-freebsd-2004@morbius.sent.com> Cc: freebsd-questions@freebsd.org Subject: Re: some questions about fsck, loader.conf Message-ID: <3aaaa3a0603162058y7c3b6f0fm@mail.gmail.com> In-Reply-To: <200603170030.51491.list-freebsd-2004@morbius.sent.com> References: <3aaaa3a0603142307l5f89dd36n@mail.gmail.com> <20060315073127.GD48583@dan.emsphone.com> <200603170030.51491.list-freebsd-2004@morbius.sent.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On 17/03/06, RW <list-freebsd-2004@morbius.sent.com> wrote: > On Wednesday 15 March 2006 07:31, Dan Nelson wrote: > > > > In rc.conf I have enabled fsck_y_enable="YES" to allow unattended > > > fsck fixes after improper shutdown but I have noticed there are some > > > problems remaining as shown by a read only fsck. Does the above > > > switch not fix all problems or is it the case the fsck bootup script > > > only does partial tests? > > > > A read-only fsck of a mounted filesystem will never come back clean, > > since the filesystem's mounted :) > > I think the question was: why did it find an error, when fsck had run at > boot? > > Were you running background checking? And had it completed? Also there was a > bug where partitions fixed with background checking still showed a minor > error when unmounted and checked - check the list for details. > > > good question, the reasoning for me doing the online fsck check was I suspect the hd itself is faulty from other factors such as very slow performance and recent crashes, I have no local access to the machine and I am not sure if the datacentre has been fully honest with me. Background checking is on assuming thats the default. However I then did some read only checks on another box which has never had an improper shutdown and that also showed errors which I will paste here. ** Phase 5 - Check Cyl groups 53 files, 36 used, 126803 free (43 frags, 15845 blocks, 0.0% fragmentation) ** /dev/ad2s1f (NO WRITE) ** Last Mounted on /usr ** Phase 1 - Check Blocks and Sizes ** Phase 2 - Check Pathnames ** Phase 3 - Check Connectivity ** Phase 4 - Check Reference Counts UNREF FILE I=4663374 OWNER=root MODE=100644 SIZE=0 MTIME=Mar 17 00:31 2006 CLEAR? no ZERO LENGTH DIR I=5087752 OWNER=root MODE=40755 SIZE=0 MTIME=Feb 2 01:47 2006 CLEAR? no UNREF FILE I=5092692 OWNER=root MODE=100755 SIZE=10036 MTIME=Dec 22 23:19 2005 CLEAR? no UNREF FILE I=5140575 OWNER=root MODE=100755 SIZE=389582 MTIME=Jan 13 13:05 2006 CLEAR? no UNREF FILE I=5206424 OWNER=root MODE=100555 SIZE=15071 MTIME=Dec 22 23:17 2005 CLEAR? no UNREF FILE I=5206613 OWNER=root MODE=100555 SIZE=107521 MTIME=Dec 22 23:17 2005 CLEAR? no UNREF FILE I=5206633 OWNER=root MODE=100555 SIZE=29059 MTIME=Dec 22 23:17 2005 CLEAR? no UNREF FILE I=5206638 OWNER=root MODE=100555 SIZE=25480 MTIME=Dec 22 23:17 2005 CLEAR? no UNREF FILE I=5206668 OWNER=root MODE=100555 SIZE=7189 MTIME=Dec 22 23:17 2005 CLEAR? no UNREF FILE I=5206671 OWNER=root MODE=100555 SIZE=13884 MTIME=Dec 22 23:17 2005 CLEAR? no UNREF FILE I=5252342 OWNER=frogees MODE=100644 SIZE=6 MTIME=Jan 30 22:36 2006 CLEAR? no UNREF FILE I=5325324 OWNER=root MODE=100555 SIZE=1209532 MTIME=Dec 22 23:17 2005 CLEAR? no UNREF FILE I=5347550 OWNER=allriped MODE=100644 SIZE=6 MTIME=Feb 9 09:51 2006 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 ALLOCATED FRAGS 21549328-21549351 MARKED FREE ALLOCATED FRAG 21552423 MARKED FREE ALLOCATED FRAGS 21560112-21560115 MARKED FREE 285913 files, 39238077 used, 16172222 free (78934 frags, 2011661 blocks, 0.1% fragmentation) and results from last read.write check are clean. Chris
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?3aaaa3a0603162058y7c3b6f0fm>