xfs-masters
[Top] [All Lists]

[xfs-masters] [Bug 712] New: 2.6.17.7 XFS internal error xfs_da_do_buf

To: xfs-master@xxxxxxxxxxx
Subject: [xfs-masters] [Bug 712] New: 2.6.17.7 XFS internal error xfs_da_do_buf
From: bugzilla-daemon@xxxxxxxxxxx
Date: Sat, 29 Jul 2006 10:09:36 -0700
Reply-to: xfs-masters@xxxxxxxxxxx
Sender: xfs-masters-bounce@xxxxxxxxxxx
http://oss.sgi.com/bugzilla/show_bug.cgi?id=712

           Summary: 2.6.17.7 XFS internal error xfs_da_do_buf
           Product: Linux XFS
           Version: unspecified
          Platform: Other
        OS/Version: Linux
            Status: NEW
          Severity: critical
          Priority: P2
         Component: XFS kernel code
        AssignedTo: xfs-master@xxxxxxxxxxx
        ReportedBy: p.mironchik@xxxxxxxxxxx
                CC: p.mironchik@xxxxxxxxxxx


I found that xfs behaves unstable on recent kernel 2.6.17.7. I put 
here results of doing one test: untaring big file on xfs volume. 
Please look at results, also as if some additional information is required.

Hardware:
 Production board based on iop80321 Xscale CPU (ARM).
Software:
 I am using linux-2.6.17.7 vanilla, toolchain based on 3.4 gcc.

Repoduce Steps:
1)mkfs.xfs /dev/xxxx
2)mount /dev/xxxx /mnt
3)cd /mnt ; tar -xf /volume/somestuff
than get I/O error here

getting like that:
0x0: 58 44 00 00 00 12 0f a6 00 00 00 00 72 75 00 00 
Filesystem "dm-14": XFS internal error xfs_da_do_buf(2) at line 2212 of file
fs/xfs/xfs_da_btree.c.  Caller 0xc0159a0c
[<c0028a4c>] (dump_stack+0x0/0x14) from [<c016cf74>] 
(xfs_error_report+0x54/0x64)
[<c016cf20>] (xfs_error_report+0x0/0x64) from [<c016d074>]
(xfs_corruption_error+0xf0/0x108)
[<c016cf84>] (xfs_corruption_error+0x0/0x108) from [<c0159854>]
(xfs_da_do_buf+0x678/0x798)
[<c01591dc>] (xfs_da_do_buf+0x0/0x798) from [<c0159a0c>] 
(xfs_da_read_buf+0x3c/0x44)
[<c01599d4>] (xfs_da_read_buf+0x4/0x44) from [<c015f340>]
(xfs_dir2_block_addname+0x68/0x998)
[<c015f2d8>] (xfs_dir2_block_addname+0x0/0x998) from [<c0167644>]
(xfs_dir2_sf_addname+0x1e8/0x918)
[<c016745c>] (xfs_dir2_sf_addname+0x0/0x918) from [<c015ec04>]
(xfs_dir2_createname+0xb8/0x140)
[<c015eb4c>] (xfs_dir2_createname+0x0/0x140) from [<c0195404>]
(xfs_symlink+0x804/0x9f4)
[<c0194c00>] (xfs_symlink+0x0/0x9f4) from [<c019f768>] 
(xfs_vn_symlink+0xbc/0x178)
[<c019f6ac>] (xfs_vn_symlink+0x0/0x178) from [<c0089540>] 
(vfs_symlink+0x80/0xc0)
[<c00894c0>] (vfs_symlink+0x0/0xc0) from [<c008961c>] (sys_symlinkat+0x9c/0xf8)
 r7 = CFCC1F30  r6 = C7771000  r5 = C46BAB60  r4 = C46BAB60
[<c0089580>] (sys_symlinkat+0x0/0xf8) from [<c0089690>] (sys_symlink+0x18/0x1c)
 r8 = C0023EE4  r7 = 00000053  r6 = 00047580  r5 = 00047530
 r4 = 00047584 
[<c0089678>] (sys_symlink+0x0/0x1c) from [<c0023d40>] 
(ret_fast_syscall+0x0/0x2c)
Filesystem "dm-14": XFS internal error xfs_trans_cancel at line 1150 of file
fs/xfs/xfs_trans.c.  Caller 0xc019558c
[<c0028a4c>] (dump_stack+0x0/0x14) from [<c016cf74>] 
(xfs_error_report+0x54/0x64)
[<c016cf20>] (xfs_error_report+0x0/0x64) from [<c018b6a4>]
(xfs_trans_cancel+0x7c/0x12c)
[<c018b628>] (xfs_trans_cancel+0x0/0x12c) from [<c019558c>]
(xfs_symlink+0x98c/0x9f4)
 r7 = CFCC1DBC  r6 = CFCC1E80  r5 = 000003DE  r4 = 00000000
