<html><head><style type="text/css"><!-- DIV {margin:0px;} --></style></head><body><div style="font-family:times new roman,new york,times,serif;font-size:12pt">You have a corrupted free space btree.<br><br>Err... apologies for my ignorance, but what is a free space btree?<div><br></div><div style="font-family: times new roman,new york,times,serif; font-size: 12pt;">I had serial trace from raid controller which i just checked and it logged some 'Loose cabling', but this was months back.....<br>not sure whether that can be the cause of this.. strange if that is the case since it's been a long time<br><br><br><div style="font-family: arial,helvetica,sans-serif; font-size: 13px;"><font face="Tahoma" size="2"><hr size="1"><b><span style="font-weight: bold;">From:</span></b> Dave Chinner <david@fromorbit.com><br><b><span style="font-weight: bold;">To:</span></b> stress_buster <leo1783@yahoo.com><br><b><span style="font-weight: bold;">Cc:</span></b>
xfs@oss.sgi.com<br><b><span style="font-weight: bold;">Sent:</span></b> Tue, April 12, 2011 3:19:17 PM<br><b><span style="font-weight: bold;">Subject:</span></b> Re: fs corruption<br></font><br>
On Tue, Apr 12, 2011 at 02:33:07AM -0700, stress_buster wrote:<br>> <br>> My dmesg output shows the below trace. It repeats over and over again.<br>> <br>> XFS internal error XFS_WANT_CORRUPTED_GOTO at line 1545 of file<br>> fs/xfs/xfs_alloc.c. Caller 0xffffffff881a8961<br>> <br>> Call Trace:<br>> [<ffffffff881a6e27>] :xfs:xfs_free_ag_extent+0x19e/0x67e<br>> [<ffffffff881a8961>] :xfs:xfs_free_extent+0xa9/0xc9<br>> [<ffffffff881d96cf>] :xfs:xlog_recover_process_efi+0x112/0x16c<br>> [<ffffffff881f31b4>] :xfs:xfs_fs_fill_super+0x0/0x3e4<br>> [<ffffffff881da8c2>] :xfs:xlog_recover_process_efis+0x4f/0x8d<br>> [<ffffffff881da914>] :xfs:xlog_recover_finish+0x14/0xad<br>> [<ffffffff881f31b4>] :xfs:xfs_fs_fill_super+0x0/0x3e4<br>> [<ffffffff881df420>] :xfs:xfs_mountfs+0x498/0x5e2<br>>
[<ffffffff881dfb42>] :xfs:xfs_mru_cache_create+0x113/0x143<br>> [<ffffffff881f33b7>] :xfs:xfs_fs_fill_super+0x203/0x3e4<br>> [<ffffffff800e544f>] get_sb_bdev+0x10a/0x16c<br>> [<ffffffff800e4dec>] vfs_kern_mount+0x93/0x11a<br>> [<ffffffff800e4eb5>] do_kern_mount+0x36/0x4d<br>> [<ffffffff800ef2ed>] do_mount+0x6a9/0x719<br>> [<ffffffff80008d84>] __handle_mm_fault+0x5f2/0xfaa<br>> [<ffffffff80022127>] __up_read+0x19/0x7f<br>> [<ffffffff80067b88>] do_page_fault+0x4fe/0x874<br>> [<ffffffff8012c580>] inode_doinit_with_dentry+0x86/0x47c<br>> [<ffffffff800cd378>] zone_statistics+0x3e/0x6d<br>> [<ffffffff8000f2ff>] __alloc_pages+0x78/0x308<br>> [<ffffffff8004c9fd>] sys_mount+0x8a/0xcd<br>> [<ffffffff8005e116>] system_call+0x7e/0x83<br>> <br>> Failed to recover
EFIs on filesystem: cciss/c0d0<br>> XFS: log mount finish failed<br>> <br>> Can someone shed some light on what is happening here?<br><br>You have a corrupted free space btree. How it occurred, I have no<br>idea.<br><br>> Also what the next steps I need to take to repair the fs? (assuming my xfs<br>> fs is corrupted)<br>> Will running xfs_repair be good enough in this case?<br><br>That's all you can do. If it's really important, and you don't have<br>a backup, I'd suggest mounting with "-o ro,norecovery" and taking a<br>backup first....<br><br>Cheers,<br><br>Dave.<br>-- <br>Dave Chinner<br><a ymailto="mailto:david@fromorbit.com" href="mailto:david@fromorbit.com">david@fromorbit.com</a><br></div></div>
</div></body></html>