Date: Sun, 11 Mar 2012 12:11:12 -0700 From: Adrian Chadd <adrian@freebsd.org> To: Alex Keda <admin@lissyara.su> Cc: freebsd-current@freebsd.org Subject: Re: SU+J and fsck problem ? Message-ID: <CAJ-Vmokd5crBQNRakEr==bE7mqLuyz5dXpcZFW5-N0_yXkk6Qw@mail.gmail.com> In-Reply-To: <4F5C5FFE.3080007@lissyara.su> References: <loom.20120310T105525-894@post.gmane.org> <4F5C5FFE.3080007@lissyara.su>
next in thread | previous in thread | raw e-mail | index | archive | help
Please file a PR and put as much debugging output as you can. I haven't had it fail for me on any of my test machines that panic _very frequently_. But I only hvae a single disk with minimal IO, I haven't had it crash doing lots of ongoing server style iO. adrian On 11 March 2012 00:19, Alex Keda <admin@lissyara.su> wrote: > On 10.03.2012 14:01, jb wrote: >> >> Hi, >> >> FB9.0-RELEASE; no updates or recompilation. >> >> In multi-user mode: >> $ mount >> /dev/ada0s2a on / (ufs, local, journaled soft-updates) >> The fs was in normal state (no known problem, clean shutdown), >> >> Booted by choice in single-user mode. >> >> # mount >> /dev/ada0s2a on / (ufs, local, read-only) >> >> # fsck -F >> ** /dev/ada0s2a >> >> USE JOURNAL? [yn] y >> >> ** SU+J recovering /dev/ada0s2a >> ** Reading 33554432 byte journal from inode 4. >> >> RECOVER? [yn] y >> >> ** ... >> ** Processing journal entries. >> >> WRITE CHANGES? [yn] y >> >> ** 208 journal records in 13312 bytes for 50% utilization >> ** Freed 0 inodes (0 dirs) 6 blocks, and 0 frags. >> >> ***** FILE SYSTEM MARKED CLEAN **** >> >> # fsck -F >> ** /dev/ada0s2a >> >> USE JOURNAL? [yn] n >> >> ** Skipping journal, falling through to full fsck >> >> ** Last Mounted on / >> ** Root file system >> ** Phase 1 - Check Blocks and Sizes >> INCORRECT BLOCK COUNT I=3D114700 (8 should be 0) >> CORRECT? [yn] n >> >> INCORRECT BLOCK COUNT I=3D196081 (32 should be 8) >> CORRECT? [yn] n >> >> INCORRECT BLOCK COUNT I=3D474381 (32 should be 8) >> CORRECT? [yn] n >> >> ** Phase 2 - Check Pathnames >> ** Phase 3 - Check Connectivity >> ** Phase 4 - Check Reference Counts >> ** Phase 5 - Check Cyl groups >> FREE BLOCK COUNTS(S) WRONG IN SUPERBLK >> SALVAGE? [yn] n >> >> SUMMARY INFORMATION BAD >> SALVAGE? [yn] n >> >> BLK(S) MISSING IN BIT MAPS >> SALVAGE? [yn] n >> >> 266075 files, 939314 used, 1896628 free (2724 frags, 236738 blocks, 0.1% >> fragmentation) >> >> ***** FILE SYSTEM MARKED DIRTY ***** >> >> ***** FILE SYSTEM WAS MODIFIED ***** >> >> ***** PLEASE RERUN FSCK ***** >> >> # fsck -F >> ** /dev/ada0s2a >> >> USE JOURNAL? [yn] y >> >> ** SU+J recovering /dev/ada0s2a >> Journal timestamp does not match fs mount time >> ** Skipping journal, falling through to full fsck >> >> ** Last Mounted on / >> ** Root file system >> ** Phase 1 - Check Blocks and Sizes >> INCORRECT BLOCK COUNT I=3D114700 (8 should be 0) >> CORRECT? [yn] y >> >> INCORRECT BLOCK COUNT I=3D196081 (32 should be 8) >> CORRECT? [yn] y >> >> INCORRECT BLOCK COUNT I=3D474381 (32 should be 8) >> CORRECT? [yn] y >> >> ** Phase 2 - Check Pathnames >> ** Phase 3 - Check Connectivity >> ** Phase 4 - Check Reference Counts >> ** Phase 5 - Check Cyl groups >> FREE BLOCK COUNTS(S) WRONG IN SUPERBLK >> SALVAGE? [yn] y >> >> SUMMARY INFORMATION BAD >> SALVAGE? [yn] y >> >> BLK(S) MISSING IN BIT MAPS >> SALVAGE? [yn] y >> >> 266075 files, 939314 used, 1896629 free (2725 frags, 236738 blocks, 0.1% >> fragmentation) >> >> ***** FILE SYSTEM MARKED CLEAN ***** >> >> ***** FILE SYSTEM WAS MODIFIED ***** >> >> # >> >> Summary: >> 1. # fsck -F =A0 =A0 =A0 =A0 =A0## recovery done with J >> >> 2. # fsck -F =A0 =A0 =A0 =A0 =A0## no recovery; fs marked dirty; time st= amp modified >> =A0 =A0 =A0Why during this step there were incorrect block counts report= ed if >> the fs >> =A0 =A0 =A0was recovered and marked clean in step 1 ? >> =A0 =A0 =A0Despite the fact that choice of no recovery was made, the fs = was >> marked >> =A0 =A0 =A0dirty (based on false assumption above ?, and time stamp ?) >> >> 3. # fsck -F =A0 =A0 =A0 =A0 =A0## forced skipped Journal >> =A0 =A0 =A0Same question as in step 2, >> =A0 =A0 =A0based on which it accepted the choice of recovery ... >> =A0 =A0 =A0Note: >> =A0 =A0 =A0after step 2: >> =A0 =A0 =A0 =A01896628 free and 2724 frags in >> =A0 =A0 =A0 =A0266075 files, 939314 used, 1896620 free (2724 frags, 2367= 38 blocks, >> ... >> =A0 =A0 =A0after step 3: >> =A0 =A0 =A0 =A01896629 free and 2725 frags in >> =A0 =A0 =A0 =A0266075 files, 939314 used, 1896629 free (2725 frags, 2367= 38 blocks, >> ... >> >> Questions: >> - is the fsck working properly with SU+J fs ? >> =A0 Note: >> =A0 fsck(8) >> =A0 =A0 -F ... >> =A0 =A0 -B ... >> =A0 =A0 =A0 =A0It is recommended that you perform foreground fsck on you= r systems >> =A0 =A0 =A0 =A0periodically and whenever you encounter file-system-relat= ed panics. >> - would the fs as after step 1, and steps 1-3 or 1,3 be considered >> =A0 "recovered": >> =A0 - structurally ? >> =A0 - identical ?, does it matter ? >> =A0 - integrally ? >> >> Any comments before I file a PR# ? >> jb > > SUJ very strange work. > it's can say - "filesystem OK", but, after full boot system crash - file > system have errors... > I disable it on all production hosts, use only on desktop. > If I manually run fsck after crash and unexpected reboot - fsck _always_ > find errors, unhandled by SUJ > > _______________________________________________ > freebsd-current@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-current > To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.org= "
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CAJ-Vmokd5crBQNRakEr==bE7mqLuyz5dXpcZFW5-N0_yXkk6Qw>