From: Maxime Nicco <maxime.nicco@free.fr>
To: cwillu <cwillu@cwillu.com>
Cc: linux-btrfs@vger.kernel.org
Subject: Re: Bad tree block, on root filesystem after reset
Date: Tue, 09 Apr 2013 19:52:39 +0200 [thread overview]
Message-ID: <51645567.7060807@free.fr> (raw)
In-Reply-To: <CAE5mzviyg7pSw0a6GhctBC4sCEFbLSfRqAtC6Qc10t_qi8Je0Q@mail.gmail.com>
Le 09/04/2013 19:42, cwillu a écrit :
> On Tue, Apr 9, 2013 at 11:18 AM, Maxime Nicco <maxime.nicco@free.fr
> <mailto:maxime.nicco@free.fr>> wrote:
>
> Hi,
>
> Today my laptop messed-up my display configuration between 2
> screens. I had to reset it, but my btrfs root partition is no longer
> mountable.
> I have the following output in dmesg :
>
>
> What kernel is this on, and have you tried mounting with -o recovery?
Oups i forgot to mention my kernel, my system was on 3.8, and i work
from a live cd in 3.5.
I already tried mounting with -o recovery, here the result
# mount -t btrfs -o recovery /dev/sda2 /mnt/sda2
mount: wrong fs type, bad option, bad superblock on /dev/sda2,
missing codepage or helper program, or other error
In some cases useful info is found in syslog - try
dmesg | tail or so
the dmesg look like this
device fsid f9264db3-f277-47b6-bd8f-57d0a67c93a7 devid 1 transid 78577
/dev/sda2
btrfs bad tree block start 0 18565984256
btrfs bad tree block start 0 18565984256
btrfs: enabling auto recovery
btrfs: failed to read tree root on sda2
btrfs bad tree block start 0 18565984256
btrfs bad tree block start 0 18565984256
btrfs: failed to read tree root on sda2
parent transid verify failed on 18563280896 wanted 78576 found 78578
parent transid verify failed on 18563280896 wanted 78576 found 78578
btrfs read error corrected: ino 1 off 18563280896 (dev /dev/sda2 sector
38894232)
btrfs: failed to read tree root on sda2
btrfs bad tree block start 0 18565726208
btrfs bad tree block start 0 18565726208
btrfs: failed to read tree root on sda2
btrfs bad tree block start 0 18564616192
btrfs bad tree block start 0 18564616192
btrfs: failed to read tree root on sda2
btrfs: open_ctree failed
prev parent reply other threads:[~2013-04-09 17:52 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-04-09 17:18 Bad tree block, on root filesystem after reset Maxime Nicco
[not found] ` <CAE5mzviyg7pSw0a6GhctBC4sCEFbLSfRqAtC6Qc10t_qi8Je0Q@mail.gmail.com>
2013-04-09 17:52 ` Maxime Nicco [this message]
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=51645567.7060807@free.fr \
--to=maxime.nicco@free.fr \
--cc=cwillu@cwillu.com \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.