[<c0194c00>] (xfs_symlink+0x0/0x9f4) from [<c019f768>] 
(xfs_vn_symlink+0xbc/0x178)
[<c019f6ac>] (xfs_vn_symlink+0x0/0x178) from [<c0089540>] 
(vfs_symlink+0x80/0xc0)
[<c00894c0>] (vfs_symlink+0x0/0xc0) from [<c008961c>] (sys_symlinkat+0x9c/0xf8)
 r7 = CFCC1F30  r6 = C7771000  r5 = C46BAB60  r4 = C46BAB60
[<c0089580>] (sys_symlinkat+0x0/0xf8) from [<c0089690>] (sys_symlink+0x18/0x1c)
 r8 = C0023EE4  r7 = 00000053  r6 = 00047580  r5 = 00047530
 r4 = 00047584 
[<c0089678>] (sys_symlink+0x0/0x1c) from [<c0023d40>] 
(ret_fast_syscall+0x0/0x2c)
xfs_force_shutdown(dm-14,0x8) called from line 1151 of file fs/xfs/xfs_trans.c.
 Return address = 0xc01a2c4c
Filesystem "dm-14": Corruption of in-memory data detected.  Shutting down
filesystem: dm-14

NOTE: hardware is not responsible for corruption, ie ext3 works fine.

xfs_repair(2.8.4) -n

...
...
entry "less" in directory inode 2009243 points to free inode 2025152, would junk
entry
entry "seq" in directory inode 2009243 points to free inode 2025153, would junk
entry
entry "test" in directory inode 2009243 points to free inode 2025154, would junk
entry
entry "tr" in directory inode 2009243 points to free inode 2025155, would junk 
entry
entry "subst" in directory inode 2009243 points to free inode 2025156, would
junk entry
entry "uuidgen" in directory inode 2009243 points to free inode 2025157, would
junk entry
entry "netcat" in directory inode 2009243 points to free inode 2025158, would
junk entry
entry "wget" in directory inode 2009243 points to free inode 2025159, would junk
entry
entry "which" in directory inode 2009243 points to free inode 2025160, would
junk entry
entry "bc" in directory inode 2009243 points to free inode 2025161, would junk 
entry
entry "chrootuid" in directory inode 2009243 points to free inode 2025162, would
junk entry
entry "killall" in directory inode 2009243 points to free inode 2025163, would
junk entry
entry "diff" in directory inode 2009243 points to free inode 2025164, would junk
entry
        - traversals finished ... 
        - moving disconnected inodes to lost+found ... 
disconnected dir inode 392012, would move to lost+found
disconnected dir inode 556954, would move to lost+found
disconnected dir inode 2009243, would move to lost+found
Phase 7 - verify link counts...
would have reset inode 392004 nlinks from 13 to 9
would have reset inode 556955 nlinks from 4 to 3
would have reset inode 854746 nlinks from 3 to 2
No modify flag set, skipping filesystem flush and exiting.


xfs_repair -L /dev/xxxx
entry "which" at block 0 offset 256 in directory inode 2009243 references free
inode 2025160
        clearing inode number in entry at offset 256...
entry "bc" at block 0 offset 272 in directory inode 2009243 references free
inode 2025161
        clearing inode number in entry at offset 272...
entry "chrootuid" at block 0 offset 288 in directory inode 2009243 references
free inode 2025162
        clearing inode number in entry at offset 288...
entry "killall" at block 0 offset 312 in directory inode 2009243 references free
inode 2025163
        clearing inode number in entry at offset 312...
entry "diff" at block 0 offset 336 in directory inode 2009243 references free
inode 2025164
        clearing inode number in entry at offset 336...
no .. entry for directory 2009243
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 128
rebuilding directory inode 42065
rebuilding directory inode 392004
rebuilding directory inode 1401147
#

-- 
Configure bugmail: http://oss.sgi.com/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.


<Prev in Thread] Current Thread [Next in Thread>
  • [xfs-masters] [Bug 712] New: 2.6.17.7 XFS internal error xfs_da_do_buf, bugzilla-daemon <=