Sorry, I sent the wrong jfs_fsck output in my last email.. That was for the
READ-ONLY pass I did *before* trying to make repairs. The output from the
read-only check is interesting because it shows the Disk Allocation Maps errors
which don't get reported in the read-write repair.
Here's the output for the first read-write repair run:
Log of /sbin/jfs_fsck -f -y -v /dev/md10
Mon Jul 16 09:54:41 2012
/sbin/jfs_fsck version 1.1.15.patched.2011.03.07, 04-Mar-2011
processing started: 7/16/2012 9:54:41
The current device is: /dev/md10
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: 4756914448
**Phase 0 - Replay Journal Log
LOGREDO: Log already redone!
logredo returned rc = 0
**Phase 1 - Check Blocks, Files/Directories, and Directory Entries
Duplicate reference to 1 block(s) beginning at offset 4248749952 found in file
system object FF4086925.
Inode F4086925 has references to cross linked blocks.
Duplicate reference to 1 block(s) beginning at offset 4248749984 found in file
system object FF4086925.
Inode F4086925 has references to cross linked blocks.
Duplicate reference to 1 block(s) beginning at offset 4248750016 found in file
system object FF4086925.
Inode F4086925 has references to cross linked blocks.
Duplicate reference to 1 block(s) beginning at offset 4248750048 found in file
system object FF4086925.
Inode F4086925 has references to cross linked blocks.
Duplicate reference to 1 block(s) beginning at offset 4248750080 found in file
system object FF4086925.
Inode F4086925 has references to cross linked blocks.
Duplicate reference to 1 block(s) beginning at offset 4248750112 found in file
system object FF4086925.
Inode F4086925 has references to cross linked blocks.
Duplicate reference to 1 block(s) beginning at offset 4248750144 found in file
system object FF4086925.
Inode F4086925 has references to cross linked blocks.
Duplicate reference to 1 block(s) beginning at offset 4248750208 found in file
system object FF4086925.
Inode F4086925 has references to cross linked blocks.
File system object FF4086925 has corrupt data (39).
File system object DF5541508 has a node with an invalid self field.
Invalid data (43) detected in file system object FF5541523.
**Phase 2 - Count links
Inode F5541497 has incorrect link count.
Incorrect link counts have been detected. Will correct.
**Phase 3 - Duplicate Block Rescan and Directory Connectedness
Duplicate reference to 1 block(s) beginning at offset 4248750208 found in file
system object FF1079633.
Inode F1079633 has references to cross linked blocks.
Duplicate reference to 1 block(s) beginning at offset 4248749952 found in file
system object FF4086486.
Duplicate reference to 1 block(s) beginning at offset 4248749984 found in file
system object FF4086486.
Duplicate reference to 1 block(s) beginning at offset 4248750016 found in file
system object FF4086486.
Duplicate reference to 1 block(s) beginning at offset 4248750048 found in file
system object FF4086486.
Duplicate reference to 1 block(s) beginning at offset 4248750080 found in file
system object FF4086486.
Duplicate reference to 1 block(s) beginning at offset 4248750112 found in file
system object FF4086486.
Duplicate reference to 1 block(s) beginning at offset 4248750144 found in file
system object FF4086486.
Inode F4086486 has references to cross linked blocks.
**Phase 4 - Report Problems
File system object FF1079633 is linked as:
/20100104/a0/a0b0217de71d1a0217f60615/03b/bzff21a0b0217de71d1a0217f60615000000000003b66e201001040747130000000240116.bzff
File claims cross linked block(s).
cannot repair FF1079633. Will release.
File system object FF4086486 is linked as:
/20120706/57/57a462ace0e313d135780014/h11/bzmf2157a462ace0e313d1357800140000000000000000201207061131500000000240116.bzmf
File claims cross linked block(s).
cannot repair FF4086486. Will release.
File system object FF4086925 is linked as:
/20120713/08/08886904e6bbb5a731290014/h10/bzmf2108886904e6bbb5a7312900140000000000000000201207131024090000000240116.bzmf
File claims cross linked block(s).
cannot repair FF4086925. Will release.
File system object DF5541508 is linked as:
/20120715/0c/0c2c8067b5548758367c0b10/h21
cannot repair the data format error(s) in this directory.
cannot repair DF5541508. Will release.
Fileset object FF5541523: No paths found.
cannot repair the data format error(s) in this file.
cannot repair FF5541523. Will release.
**Phase 5 - Check Connectivity
No paths were found for inode F5541509.
No paths were found for inode F5541515.
**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 F1079508 entry reference to inode F1079633 removed.
Storage allocated to inode F1079633 has been cleared.
Directory inode F2709628 entry reference to inode F4086486 removed.
Storage allocated to inode F4086486 has been cleared.
Directory inode F4086922 entry reference to inode F4086925 removed.
Storage allocated to inode F4086925 has been cleared.
Link count for inode F5541497 has been adjusted/corrected.
Directory inode F5541497 entry reference to inode F5541508 removed.
Storage allocated to inode F5541508 has been cleared.
Storage allocated to inode F5541523 has been cleared.
File inode 5541515 has been reconnected to /lost+found/.
File inode 5541509 has been reconnected to /lost+found/.
2 files reconnected to /lost+found/.
**Phase 7 - Rebuild File/Directory Allocation Maps
**Phase 8 - Rebuild Disk Allocation Maps
Filesystem Summary:
Blocks in use for inodes: 2512268
Inode count: 20098144
File count: 11226661
Directory count: 2153660
Block count: 4756914448
Free block count: 561778084
19027657792 kilobytes total disk space.
6911782 kilobytes in 2153660 directories.
16769589090 kilobytes in 11226661 user files.
0 kilobytes in extended attributes
0 kilobytes in access control lists
17868148 kilobytes reserved for system use.
2247112336 kilobytes are available for use.
Filesystem is dirty.
**** Filesystem was modified. ****
processing terminated: 7/16/2012 21:10:06 with return code: 0 exit code: 4.
/sbin/jfs_fsck died with exit status 4
Mon Jul 16 21:10:13 2012
----------------
Tim
On Jul 18, 2012, at 3:29 PM, Tim Nufire <[email protected]> wrote:
> Dave,
>
> Thanks for the response.
>
> The errors in the second run were not the same as the first run but the file
> with cross linked blocks in the second run was in the same directory
> (/20120713/08/08886904e6bbb5a731290014/h10) as a file with similar problems
> the first time.
>
> Here's the full output from the first run showing many more errors:
>
> Log of /sbin/jfs_fsck -n -v /dev/md10
> Sun Jul 15 18:36:09 2012
>
> /sbin/jfs_fsck version 1.1.15.patched.2011.03.07, 04-Mar-2011
> processing started: 7/15/2012 18:36:09
>
> FSCK Device /dev/md10 is currently mounted READ ONLY.
> The current device is: /dev/md10
> 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: 4756914448
> **Phase 1 - Check Blocks, Files/Directories, and Directory Entries
> Duplicate reference to 1 block(s) beginning at offset 4248749952 found in
> file system object FF4086925.
> Inode F4086925 has references to cross linked blocks.
> Duplicate reference to 1 block(s) beginning at offset 4248749984 found in
> file system object FF4086925.
> Inode F4086925 has references to cross linked blocks.
> Duplicate reference to 1 block(s) beginning at offset 4248750016 found in
> file system object FF4086925.
> Inode F4086925 has references to cross linked blocks.
> Duplicate reference to 1 block(s) beginning at offset 4248750048 found in
> file system object FF4086925.
> Inode F4086925 has references to cross linked blocks.
> Duplicate reference to 1 block(s) beginning at offset 4248750080 found in
> file system object FF4086925.
> Inode F4086925 has references to cross linked blocks.
> Duplicate reference to 1 block(s) beginning at offset 4248750112 found in
> file system object FF4086925.
> Inode F4086925 has references to cross linked blocks.
> Duplicate reference to 1 block(s) beginning at offset 4248750144 found in
> file system object FF4086925.
> Inode F4086925 has references to cross linked blocks.
> Duplicate reference to 1 block(s) beginning at offset 4248750208 found in
> file system object FF4086925.
> Inode F4086925 has references to cross linked blocks.
> File system object FF4086925 has corrupt data (39).
> File system object DF5541508 has a node with an invalid self field.
> Invalid data (43) detected in file system object FF5541523.
> **Phase 2 - Count links
> Inode F5541497 has incorrect link count.
> Incorrect link counts detected in the aggregate.
> **Phase 3 - Duplicate Block Rescan and Directory Connectedness
> Duplicate reference to 1 block(s) beginning at offset 4248750208 found in
> file system object FF1079633.
> Inode F1079633 has references to cross linked blocks.
> Duplicate reference to 1 block(s) beginning at offset 4248749952 found in
> file system object FF4086486.
> Duplicate reference to 1 block(s) beginning at offset 4248749984 found in
> file system object FF4086486.
> Duplicate reference to 1 block(s) beginning at offset 4248750016 found in
> file system object FF4086486.
> Duplicate reference to 1 block(s) beginning at offset 4248750048 found in
> file system object FF4086486.
> Duplicate reference to 1 block(s) beginning at offset 4248750080 found in
> file system object FF4086486.
> Duplicate reference to 1 block(s) beginning at offset 4248750112 found in
> file system object FF4086486.
> Duplicate reference to 1 block(s) beginning at offset 4248750144 found in
> file system object FF4086486.
> Inode F4086486 has references to cross linked blocks.
> Inode F5541509 is not connected to the root directory tree.
> Inode F5541515 is not connected to the root directory tree.
> Inode F5541523 is not connected to the root directory tree.
> **Phase 4 - Report Problems
> File system object FF1079633 is linked as:
> /20100104/a0/a0b0217de71d1a0217f60615/03b/bzff21a0b0217de71d1a0217f60615000000000003b66e201001040747130000000240116.bzff
> File claims cross linked block(s).
> cannot repair FF1079633.
> File system object FF4086486 is linked as:
> /20120706/57/57a462ace0e313d135780014/h11/bzmf2157a462ace0e313d1357800140000000000000000201207061131500000000240116.bzmf
> File claims cross linked block(s).
> cannot repair FF4086486.
> File system object FF4086925 is linked as:
> /20120713/08/08886904e6bbb5a731290014/h10/bzmf2108886904e6bbb5a7312900140000000000000000201207131024090000000240116.bzmf
> File claims cross linked block(s).
> cannot repair FF4086925.
> File system object DF5541508 is linked as:
> /20120715/0c/0c2c8067b5548758367c0b10/h21
> cannot repair the data format error(s) in this directory.
> cannot repair DF5541508.
> Fileset object FF5541523: No paths found.
> cannot repair the data format error(s) in this file.
> cannot repair FF5541523.
> **Phase 5 - Check Connectivity
> **Phase 6 - Perform Approved Corrections
> **Phase 7 - Verify File/Directory Allocation Maps
> **Phase 8 - Verify Disk Allocation Maps
> 104 consecutive blocks observed available but pmap (509262, 26, 8) indicates
> they are allocated.
> 13 consecutive blocks observed available but pmap (509262, 38, 6) indicates
> they are allocated.
> 232 consecutive blocks observed available but pmap (509262, 45, 19) indicates
> they are allocated.
> Incorrect number free detected in dmap 509262.
> Incorrect internal (0) value detected in DM page 509262.
> Incorrect internal (1) value detected in DM page 509262.
> Incorrect internal (6) value detected in DM page 509262.
> Incorrect internal (7) value detected in DM page 509262.
> Incorrect internal (8) value detected in DM page 509262.
> Incorrect internal (27) value detected in DM page 509262.
> Incorrect internal (28) value detected in DM page 509262.
> Incorrect internal (30) value detected in DM page 509262.
> Incorrect internal (32) value detected in DM page 509262.
> Incorrect internal (33) value detected in DM page 509262.
> Incorrect internal (34) value detected in DM page 509262.
> Incorrect leaf (111) value detected in DM page 509262.
> Incorrect leaf (112) value detected in DM page 509262.
> Incorrect leaf (113) value detected in DM page 509262.
> Incorrect leaf (114) value detected in DM page 509262.
> Incorrect leaf (123) value detected in DM page 509262.
> Incorrect leaf (130) value detected in DM page 509262.
> Incorrect leaf (131) value detected in DM page 509262.
> Incorrect leaf (133) value detected in DM page 509262.
> Incorrect leaf (137) value detected in DM page 509262.
> 99 consecutive blocks observed available but pmap (509408, 141, 27) indicates
> they are allocated.
> 90 consecutive blocks observed available but pmap (509408, 145, 1) indicates
> they are allocated.
> 35 consecutive blocks observed available but pmap (509408, 147, 29) indicates
> they are allocated.
> 256 consecutive blocks observed available but pmap (509408, 197, 15)
> indicates they are allocated.
> Incorrect number free detected in dmap 509408.
> Incorrect internal (0) value detected in DM page 509408.
> Incorrect internal (3) value detected in DM page 509408.
> Incorrect internal (4) value detected in DM page 509408.
> Incorrect internal (13) value detected in DM page 509408.
> Incorrect internal (14) value detected in DM page 509408.
> Incorrect internal (17) value detected in DM page 509408.
> Incorrect internal (56) value detected in DM page 509408.
> Incorrect internal (57) value detected in DM page 509408.
> Incorrect internal (58) value detected in DM page 509408.
> Incorrect internal (70) value detected in DM page 509408.
> Incorrect internal (71) value detected in DM page 509408.
> Incorrect internal (72) value detected in DM page 509408.
> Incorrect leaf (226) value detected in DM page 509408.
> Incorrect leaf (227) value detected in DM page 509408.
> Incorrect leaf (229) value detected in DM page 509408.
> Incorrect leaf (230) value detected in DM page 509408.
> Incorrect leaf (231) value detected in DM page 509408.
> Incorrect leaf (232) value detected in DM page 509408.
> Incorrect leaf (233) value detected in DM page 509408.
> Incorrect leaf (282) value detected in DM page 509408.
> Incorrect leaf (283) value detected in DM page 509408.
> Incorrect leaf (285) value detected in DM page 509408.
> Incorrect leaf (289) value detected in DM page 509408.
> Incorrect leaf (290) value detected in DM page 509408.
> 187 consecutive blocks observed available but pmap (509409, 45, 16) indicates
> they are allocated.
> Incorrect number free detected in dmap 509409.
> Incorrect internal (0) value detected in DM page 509409.
> Incorrect internal (1) value detected in DM page 509409.
> Incorrect internal (7) value detected in DM page 509409.
> Incorrect internal (8) value detected in DM page 509409.
> Incorrect internal (32) value detected in DM page 509409.
> Incorrect internal (33) value detected in DM page 509409.
> Incorrect leaf (130) value detected in DM page 509409.
> Incorrect leaf (131) value detected in DM page 509409.
> Incorrect leaf (133) value detected in DM page 509409.
> Incorrect leaf (135) value detected in DM page 509409.
> Incorrect leaf (136) value detected in DM page 509409.
> 1 consecutive blocks observed available but pmap (509413, 238, 10) indicates
> they are allocated.
> 49 consecutive blocks observed available but pmap (509413, 238, 12) indicates
> they are allocated.
> Incorrect number free detected in dmap 509413.
> Incorrect internal (0) value detected in DM page 509413.
> Incorrect internal (4) value detected in DM page 509413.
> Incorrect internal (19) value detected in DM page 509413.
> Incorrect internal (80) value detected in DM page 509413.
> Incorrect leaf (323) value detected in DM page 509413.
> Incorrect leaf (324) value detected in DM page 509413.
> 42 consecutive blocks observed available but pmap (509786, 15, 13) indicates
> they are allocated.
> 1 consecutive blocks observed available but pmap (509786, 24, 24) indicates
> they are allocated.
> 1 consecutive blocks observed available but pmap (509786, 33, 30) indicates
> they are allocated.
> 2 consecutive blocks observed available but pmap (509786, 59, 6) indicates
> they are allocated.
> 1 consecutive blocks observed available but pmap (509786, 67, 10) indicates
> they are allocated.
> 1 consecutive blocks observed available but pmap (509786, 102, 16) indicates
> they are allocated.
> 1 consecutive blocks observed available but pmap (509786, 128, 30) indicates
> they are allocated.
> 1 consecutive blocks observed available but pmap (509786, 131, 14) indicates
> they are allocated.
> 256 consecutive blocks observed available but pmap (509786, 139, 15)
> indicates they are allocated.
> 1 consecutive blocks observed available but pmap (509786, 163, 15) indicates
> they are allocated.
> 1 consecutive blocks observed available but pmap (509786, 184, 24) indicates
> they are allocated.
> 258 consecutive blocks observed available but pmap (509786, 184, 27)
> indicates they are allocated.
> 3 consecutive blocks observed available but pmap (509786, 200, 29) indicates
> they are allocated.
> 258 consecutive blocks observed available but pmap (509786, 225, 20)
> indicates they are allocated.
> 2 consecutive blocks observed available but pmap (509786, 241, 22) indicates
> they are allocated.
> Incorrect number free detected in dmap 509786.
> Incorrect internal (0) value detected in DM page 509786.
> Incorrect internal (1) value detected in DM page 509786.
> Incorrect internal (2) value detected in DM page 509786.
> Incorrect internal (3) value detected in DM page 509786.
> Incorrect internal (4) value detected in DM page 509786.
> Incorrect internal (5) value detected in DM page 509786.
> Incorrect internal (6) value detected in DM page 509786.
> Incorrect internal (7) value detected in DM page 509786.
> Incorrect internal (8) value detected in DM page 509786.
> Incorrect internal (9) value detected in DM page 509786.
> Incorrect internal (11) value detected in DM page 509786.
> Incorrect internal (13) value detected in DM page 509786.
> Incorrect internal (14) value detected in DM page 509786.
> Incorrect internal (15) value detected in DM page 509786.
> Incorrect internal (16) value detected in DM page 509786.
> Incorrect internal (17) value detected in DM page 509786.
> Incorrect internal (19) value detected in DM page 509786.
> Incorrect internal (20) value detected in DM page 509786.
> Incorrect internal (24) value detected in DM page 509786.
> Incorrect internal (25) value detected in DM page 509786.
> Incorrect internal (27) value detected in DM page 509786.
> Incorrect internal (29) value detected in DM page 509786.
> Incorrect internal (35) value detected in DM page 509786.
> Incorrect internal (37) value detected in DM page 509786.
> Incorrect internal (46) value detected in DM page 509786.
> Incorrect internal (53) value detected in DM page 509786.
> Incorrect internal (55) value detected in DM page 509786.
> Incorrect internal (56) value detected in DM page 509786.
> Incorrect internal (57) value detected in DM page 509786.
> Incorrect internal (61) value detected in DM page 509786.
> Incorrect internal (67) value detected in DM page 509786.
> Incorrect internal (68) value detected in DM page 509786.
> Incorrect internal (69) value detected in DM page 509786.
> Incorrect internal (71) value detected in DM page 509786.
> Incorrect internal (77) value detected in DM page 509786.
> Incorrect internal (78) value detected in DM page 509786.
> Incorrect internal (79) value detected in DM page 509786.
> Incorrect internal (81) value detected in DM page 509786.
> Incorrect leaf (100) value detected in DM page 509786.
> Incorrect leaf (101) value detected in DM page 509786.
> Incorrect leaf (109) value detected in DM page 509786.
> Incorrect leaf (118) value detected in DM page 509786.
> Incorrect leaf (144) value detected in DM page 509786.
> Incorrect leaf (152) value detected in DM page 509786.
> Incorrect leaf (187) value detected in DM page 509786.
> Incorrect leaf (213) value detected in DM page 509786.
> Incorrect leaf (216) value detected in DM page 509786.
> Incorrect leaf (224) value detected in DM page 509786.
> Incorrect leaf (225) value detected in DM page 509786.
> Incorrect leaf (229) value detected in DM page 509786.
> Incorrect leaf (231) value detected in DM page 509786.
> Incorrect leaf (232) value detected in DM page 509786.
> Incorrect leaf (248) value detected in DM page 509786.
> Incorrect leaf (269) value detected in DM page 509786.
> Incorrect leaf (270) value detected in DM page 509786.
> Incorrect leaf (271) value detected in DM page 509786.
> Incorrect leaf (273) value detected in DM page 509786.
> Incorrect leaf (277) value detected in DM page 509786.
> Incorrect leaf (285) value detected in DM page 509786.
> Incorrect leaf (310) value detected in DM page 509786.
> Incorrect leaf (311) value detected in DM page 509786.
> Incorrect leaf (313) value detected in DM page 509786.
> Incorrect leaf (317) value detected in DM page 509786.
> Incorrect leaf (318) value detected in DM page 509786.
> Incorrect leaf (326) value detected in DM page 509786.
> 5 consecutive blocks observed available but pmap (509787, 2, 10) indicates
> they are allocated.
> 2 consecutive blocks observed available but pmap (509787, 25, 15) indicates
> they are allocated.
> 2 consecutive blocks observed available but pmap (509787, 33, 17) indicates
> they are allocated.
> 6 consecutive blocks observed available but pmap (509787, 70, 3) indicates
> they are allocated.
> 1 consecutive blocks observed available but pmap (509787, 75, 14) indicates
> they are allocated.
> 3 consecutive blocks observed available but pmap (509787, 91, 16) indicates
> they are allocated.
> 7 consecutive blocks observed available but pmap (509787, 101, 24) indicates
> they are allocated.
> 4 consecutive blocks observed available but pmap (509787, 102, 0) indicates
> they are allocated.
> 1 consecutive blocks observed available but pmap (509787, 102, 5) indicates
> they are allocated.
> 257 consecutive blocks observed available but pmap (509787, 111, 14)
> indicates they are allocated.
> 1 consecutive blocks observed available but pmap (509787, 128, 25) indicates
> they are allocated.
> 2 consecutive blocks observed available but pmap (509787, 140, 15) indicates
> they are allocated.
> 1 consecutive blocks observed available but pmap (509787, 142, 23) indicates
> they are allocated.
> 1 consecutive blocks observed available but pmap (509787, 142, 28) indicates
> they are allocated.
> 1 consecutive blocks observed available but pmap (509787, 160, 6) indicates
> they are allocated.
> 436 consecutive blocks observed available but pmap (509787, 168, 20)
> indicates they are allocated.
> Incorrect number free detected in dmap 509787.
> Incorrect internal (0) value detected in DM page 509787.
> Incorrect internal (1) value detected in DM page 509787.
> Incorrect internal (2) value detected in DM page 509787.
> Incorrect internal (3) value detected in DM page 509787.
> Incorrect internal (5) value detected in DM page 509787.
> Incorrect internal (6) value detected in DM page 509787.
> Incorrect internal (7) value detected in DM page 509787.
> Incorrect internal (9) value detected in DM page 509787.
> Incorrect internal (10) value detected in DM page 509787.
> Incorrect internal (11) value detected in DM page 509787.
> Incorrect internal (12) value detected in DM page 509787.
> Incorrect internal (13) value detected in DM page 509787.
> Incorrect internal (15) value detected in DM page 509787.
> Incorrect internal (16) value detected in DM page 509787.
> Incorrect internal (21) value detected in DM page 509787.
> Incorrect internal (27) value detected in DM page 509787.
> Incorrect internal (29) value detected in DM page 509787.
> Incorrect internal (38) value detected in DM page 509787.
> Incorrect internal (39) value detected in DM page 509787.
> Incorrect internal (43) value detected in DM page 509787.
> Incorrect internal (46) value detected in DM page 509787.
> Incorrect internal (48) value detected in DM page 509787.
> Incorrect internal (49) value detected in DM page 509787.
> Incorrect internal (50) value detected in DM page 509787.
> Incorrect internal (53) value detected in DM page 509787.
> Incorrect internal (56) value detected in DM page 509787.
> Incorrect internal (61) value detected in DM page 509787.
> Incorrect internal (63) value detected in DM page 509787.
> Incorrect internal (64) value detected in DM page 509787.
> Incorrect internal (65) value detected in DM page 509787.
> Incorrect internal (66) value detected in DM page 509787.
> Incorrect leaf (87) value detected in DM page 509787.
> Incorrect leaf (110) value detected in DM page 509787.
> Incorrect leaf (118) value detected in DM page 509787.
> Incorrect leaf (155) value detected in DM page 509787.
> Incorrect leaf (160) value detected in DM page 509787.
> Incorrect leaf (176) value detected in DM page 509787.
> Incorrect leaf (186) value detected in DM page 509787.
> Incorrect leaf (187) value detected in DM page 509787.
> Incorrect leaf (196) value detected in DM page 509787.
> Incorrect leaf (197) value detected in DM page 509787.
> Incorrect leaf (201) value detected in DM page 509787.
> Incorrect leaf (203) value detected in DM page 509787.
> Incorrect leaf (204) value detected in DM page 509787.
> Incorrect leaf (213) value detected in DM page 509787.
> Incorrect leaf (225) value detected in DM page 509787.
> Incorrect leaf (227) value detected in DM page 509787.
> Incorrect leaf (245) value detected in DM page 509787.
> Incorrect leaf (253) value detected in DM page 509787.
> Incorrect leaf (254) value detected in DM page 509787.
> Incorrect leaf (255) value detected in DM page 509787.
> Incorrect leaf (257) value detected in DM page 509787.
> Incorrect leaf (261) value detected in DM page 509787.
> Incorrect leaf (265) value detected in DM page 509787.
> Incorrect leaf (267) value detected in DM page 509787.
> Incorrect internal (2) value detected in L0 page 497.
> Incorrect internal (10) value detected in L0 page 497.
> Incorrect internal (12) value detected in L0 page 497.
> Incorrect internal (41) value detected in L0 page 497.
> Incorrect internal (51) value detected in L0 page 497.
> Incorrect internal (168) value detected in L0 page 497.
> Incorrect internal (205) value detected in L0 page 497.
> Incorrect internal (206) value detected in L0 page 497.
> Incorrect internal (299) value detected in L0 page 497.
> Incorrect leaf (675) value detected in L0 page 497.
> Incorrect leaf (821) value detected in L0 page 497.
> Incorrect leaf (822) value detected in L0 page 497.
> Incorrect leaf (826) value detected in L0 page 497.
> Incorrect leaf (1199) value detected in L0 page 497.
> Incorrect leaf (1200) value detected in L0 page 497.
> 256 consecutive blocks observed allocated but pmap (518645, 158, 28)
> indicates they are available.
> 2 consecutive blocks observed allocated but pmap (518645, 167, 29) indicates
> they are available.
> 223 consecutive blocks observed allocated but pmap (518645, 219, 14)
> indicates they are available.
> 143 consecutive blocks observed allocated but pmap (518645, 226, 14)
> indicates they are available.
> 14 consecutive blocks observed allocated but pmap (518645, 234, 0) indicates
> they are available.
> 13 consecutive blocks observed allocated but pmap (518645, 242, 14) indicates
> they are available.
> 3 consecutive blocks observed allocated but pmap (518645, 243, 3) indicates
> they are available.
> Incorrect number free detected in dmap 518645.
> Incorrect internal (0) value detected in DM page 518645.
> Incorrect internal (3) value detected in DM page 518645.
> Incorrect internal (4) value detected in DM page 518645.
> Incorrect internal (14) value detected in DM page 518645.
> Incorrect internal (15) value detected in DM page 518645.
> Incorrect internal (18) value detected in DM page 518645.
> Incorrect internal (19) value detected in DM page 518645.
> Incorrect internal (20) value detected in DM page 518645.
> Incorrect internal (60) value detected in DM page 518645.
> Incorrect internal (61) value detected in DM page 518645.
> Incorrect internal (62) value detected in DM page 518645.
> Incorrect internal (75) value detected in DM page 518645.
> Incorrect internal (76) value detected in DM page 518645.
> Incorrect internal (77) value detected in DM page 518645.
> Incorrect internal (78) value detected in DM page 518645.
> Incorrect internal (79) value detected in DM page 518645.
> Incorrect internal (81) value detected in DM page 518645.
> Incorrect leaf (243) value detected in DM page 518645.
> Incorrect leaf (244) value detected in DM page 518645.
> Incorrect leaf (245) value detected in DM page 518645.
> Incorrect leaf (249) value detected in DM page 518645.
> Incorrect leaf (251) value detected in DM page 518645.
> Incorrect leaf (252) value detected in DM page 518645.
> Incorrect leaf (304) value detected in DM page 518645.
> Incorrect leaf (305) value detected in DM page 518645.
> Incorrect leaf (309) value detected in DM page 518645.
> Incorrect leaf (311) value detected in DM page 518645.
> Incorrect leaf (312) value detected in DM page 518645.
> Incorrect leaf (313) value detected in DM page 518645.
> Incorrect leaf (315) value detected in DM page 518645.
> Incorrect leaf (319) value detected in DM page 518645.
> Incorrect leaf (327) value detected in DM page 518645.
> Incorrect leaf (328) value detected in DM page 518645.
> Incorrect leaf (842) value detected in L0 page 506.
> Incorrect number of free blocks detected in Block Map Control Page.
> Incorrect number of free blocks in AG 62 detected in Block Map Control Page.
> Incorrect number of free blocks in AG 63 detected in Block Map Control Page.
> Descrepancies detected between observed block allocations and pmaps.
> Inconsistencies detected in leaf values (DM).
> Inconsistencies detected in internal values (DM).
> Incorrect data detected in pages (DM).
> Inconsistencies detected in leaf values (L0).
> Inconsistencies detected in internal values (L0).
> Discrepancies detected in the Block Map Control Page AG free count list.
> Incorrect data detected in the Block Map Control Page.
> Incorrect data detected in disk allocation structures.
> Incorrect data detected in disk allocation control structures.
> Filesystem Summary:
> Blocks in use for inodes: 2512268
> Inode count: 20098144
> File count: 11226665
> Directory count: 2153660
> Block count: 4756914448
> Free block count: 561771864
> 19027657792 kilobytes total disk space.
> 6911782 kilobytes in 2153660 directories.
> 16769625592 kilobytes in 11226665 user files.
> 0 kilobytes in extended attributes
> 0 kilobytes in access control lists
> 17856526 kilobytes reserved for system use.
> 2247087456 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/md10 (except by this utility) are undefined.
> processing terminated: 7/16/2012 5:34:58 with return code: 0 exit code: 4.
> /sbin/jfs_fsck died with exit status 4
>
> Mon Jul 16 05:34:58 2012
> ----------------
>
> In the hope that this will eventually result in a clean file system we're
> re-running the repair a 3rd time. This will take about 11 hours... If this
> does not work, is there anything else we can try?
>
> Thanks,
> Tim
>
> On Jul 18, 2012, at 9:44 AM, Dave Kleikamp <[email protected]> wrote:
>
>> On 07/17/2012 09:20 PM, Tim Nufire wrote:
>>> Hello,
>>>
>>> I'm having trouble repairing one of my volumes running JFS... Each time
>>> I run jfs_fsck problems are found and repaired but yet the volume is
>>> still marked dirty and the exit code is 4 (File system errors left
>>> uncorrected). Here's the output from the last repair I did...
>>>
>>> Log of /sbin/jfs_fsck -f -y -v /dev/md10
>>> Tue Jul 17 07:21:08 2012
>>>
>>> /sbin/jfs_fsck version 1.1.15.patched.2011.03.07, 04-Mar-2011
>>> processing started: 7/17/2012 7:21:08
>>> The current device is: /dev/md10
>>> 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: 4756914448
>>> **Phase 0 - Replay Journal Log
>>> LOGREDO: Log already redone!
>>> logredo returned rc = 0
>>> **Phase 1 - Check Blocks, Files/Directories, and Directory Entries
>>> Duplicate reference to 1 block(s) beginning at offset 4248749952 found
>>> in file system object FF4086926.
>>> Inode F4086926 has references to cross linked blocks.
>>> File system object FF4086926 has corrupt data (39).
>>> **Phase 2 - Count links
>>> **Phase 3 - Duplicate Block Rescan and Directory Connectedness
>>> Duplicate reference to 1 block(s) beginning at offset 4248749952 found
>>> in file system object FF4086926.
>>> Inode F4086926 has references to cross linked blocks.
>>> **Phase 4 - Report Problems
>>> File system object FF4086926 is linked as:
>>> /20120713/08/08886904e6bbb5a731290014/h10/bzmf2108886904e6bbb5a7312900140000000000000000201207131025000000000240116.bzmf
>>> File claims cross linked block(s).
>>> cannot repair FF4086926. Will release.
>>> **Phase 5 - Check Connectivity
>>> **Phase 6 - Perform Approved Corrections
>>> Superblock marked dirty because repairs are about to be written.
>>> Directory inode F4086922 entry reference to inode F4086926 removed.
>>> Storage allocated to inode F4086926 has been cleared.
>>> **Phase 7 - Rebuild File/Directory Allocation Maps
>>> **Phase 8 - Rebuild Disk Allocation Maps
>>> Filesystem Summary:
>>> Blocks in use for inodes: 2512268
>>> Inode count: 20098144
>>> File count: 11226660
>>> Directory count: 2153660
>>> Block count: 4756914448
>>> Free block count: 561778097
>>> 19027657792 kilobytes total disk space.
>>> 6911782 kilobytes in 2153660 directories.
>>> 16769576062 kilobytes in 11226660 user files.
>>> 0 kilobytes in extended attributes
>>> 0 kilobytes in access control lists
>>> 17881124 kilobytes reserved for system use.
>>> 2247112388 kilobytes are available for use.
>>> *Filesystem is dirty.*
>>> **** Filesystem was modified. ****
>>> processing terminated: 7/17/2012 18:44:33 with return code: 0 exit
>>> code: 4.
>>> /sbin/jfs_fsck died with exit status 4
>>>
>>> Tue Jul 17 18:44:37 2012
>>> ----------------
>>>
>>> From the above it looks like all the problem found have been repaired so
>>> I don't understand why the file system would still be dirty. Has anyone
>>> else seen this? Should I just keep repairing it until it finally comes
>>> back clean?
>>
>> Is it reporting and fixing different problems each time, or is it
>> attempting to fix the same thing over and over? It looks like it should
>> be marking the file system clean since it claims to have fixed the
>> problem, but obviously there are still problems. I can't recall seeing
>> this problem before.
>>
>>> Thanks,
>>> Tim
>
>
> ------------------------------------------------------------------------------
> Live Security Virtual Conference
> Exclusive live event will cover all the ways today's security and
> threat landscape has changed and how IT managers can respond. Discussions
> will include endpoint security, mobile security and the latest in malware
> threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
> _______________________________________________
> Jfs-discussion mailing list
> [email protected]
> https://lists.sourceforge.net/lists/listinfo/jfs-discussion
------------------------------------------------------------------------------
Live Security Virtual Conference
Exclusive live event will cover all the ways today's security and
threat landscape has changed and how IT managers can respond. Discussions
will include endpoint security, mobile security and the latest in malware
threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
_______________________________________________
Jfs-discussion mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/jfs-discussion
