XFS mount fail: XFS_WANT_CORRUPTED_GOTO fs/xfs/xfs_alloc.c
sandeen at sandeen.net
Wed Dec 8 21:51:22 CST 2010
On 12/3/10 10:19 PM, Ajeet Yadav wrote:
> Our test case is automated:
> 1. Create large number of file of 6KB sizes ( 6KB is taken, we wanted to increase journal load, and file size not in multiple of file system block size)
> 2. Set target to reboot at random seconds seconds.
What exactly is meant by "reboot?"
Does this mean "cycle power" or cleanly reboot?
Based on the problems you are encountering, I am guessing that
you drop power.
Is the storage external for this test? Is it qualified hardware
or are you planning on supporting anything that the user may choose
to plug into their device?
It's possible that an external USB device is behaving poorly,
and that may be the root of your problems.
> 3. Next boot do "ls" of all files in XFS partition.
> 4. Remove all files in XFS.
> 5. Go back to step 1
> The purpose of this test is to test journal and stability of XFS filestem.
> Do you think, we should consider this test case ?
> Other is when we should run xfs_repair ? because if mount fails and journal contain dirty logs then xfs_repair does not run, we are forced to use (-L) option but its description say that (-L) can corrupt the file system.
> Other case even if xfs mount successfully, even in that case accessing some files give IO input/ output error.
> 1. I recommend the following usage for xfs_repair so that we do not come accross these problem
> Mount Success -> Umount -> run xfs_repair -> mount
> Mount fails -> try xfs_repair -> xfs_repair fails -> finally xfs_repair -L -> mount
> Adding above mount + xfs_repair procedure to script makes file system stable. But other member of my team do not agree as it increases mount time.
> On Fri, Dec 3, 2010 at 4:15 AM, Dave Chinner <david at fromorbit.com <mailto:david at fromorbit.com>> wrote:
> On Thu, Dec 02, 2010 at 12:31:30PM +0530, Ajeet Yadav wrote:
> > Dear all,
> > This is XFS fail mount log on linux 184.108.40.206
> > XFS mounting filesystem sda2
> > Starting XFS recovery on filesystem: sda2 (logdev: internal)
> > XFS internal error XFS_WANT_CORRUPTED_GOTO at line 1629 of file
> > fs/xfs/xfs_alloc.c. Caller 0x80129658
> > Call Trace:
> > [<802dedc8>] dump_stack+0x8/0x34 from[<80127400>]
> > xfs_free_ag_extent+0x128/0x7ac
> > [<80127400>] xfs_free_ag_extent+0x128/0x7ac from[<80129658>]
> > xfs_free_extent+0xb8/0xe8
> > [<80129658>] xfs_free_extent+0xb8/0xe8 from[<80163978>]
> > xlog_recover_process_efi+0x160/0x214
> > [<80163978>] xlog_recover_process_efi+0x160/0x214 from[<80163ac4>]
> > xlog_recover_process_efis+0x98/0x11c
> > [<80163ac4>] xlog_recover_process_efis+0x98/0x11c from[<8016663c>]
> > xlog_recover_finish+0x28/0xdc
> > [<8016663c>] xlog_recover_finish+0x28/0xdc from[<8016aec0>]
> > xfs_mountfs+0x4d0/0x610
> > [<8016aec0>] xfs_mountfs+0x4d0/0x610 from[<80184434>]
> > xfs_fs_fill_super+0x1fc/0x418
> > [<80184434>] xfs_fs_fill_super+0x1fc/0x418 from[<800bae48>]
> > get_sb_bdev+0x11c/0x1c0
> > [<800bae48>] get_sb_bdev+0x11c/0x1c0 from[<80181f20>]
> > xfs_fs_get_sb+0x20/0x2c
> > [<80181f20>] xfs_fs_get_sb+0x20/0x2c from[<800b9424>]
> > vfs_kern_mount+0x68/0xd0
> > [<800b9424>] vfs_kern_mount+0x68/0xd0 from[<800b94f0>]
> > do_kern_mount+0x54/0x118
> > [<800b94f0>] do_kern_mount+0x54/0x118 from[<800d44e8>] do_mount+0x7b4/0x828
> > [<800d44e8>] do_mount+0x7b4/0x828 from[<800d45f8>] sys_mount+0x9c/0x194
> > [<800d45f8>] sys_mount+0x9c/0x194 from[<800102c4>] stack_done+0x20/0x3c
> > Failed to recover EFIs on filesystem: sda2
> > XFS: log mount finish failed
> You corrupted a free space btree. Care to tell uswhat test you were
> running that caused this? Did you pull the plug on the device
> during a copy again?
> Dave Chinner
> david at fromorbit.com <mailto:david at fromorbit.com>
> xfs mailing list
> xfs at oss.sgi.com
More information about the xfs