For all interested, It looks like the following stack trace (also related to this problem):
[<ffffffff817557fe>] dump_stack+0x46/0x58 [<ffffffffa028ffdf>] xfs_error_report+0x3f/0x50 [xfs] [<ffffffffa02aae97>] ? xfs_free_extent+0xd7/0x120 [xfs] [<ffffffffa02a8496>] xfs_free_ag_extent+0x4b6/0x720 [xfs] [<ffffffffa02aae97>] xfs_free_extent+0xd7/0x120 [xfs] [<ffffffffa02e0b00>] xlog_recover_process_efi+0x170/0x1b0 [xfs] [<ffffffffa02e2156>] xlog_recover_process_efis.isra.11+0x76/0xd0 [xfs] [<ffffffffa02e69ba>] xlog_recover_finish+0x2a/0xd0 [xfs] [<ffffffffa02ebb34>] xfs_log_mount_finish+0x34/0x50 [xfs] [<ffffffffa02a0221>] xfs_mountfs+0x481/0x710 [xfs] [<ffffffffa02a131d>] ? xfs_mru_cache_create+0x15d/0x1a0 [xfs] [<ffffffffa02a3707>] xfs_fs_fill_super+0x2c7/0x340 [xfs] [<ffffffff811cd4a9>] mount_bdev+0x1b9/0x200 [<ffffffffa02a3440>] ? xfs_parseargs+0xb30/0xb30 [xfs] [<ffffffffa02a16f5>] xfs_fs_mount+0x15/0x20 [xfs] [<ffffffff811ce123>] mount_fs+0x43/0x1b0 [<ffffffff811e9bf6>] vfs_kern_mount+0x76/0x130 [<ffffffff811eb3a4>] do_new_mount+0xa4/0x1f0 [<ffffffff811ec706>] do_mount+0x216/0x260 [<ffffffff811ecad0>] SyS_mount+0x90/0xe0 [<ffffffff8176ae2d>] system_call_fastpath+0x1a/0x1f With the following observed error: XFS: Internal error XFS_WANT_CORRUPTED_GOTO at line 1602 of file .../xfs_alloc.c. Caller 0xffffffffa02aae97 Can be linked to a specific recent upstream commit that fixes XFS wrong behavior for suspending/resuming under medium/heavy workload: commit 8018ec083c72443cc74fd2d08eb7c5dddc13af53 Author: Brian Foster <[email protected]> Date: Tue Sep 9 11:44:46 2014 +1000 xfs: mark all internal workqueues as freezable Workqueues must be explicitly set as freezable to ensure they are frozen in the assocated part of the hibernation/suspend sequence. Freezing of workqueues and kernel threads is important to ensure that modifications are not made on-disk after the hibernation image has been created. Otherwise, the in-memory state can become inconsistent with what is on disk and eventually lead to filesystem corruption. We have reports of free space btree corruptions that occur immediately after restore from hibernate that suggest the xfs-eofblocks workqueue could be causing such problems if it races with hibernation. Mark all of the internal XFS workqueues as freezable to ensure nothing changes on-disk once the freezer infrastructure freezes kernel threads and creates the hibernation image. Signed-off-by: Brian Foster <[email protected]> Reported-by: Carlos E. R. <[email protected]> Reviewed-by: Dave Chinner <[email protected]> Signed-off-by: Dave Chinner <[email protected]> But also make sure xfs_freeze works as expected (freezing all internal workqueues). -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1382801 Title: XFS: mount hangs for corrupted filesystem To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1382801/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
