Mailinglist Archive: opensuse-bugs (5372 mails)

[bugzilla_noreply@xxxxxxxxxx]

https://bugzilla.novell.com/show_bug.cgi?id=280905

           Summary: can not xfs_repair a partition, bug reported in output
                    (fatal error -- 117 - couldn't iget disconnected inode)
           Product: openSUSE 10.2
           Version: Final
          Platform: Other
        OS/Version: openSUSE 10.2
            Status: NEW
          Severity: Normal
          Priority: P5 - None
         Component: Kernel
        AssignedTo: kernel-maintainers@xxxxxxxxxxxxxxxxxxxxxx
        ReportedBy: robin.listas@xxxxxxxxxxxxxx
         QAContact: qa@xxxxxxx


I had a bad disk failure some months back (with 10.1). In the affected
partition  the xfs structure is not repairable, the program halts with a bug.
This test I do with 10.2. There is currently no hardware error, no surface
defects.
See the output for the command (excerpted (...)):

nimrodel:~ # xfs_repair /dev/hdd8
Phase 1 - find and verify superblock...
Phase 2 - using internal log
        - zero log...
        - scan filesystem freespace and inode maps...
        - found root inode chunk
Phase 3 - for each AG...
        - scan and clear agi unlinked lists...
        - process known inodes and perform inode discovery...
        - agno = 0
..
        - agno = 11
no .. entry for directory 46170794
..
no .. entry for directory 46565380
        - agno = 12
no .. entry for directory 50332964
..
no .. entry for directory 50682298
        - agno = 13
        - agno = 14
no .. entry for directory 58720388
..
no .. entry for directory 58729626
bogus .. inode number (0) in directory inode 58739862, clearing inode number
no .. entry for directory 58749936
..
no .. entry for directory 58843376
bogus .. inode number (0) in directory inode 58843428, clearing inode number
bogus .. inode number (0) in directory inode 58843438, clearing inode number
no .. entry for directory 58843452
no .. entry for directory 58847875
no .. entry for directory 58847934
bogus .. inode number (0) in directory inode 58855317, clearing inode number
        - agno = 15
        - process newly discovered inodes...
Phase 4 - check for duplicate blocks...
        - setting up duplicate extent list...
        - clear lost+found (if it exists) ...
        - clearing existing "lost+found" inode
        - deleting existing "lost+found" entry
        - check for inodes claiming duplicate blocks...
        - agno = 0
..
        - agno = 8
entry ".." at block 0 offset 32 in directory inode 33680808 references free
inode 131
        clearing inode number in entry at offset 32...
no .. entry for directory 33680808
        - agno = 9
        - agno = 10
        - agno = 11
no .. entry for directory 46170794
..
no .. entry for directory 46565380
        - agno = 12
no .. entry for directory 50332964
..
no .. entry for directory 50682298
        - agno = 13
        - agno = 14
no .. entry for directory 58720388
..
no .. entry for directory 58729626
bogus .. inode number (0) in directory inode 58739862, clearing inode number
no .. entry for directory 58749936
..
no .. entry for directory 58843376
bogus .. inode number (0) in directory inode 58843428, clearing inode number
bogus .. inode number (0) in directory inode 58843438, clearing inode number
no .. entry for directory 58843452
no .. entry for directory 58847875
no .. entry for directory 58847934
bogus .. inode number (0) in directory inode 58855317, clearing inode number
        - agno = 15
Phase 5 - rebuild AG headers and trees...
        - reset superblock...
Phase 6 - check inode connectivity...
        - resetting contents of realtime bitmap and summary inodes
        - ensuring existence of lost+found directory
        - traversing filesystem starting at / ... 
rebuilding directory inode 33680808
        - traversal finished ... 
        - traversing all unattached subtrees ... 
        - traversals finished ... 
        - moving disconnected inodes to lost+found ... 
disconnected dir inode 168, moving to lost+found
..
..
..
disconnected dir inode 544, moving to lost+found
disconnected dir inode 46144141, moving to lost+found
disconnected dir inode 46144142, moving to lost+found
disconnected inode 46170775, moving to lost+found
corrupt inode 46170775 (btree).  This is a bug.
Please report it to xfs@xxxxxxxxxxxx
cache_node_purge: refcount was 1, not zero (node=0x82e8af8)

fatal error -- 117 - couldn't iget disconnected inode
nimrodel:~ #


I tried several times, it always stop with the same error messages. I will keep
that partition for some time, just in case you want some test to run. I can not
email the partition, sorry: too big, and it was /home --> private data.


-- 
Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug, or are watching someone who is.