From: Sam Thursfield <sam.thursfield@codethink.co.uk>
To: linux-btrfs@vger.kernel.org
Subject: Advice on FS corruption
Date: Mon, 03 Sep 2012 15:23:15 +0100 [thread overview]
Message-ID: <5044BD53.5080106@codethink.co.uk> (raw)
Hi
I've been running btrfs in various VMs for a while, and periodically
I've experienced corruption in the filesystems being used. None of the
data is important, but I'd like to track down how the corruption
occurred in the first place.
Trying to mount any of the corrupt filesystems fails with an error of
this form:
[ 47.805146] device label baserock devid 1 transid 90 /dev/sdb1
[ 47.810073] btrfs: disk space caching is enabled
[ 47.817261] parent transid verify failed on 1636728832 wanted 76 found 95
[ 47.818081] parent transid verify failed on 1636728832 wanted 76 found 95
[ 47.818522] Failed to read block groups: -5
[ 47.826103] btrfs: open_ctree failed
This is with Linux master as of 29/Aug/2012, so including the latest
'for-linus' branch from the btrfs tree. Attempts to run btrfs-debug-tree
on the disk images fail with the same error, and btrfsck segfaults.
I've not yet been able to reliably reproduce the cause of the
corruption, but I know that in at least one case the VM was compiling
code and then had a forced power-off. However, in at least one case the
corruption appeared after a clean shut down. I have a suspicion that it
may be linked with suspending the host machine and thus causing weird
things to happen to time in the VM's universe, since btrfs has been
working fine with the same kernel in a VM on a machine that is never
suspended or powered off, but I've not yet managed to prove anything.
I'll keep trying to reproduce the issue, in the mean time I'm interested
how common this sort of issue is and if anyone has any tips for
repairing the image, or if there is work in progress to prevent or fix
the corruption.
Thanks
Sam
next reply other threads:[~2012-09-03 14:33 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-09-03 14:23 Sam Thursfield [this message]
2012-09-03 14:35 ` Advice on FS corruption cwillu
2012-09-03 16:12 ` Sam Thursfield
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=5044BD53.5080106@codethink.co.uk \
--to=sam.thursfield@codethink.co.uk \
--cc=linux-btrfs@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).