From: Hugo Mills <hugo-lkml@carfax.org.uk>
To: Tomasz Chmielewski <mangoo@wpkg.org>
Cc: linux-btrfs <linux-btrfs@vger.kernel.org>
Subject: Re: "open_ctree failed", unable to mount the fs
Date: Fri, 7 Jan 2011 19:09:30 +0000 [thread overview]
Message-ID: <20110107190930.GA24059@carfax.org.uk> (raw)
In-Reply-To: <4D27631B.9020700@wpkg.org>
[-- Attachment #1: Type: text/plain, Size: 1201 bytes --]
On Fri, Jan 07, 2011 at 08:01:47PM +0100, Tomasz Chmielewski wrote:
> I got a "power cycle", after which I'm no longer able to mount btrfs
> filesystem:
>
>
> device fsid xxxxx-yyyyy devid 1 transid 169686 /dev/vda3
> device fsid xxxxx-yyyyy devid 1 transid 169686 /dev/vda3
> parent transid verify failed on 3260289024 wanted 169686 found 169685
> parent transid verify failed on 3260289024 wanted 169686 found 169685
> parent transid verify failed on 3260289024 wanted 169686 found 169685
> btrfs: open_ctree failed
>
>
> Tried to get that mounted with 2.6.35 and 2.6.37, without success.
>
> Is there a way to fix it?
The forthcoming[1] btrfsck tool should handle that particular
error, I believe.
To prevent it from happening again, ensure that you have working
barriers on your disks, or that you turn off write caching on the
drives at every boot.
Hugo.
[1] out "real soon now"
--
=== Hugo Mills: hugo@... carfax.org.uk | darksatanic.net | lug.org.uk ===
PGP key: 515C238D from wwwkeys.eu.pgp.net or http://www.carfax.org.uk
--- Well, sir, the floor is yours. But remember, the ---
roof is ours!
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 190 bytes --]
next prev parent reply other threads:[~2011-01-07 19:09 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-01-07 19:01 "open_ctree failed", unable to mount the fs Tomasz Chmielewski
2011-01-07 19:09 ` Hugo Mills [this message]
2011-01-07 20:02 ` 'open_ctree failed', " Ken D'Ambrosio
2011-01-07 20:31 ` cwillu
-- strict thread matches above, loose matches on Subject: below --
2011-01-07 19:25 "open_ctree failed", " Tomasz Chmielewski
2011-01-07 19:47 ` cwillu
[not found] ` <AANLkTik3GZVTwco+4PNFriB0+t_U=e+dH0UOgK_3P9D5@mail.gmail.com>
2011-01-07 20:01 ` Tomasz Chmielewski
2011-01-07 20:18 ` cwillu
2011-01-07 20:44 ` Tomasz Chmielewski
[not found] <S1750921Ab1CIXPz/20110309231555Z+1799@vger.kernel.org>
2011-03-09 23:28 ` Tomáš Thiemel
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=20110107190930.GA24059@carfax.org.uk \
--to=hugo-lkml@carfax.org.uk \
--cc=linux-btrfs@vger.kernel.org \
--cc=mangoo@wpkg.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).