On Fri, 10 Sep 2004 09:32:53 -0500, Dave Kleikamp <[EMAIL PROTECTED]> wrote:
> On Tue, 2004-09-07 at 05:27, Ash wrote:
> > Hi
> > I was running a kind of crash test on JFS in which
> > I do a large number of filesystem operations with several threads and
> > crash the machine with a direct poweroff.
> >
> > On reboot, I ran fsck.jfs firstly with default options simply to replay the log.
> > This succeeded without reporting and problems and said that the
> > filesystem was marked clean.
> > <snip>
> > **Phase 0 - Replay Journal Log
> > Filesystem is clean.
> > <snip>
> >
> > Next, I ran fsck.jfs with "-f" option to verify if there are any
> > inconsistencies in the filesystem.
> > I got a few errors saying something like
> > <snip>
> > **Phase 4 - Report Problems
> > File system object FF106504 is linked as: /d15/run_23-10000109
> > cannot repair the data format error(s) in this file.
> > cannot repair FF106504. Will release.
>
> These errors should not be here. Replaying the journal is supposed to
> make sure that the metadata is consistent after a power-off. I can tell
> that you are using a recent version of jfsutils, but are you using a
> recent kernel?
I'm using Kernel 2.6.7 on Redhat 8.0.
And yes, this does get reproduced. Here's what I have from a recent
crash test cycle.
Output on running fsck.jfs with default parameters after rebooting
from the crash:
/sbin/fsck.jfs version 1.1.6, 28-Apr-2004
processing started: 9/10/2004 21.28.37
Using default parameter: -p
The current device is: /dev/cciss/c0d0p8
Block size in bytes: 4096
Filesystem size in blocks: 4678923
**Phase 0 - Replay Journal Log
Filesystem is clean.
Next run of fsck.jfs (this time with force checking option "-f")
immediately after the above run:
/sbin/fsck.jfs version 1.1.6, 28-Apr-2004
processing started: 9/10/2004 21.28.38
The current device is: /dev/cciss/c0d0p8
Block size in bytes: 4096
Filesystem size in blocks: 4678923
**Phase 0 - Replay Journal Log
**Phase 1 - Check Blocks, Files/Directories, and Directory Entries
**Phase 2 - Count links
Incorrect link counts have been detected. Will correct.
**Phase 3 - Duplicate Block Rescan and Directory Connectedness
**Phase 4 - Report Problems
File system object DF139270 is linked as: /d19/run_68-10000063
cannot repair the data format error(s) in this directory.
cannot repair DF139270. Will release.
File system object DF213000 is linked as: /d19
**Phase 5 - Check Connectivity
**Phase 6 - Perform Approved Corrections
8 files reconnected to /lost+found/.
**Phase 7 - Rebuild File/Directory Allocation Maps
**Phase 8 - Rebuild Disk Allocation Maps
18715692 kilobytes total disk space.
1640 kilobytes in 657 directories.
97547 kilobytes in 1270 user files.
0 kilobytes in extended attributes
41505 kilobytes reserved for system use.
18578280 kilobytes are available for use.
Filesystem is clean.
Now, the third run of fsck.jfs (with "-f" option again) :
/sbin/fsck.jfs version 1.1.6, 28-Apr-2004
processing started: 9/10/2004 21.28.45
The current device is: /dev/cciss/c0d0p8
Block size in bytes: 4096
Filesystem size in blocks: 4678923
**Phase 0 - Replay Journal Log
**Phase 1 - Check Blocks, Files/Directories, and Directory Entries
**Phase 2 - Count links
**Phase 3 - Duplicate Block Rescan and Directory Connectedness
**Phase 4 - Report Problems
File system object DF213000 is linked as: /d19
Errors detected in Directory Index Table. Will Fix.
**Phase 5 - Check Connectivity
**Phase 6 - Perform Approved Corrections
**Phase 7 - Rebuild File/Directory Allocation Maps
**Phase 8 - Rebuild Disk Allocation Maps
18715692 kilobytes total disk space.
1636 kilobytes in 657 directories.
97547 kilobytes in 1270 user files.
0 kilobytes in extended attributes
41497 kilobytes reserved for system use.
18578284 kilobytes are available for use.
Filesystem is clean.
And finally the last run, which seems to report no errors now:
fsck.jfs version 1.1.6, 28-Apr-2004
processing started: 9/13/2004 14.23.52
The current device is: /dev/cciss/c0d0p8
Block size in bytes: 4096
Filesystem size in blocks: 4678923
**Phase 0 - Replay Journal Log
**Phase 1 - Check Blocks, Files/Directories, and Directory Entries
**Phase 2 - Count links
**Phase 3 - Duplicate Block Rescan and Directory Connectedness
**Phase 4 - Report Problems
**Phase 5 - Check Connectivity
**Phase 6 - Perform Approved Corrections
**Phase 7 - Rebuild File/Directory Allocation Maps
**Phase 8 - Rebuild Disk Allocation Maps
18715692 kilobytes total disk space.
1636 kilobytes in 657 directories.
97547 kilobytes in 1270 user files.
0 kilobytes in extended attributes
41497 kilobytes reserved for system use.
18578284 kilobytes are available for use.
Filesystem is clean.
Please let me know if there's any more info you need.
Thanks,
Ash
_______________________________________________
Jfs-discussion mailing list
[EMAIL PROTECTED]
http://www-124.ibm.com/developerworks/oss/mailman/listinfo/jfs-discussion
