Hello,
It seems that every time fsck.jfs creates a lost+found directory to recover
files and directories it produces an invalid file system object... I've now
seen this 4 times so it appears to be 100% reproducible, at least in the case
where the root directory was corrupt and needed to be recreated.
Here's an example...
fsck.jfs -f -v /dev/loop0
fsck.jfs version 1.1.14, 06-Apr-2009
processing started: 8/5/2010 17.40.18
The current device is: /dev/loop0
Open(...READ/WRITE EXCLUSIVE...) returned rc = 0
Primary superblock is valid.
The type of file system for the device is JFS.
Block size in bytes: 4096
Filesystem size in blocks: 1692095488
**Phase 0 - Replay Journal Log
LOGREDO: Log already redone!
logredo returned rc = 0
**Phase 1 - Check Blocks, Files/Directories, and Directory Entries
Root directory has a corrupt tree.
Initialized tree created for root directory.
The root directory has an invalid data format. Will correct.
**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
Superblock marked dirty because repairs are about to be written.
No \lost+found directory found in the filesystem.
Directory inode 7485024 has been reconnected to /lost+found/.
Directory inode 7477042 has been reconnected to /lost+found/.
.
.
Directory inode 1021058 has been reconnected to /lost+found/.
Directory inode 1010272 has been reconnected to /lost+found/.
Directory inode 994442 has been reconnected to /lost+found/.
Directory inode 994435 has been reconnected to /lost+found/.
.
.
Directory inode 41161 has been reconnected to /lost+found/.
Directory inode 12352 has been reconnected to /lost+found/.
Directory inode 4096 has been reconnected to /lost+found/.
File inode 2817 has been reconnected to /lost+found/.
548 directories reconnected to /lost+found/.
1 file reconnected to /lost+found/.
**Phase 7 - Rebuild File/Directory Allocation Maps
**Phase 8 - Rebuild Disk Allocation Maps
Filesystem Summary:
Blocks in use for inodes: 790564
Inode count: 6324512
File count: 5082304
Directory count: 468747
Block count: 1692095488
Free block count: 392981888
6768381952 kilobytes total disk space.
2699049 kilobytes in 468747 directories.
5192294548 kilobytes in 5082304 user files.
0 kilobytes in extended attributes
0 kilobytes in access control lists
6858901 kilobytes reserved for system use.
1571927552 kilobytes are available for use.
Filesystem is clean.
All observed inconsistencies have been repaired.
Filesystem has been marked clean.
**** Filesystem was modified. ****
processing terminated: 8/5/2010 23:32:58 with return code: 0 exit code: 1.
fsck.jfs -n -v /dev/loop0
fsck.jfs version 1.1.14, 06-Apr-2009
processing started: 8/6/2010 9.55.4
The current device is: /dev/loop0
Open(...READONLY...) returned rc = 0
Primary superblock is valid.
The type of file system for the device is JFS.
Block size in bytes: 4096
Filesystem size in blocks: 1692095488
**Phase 1 - Check Blocks, Files/Directories, and Directory Entries
Bad directory cookie found.
**Phase 2 - Count links
**Phase 3 - Duplicate Block Rescan and Directory Connectedness
**Phase 4 - Report Problems
File system object DF2816 is linked as: /lost+found
Errors detected in Directory Index Table.
**Phase 5 - Check Connectivity
**Phase 6 - Perform Approved Corrections
**Phase 7 - Verify File/Directory Allocation Maps
**Phase 8 - Verify Disk Allocation Maps
Filesystem Summary:
Blocks in use for inodes: 790564
Inode count: 6324512
File count: 5082304
Directory count: 468747
Block count: 1692095488
Free block count: 392981888
6768381952 kilobytes total disk space.
2699117 kilobytes in 468747 directories.
5192294548 kilobytes in 5082304 user files.
0 kilobytes in extended attributes
0 kilobytes in access control lists
6858969 kilobytes reserved for system use.
1571927552 kilobytes are available for use.
File system checked READ ONLY.
ERRORS HAVE BEEN DETECTED. Run fsck with the -f parameter to repair.
Filesystem is dirty.
Filesystem is dirty but is marked clean. In its present state,
the results of accessing /dev/loop0 (except by this utility) are undefined.
processing terminated: 8/6/2010 13:58:22 with return code: 0 exit code: 4.
Running fsck.jfs again fixes this problem.
Let me know if any additional information would be useful.
Tim------------------------------------------------------------------------------
This SF.net email is sponsored by
Make an app they can't live without
Enter the BlackBerry Developer Challenge
http://p.sf.net/sfu/RIM-dev2dev
_______________________________________________
Jfs-discussion mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/jfs-discussion
