Date: Sun, 11 Mar 2012 21:28:26 GMT From: jb <jb.1234abcd@gmail.com> To: freebsd-gnats-submit@FreeBSD.org Subject: misc/165950: SU+J and fsck problem Message-ID: <201203112128.q2BLSQJJ053318@red.freebsd.org> Resent-Message-ID: <201203112130.q2BLUDHS075343@freefall.freebsd.org>
next in thread | raw e-mail | index | archive | help
>Number: 165950
>Category: misc
>Synopsis: SU+J and fsck problem
>Confidential: no
>Severity: serious
>Priority: medium
>Responsible: freebsd-bugs
>State: open
>Quarter:
>Keywords:
>Date-Required:
>Class: sw-bug
>Submitter-Id: current-users
>Arrival-Date: Sun Mar 11 21:30:13 UTC 2012
>Closed-Date:
>Last-Modified:
>Originator: jb
>Release: FreeBSD 9.0-RELEASE #0
>Organization:
>Environment:
FreeBSD localhost.localdomain 9.0-RELEASE FreeBSD 9.0-RELEASE #0: Tue Jan 3 07:15:25 UTC 2012 root@obrian.cse.buffalo.edu:/usr/obj/usr/src/sys/GENERIC i386
>Description:
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=114700 (8 should be 0)
CORRECT? [yn] n
INCORRECT BLOCK COUNT I=196081 (32 should be 8)
CORRECT? [yn] n
INCORRECT BLOCK COUNT I=474381 (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=114700 (8 should be 0)
CORRECT? [yn] y
INCORRECT BLOCK COUNT I=196081 (32 should be 8)
CORRECT? [yn] y
INCORRECT BLOCK COUNT I=474381 (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 ## recovery done with J
2. # fsck -F ## no recovery; fs marked dirty; time stamp modified
Why during this step there were incorrect block counts reported if the fs
was recovered and marked clean in step 1 ?
Despite the fact that choice of no recovery was made, the fs was marked
dirty (based on false assumption above ?, and time stamp ?)
3. # fsck -F ## forced skipped Journal
Same question as in step 2,
based on which it accepted the choice of recovery ...
Note:
after step 2:
1896628 free and 2724 frags in
266075 files, 939314 used, 1896620 free (2724 frags, 236738 blocks, ...
after step 3:
1896629 free and 2725 frags in
266075 files, 939314 used, 1896629 free (2725 frags, 236738 blocks, ...
Questions:
- is the fsck working properly with SU+J fs ?
Note:
fsck(8)
-F ...
-B ...
It is recommended that you perform foreground fsck on your systems
periodically and whenever you encounter file-system-related panics.
>How-To-Repeat:
I re-run the same tests today (2 days later).
Summary:
1. # fsck -F ## recovery done with J (as in step 1 previously)
2. # fsck -F ## no errors (like those in step 2 previously);
fs marked clean
** /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
Phase 2 thru 5
***** FILE SYSTEM MARKED CLEAN *****
>Fix:
>Release-Note:
>Audit-Trail:
>Unformatted:
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?201203112128.q2BLSQJJ053318>