On 02/21/14 08:48, Bruno PrÃmont wrote:
On Fri, 21 Feb 2014 08:14:12 -0600 Mark Tinguely wrote:
On 02/21/14 01:47, Bruno PrÃmont wrote:
A virtual server of mine stopped working properly yesterday because one
partition became corrupted (or corruption has been stumbled over).
The running kernel was 3.12.6.
I would have appreciated if the XFS filesystem had continued being
accessible even if only in read-only mode instead of completely shutting
down. That would have made it possible to gather more information and
doing so more easily as well.
Well it appears that the xlog_cil_push problem is not going to be fixed
soon, so I will repost the patch for the log recovery portion.
Restarting the system any attempt to mount that partition (without
-o norecovery,ro) results in the following trace (transcribed):
XFS (sda5): Mounting Filesystem
XFS (sda5): Starting recovery (logdev: internal)
XFS: Internal error XFS_WANT_CORRUPTED_GOTO at line 1602 of file
CPU: 0 PID: 606 Commm: mount Not tainted 3.13.0-hetzner #1
Hardware name: Bochs Bochs, BIOS Bochs 01/01/2007
000000000002eb84 ffff88001dc53ab8 ffffffff813ca339 ffff88001dc53ad8
ffffffff81156d4a ffffffff8116d926 00000000000002a8 ffff88001dc53b68
ffffffff8116b8dd ffff88001dd7ccc0 0000000000000000 0000000000000001
[<ffffffff8116d926>] ? xfs_free_extent+0xd6/0x120
[<ffffffff810d5fa4>] ? kmem_cache_alloc+0xa4/0xb0
[<ffffffff81074709>] ? wake_up_bit+0x29/0x40
[<ffffffff811958ee>] ? xfs_iunlock+0x6e/0x90
[<ffffffff811e337c>] ? ida_get_new_above+0x21c/0x290
[<ffffffff81166de0>] ? xfs_parseargs+0xc10/0xc10
[<ffffffff810b3b43>] ? strndup_user+0x53/0x70
XFS (sda5): Failed to recover EFIs
XFS (sda5): log mount finish failed
curious on which version of Linux hit this problem?
The trace was produced by 3.13 kernel from kernel.org.
A reboot attempt with 3.12.6 showed a similar trace though I didn't
The original problem is attempting to free a partial free extent,
I was curious because that problem has been flaring up recently
internally and in the community.
Thank-you for the information.