Hi Eric,<br><br>This seems related with the directory Inodes.<br><br>I tried the changes mentioned in the patch, they didn't work for me.<br>As mine seems to be ARM with EABI.<br><br>When files are created at the Root . It reports Root Inode :128 at the crash with bno:2<br>
<br>While suppose if another directory is created and Inode is 137<br>And then, rm -rf * in that directory<br>Crash would report error With this inode<br><br>xfs_da_do_buf: bno 8388631<br>dir: inode 137<br>Filesystem "sda4": XFS internal error xfs_da_do_buf(1) at line 1992 of file fs/x<br>
fs/xfs_da_btree.c. Caller 0xc0118eb8<br>ry<br>rm: unable [<c0022618>] (dump_stack+0x0/0x14) from [<c0125700>] (xfs_error_repor<br>t+0x54/0x64)<br>[<c01256ac>] (xfs_error_report+0x0/0x64) from [<c0118a74>] (xfs_da_do_buf+0x334/<br>
0x6ec)<br>[<c0118740>] (xfs_da_do_buf+0x0/0x6ec) from [<c0118eb8>] (xfs_da_read_buf+0x34/0<br>x3c)<br>[<c0118e84>] (xfs_da_read_buf+0x0/0x3c) from [<c011b5c8>] (xfs_da_node_lookup_in<br>t+0x70/0x318)<br>
[<c011b558>] (xfs_da_node_lookup_int+0x0/0x318) from [<c01219d4>] (xfs_dir2_node<br>_removename+0x48/0x500)<br>[<c012198c>] (xfs_dir2_node_removename+0x0/0x500) from [<c011c334>] (xfs_dir_rem<br>ovename+0x100/0x10c)<br>
[<c011c234>] (xfs_dir_removename+0x0/0x10c) from [<c014cde4>] (xfs_remove+0x280/<br>0x424)<br> r6 = 00000000 r5 = 00000000 r4 = 00003951<br>[<c014cb64>] (xfs_remove+0x0/0x424) from [<c0157044>] (xfs_vn_unlink+0x30/0x60)<br>
[<c0157014>] (xfs_vn_unlink+0x0/0x60) from [<c009175c>] (vfs_unlink+0x70/0xac)<br> r7 = C471C000 r6 = C43BF598 r5 = C395B3B8 r4 = 00000000<br>[<c00916ec>] (vfs_unlink+0x0/0xac) from [<c0093ac0>] (do_unlinkat+0xcc/0x14c)<br>
r6 = C3968AD8 r5 = C395B3B8 r4 = 00000000<br>[<c00939f4>] (do_unlinkat+0x0/0x14c) from [<c0093b58>] (sys_unlink+0x18/0x1c)<br> r7 = 0000000A r6 = 0000000C r5 = 00000008 r4 = BEDCBC19<br>[<c0093b40>] (sys_unlink+0x0/0x1c) from [<c001de40>] (ret_fast_syscall+0x0/0x2c)<br>
to remove `5826'xfs_da_do_buf: bno 8388631<br>dir: inode 137<br><br>Checking this through xfs_check will show:<br>]# xfs_check /dev/sdb4<br>dir 128 block 8388609 extra leaf entry d5830 402<br>dir 128 block 8388609 extra leaf entry d5831 404<br>
dir 128 block 8388609 extra leaf entry d5832 406<br>dir 128 block 8388609 extra leaf entry d5833 408<br>dir 128 block 8388609 extra leaf entry d5834 40a<br>dir 128 block 8388609 extra leaf entry d5835 40c<br>dir 128 block 8388609 extra leaf entry d5836 40e<br>
dir 128 block 8388609 extra leaf entry d5837 410<br>...<br>...<br>dir 128 block 8388609 extra leaf entry ddab2 5fa<br>dir 128 block 8388609 extra leaf entry ddab3 5fc<br>dir 128 block 8388609 extra leaf entry ddab4 5fe<br>
bad free block ent 1 is 65535 should be 0 for dir ino 128 block 16777216<br>bad free block ent 2 is 0 should be 65535 for dir ino 128 block 16777216<br>dir ino 128 missing leaf entry for d5a37/260<br>dir ino 128 missing leaf entry for d5a38/262<br>
dir ino 128 missing leaf entry for d5a39/264<br>...<br>...<br><br>I tried checking the inode before and after corruption using xfs_db and xfs_check<br>When I create files and check using xfs_check, no corruption is showed and also xfs_db shows correct results for the inode.<br>
While after the crash is observed, xfs_check show the errors I mentioned above.<br>Also, the values for Inode using xfs_db differ from the ones I get after i do xfs_repair -L on the device.<br><br><br>Can u get anything from the above mentioned log.<br>
<br>Thanks & Regards,<br>Amit Sahrawat<br><br><br><div class="gmail_quote">On Wed, Oct 21, 2009 at 11:14 PM, Eric Sandeen <span dir="ltr"><<a href="mailto:sandeen@sandeen.net">sandeen@sandeen.net</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;"><div class="im">Amit Sahrawat wrote:<br>
> Thanks Eric,<br>
><br>
> Yes, I am able to get this for the same Inode and Block number.<br>
><br>
> xfs_check reports error for dir inode 128 missing leaf entries..(exact<br>
> string I m missing), will provide you the details.<br>
><br>
> Using xfs_repair fixes the problem. But again the same operation leads<br>
> to the crash.<br>
> Even on a freshly formatted disk, I get this error.<br>
><br>
> Please let me know from where I can get this patch to try whether it<br>
> fixes for me or not.<br>
<br>
<br>
</div><a href="http://git.kernel.org/?p=linux/kernel/git/torvalds/linux-2.6.git;a=commitdiff_plain;h=ae23a5e87dbbf4657a82e1ff8ebc52ab50361c14" target="_blank">http://git.kernel.org/?p=linux/kernel/git/torvalds/linux-2.6.git;a=commitdiff_plain;h=ae23a5e87dbbf4657a82e1ff8ebc52ab50361c14</a><br>
<font color="#888888"><br>
-Eric<br>
<br>
</font></blockquote></div><br>