#282 jfs.fsck fails on large volumes

bug
closed
nobody
fsck (38)
9
2010-11-22
2010-10-08
Patrick Allemann
No

Hi,

this is a follow-up bug of issue 2905273

Fsck is still failing on large volumes:
fsck.jfs /dev/pod/video
fsck.jfs version 1.1.14, 06-Apr-2009
processing started: 10/8/2010 7.50.17
Using default parameter: -p
The current device is: /dev/pod/video
Block size in bytes: 4096
Filesystem size in blocks: 12135967744
**Phase 0 - Replay Journal Log
logredo failed (rc=-220). fsck continuing.
**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
ujfs_rw_diskblocks: disk_count is 0
Unrecoverable error writing M to /dev/pod/video. CANNOT CONTINUE.

in the referenced issue it was written that we should not hesitate to nag about this issue ;)

Thank you

Discussion

    • priority: 5 --> 9
     
  • some more verbose log:

    fsck -v /dev/pod/video
    fsck 1.41.3 (12-Oct-2008)
    fsck.jfs version 1.1.14, 06-Apr-2009
    processing started: 11/22/2010 11.23.4
    Using default parameter: -p
    The current device is: /dev/pod/video
    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: 12135967744
    **Phase 0 - Replay Journal Log
    LOGREDO: Log record for Sync Point at: 0x0614a284
    LOGREDO: Beginning to update the Inode Allocation Map.
    LOGREDO: Done updating the Inode Allocation Map.
    LOGREDO: Beginning to update the Block Map.
    LOGREDO: Invalid leaf index detected while updating dmap page.
    LOGREDO: Error rebuilding DMap page (k=(d) 0, j=(d) 423, i=(d) 690).
    LOGREDO: Write Block Map control page failed in UpdateMaps().
    LOGREDO: Unable to update map(s).
    logredo failed (rc=-220). fsck continuing.
    **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
    ujfs_rw_diskblocks: disk_count is 0
    Unrecoverable error writing M to /dev/pod/video. CANNOT CONTINUE.
    Fatal error (-10091,87) accessing the filesystem (2,1778831360,0,0).
    **** Filesystem was modified. ****
    processing terminated: 11/22/2010 11:44:28 with return code: -10091 exit code: 4.

    It looks to me as if the RAID would still be recoverable. But I cannot mount the volume.

     
  • Hi,

    sorry for the latest port - everything is fine in the jfsutils-version currently checked in the CVS.
    Closing Ticket.
    thank you and apologies

     
    • status: open --> closed