From: "Jogi Hofmüller" <jogi@mur.at>
To: linux-btrfs@vger.kernel.org
Subject: rootfs crash
Date: Mon, 16 Sep 2013 12:48:31 +0200 [thread overview]
Message-ID: <5236E1FF.4080900@mur.at> (raw)
[-- Attachment #1: Type: text/plain, Size: 1300 bytes --]
Dear all,
Yesterday the rootfs on my laptop crashed. So far all attempts to fix
it have failed; hence I am looking for some help (if possible).
I was creating a copy of a virtual machine (kvm) on my laptop and
started modifying the machine from the inside (installing new packages),
when the laptop froze. Rebooting failed because /dev/sda3 (the rootfs)
could not be mounted anymore.
Some of the errors were
btrfs: failed to read log tree
btrfs: open_ctree failed
Recovery using a Debian/Testing boot stick (kernel 3.10.2, btrfs-tools
v0.20-rc1) were unsuccessful so far. After btrfs-zero-log the device
was still not mountable. Mount attempts fail with i/o erros now.
btrfs restore manages to restore some files from /boot/grub but then
fails with
failed to inflate: -6
and
failed to inflate: -8
and
*** Error in `btrfs': free(): invalid next size
(normal):0x0000000000c0e650 ***
The filesystem is setup as raid1 on devices sda3 and sdb3 using lzo
compression. There are subvolumes for /home and /var.
Images created with btrfs-image are available from before and after
btrfs-zero-log was run. I can make them available if needed.
Any hints appreciated!
Regards,
--
j.hofmüller http://users.mur.at/thesix/
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 294 bytes --]
next reply other threads:[~2013-09-16 11:07 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-09-16 10:48 Jogi Hofmüller [this message]
2013-09-17 10:51 ` rootfs crash Jogi Hofmüller
2013-09-17 11:18 ` Sander
2013-09-17 12:24 ` Jogi Hofmüller
2013-09-17 15:23 ` Jogi Hofmüller
2013-09-17 18:53 ` Clemens Eisserer
2013-09-18 18:15 ` Jogi Hofmüller
2013-09-19 16:18 ` Frank Holton
2013-09-19 17:07 ` Jogi Hofmüller
2013-09-20 4:49 ` Jérôme Poulin
2013-09-20 7:58 ` Jogi Hofmüller
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=5236E1FF.4080900@mur.at \
--to=jogi@mur.at \
--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).