From: Frankie Fisher <frankie@terrorise.me.uk>
To: linux-btrfs@vger.kernel.org
Subject: Re: open_ctree failed on 3.16.0
Date: Fri, 01 Aug 2014 13:45:19 +0100 [thread overview]
Message-ID: <53DB8BDF.9020509@terrorise.me.uk> (raw)
In-Reply-To: <pan$aa380$cfda0300$d7b3a968$e36385c0@cox.net>
[-- Attachment #1: Type: text/plain, Size: 1234 bytes --]
On 01/08/14 12:29, Duncan wrote:
> Frankie Fisher posted on Fri, 01 Aug 2014 10:58:39 +0100 as excerpted:
>
>> A circuit breaker failed a few times and now I can't mount my btrfs
>> volume - it fails with open_ctree failed:
>
>>
>> What are the next steps I should try? Should I try btrfs-zero-log? Or
>> should I try btrfsck? Or something else?
>
> The standard advice concerning btrfs check (aka btrfsck) is that running
> it without --repair or similar won't hurt as in that case it's read-only,
> but by the same token, it won't help, except possibly to give you an idea
> of what's wrong.
fwiw, this is the output of btrfsck:
http://cwillu.com:8080/86.136.116.221/2
> <snip helpful advice>
Thanks for the helpful info, I will work through it. It would be nice to
be able to recover the filesystem, but if I can't recover the filesystem
it wouldn't be the end of the world as I have a backup from a few days
before the incident. Even if I can't recover the filesystem, if
reporting this issue helps btrfs be more robust in the future that would
be a good outcome. To that end I have made a copy of the filesystem with
btrfs-image which I can supply if necessary.
Regards,
Frankie Fisher
[-- Attachment #2: S/MIME Cryptographic Signature --]
[-- Type: application/pkcs7-signature, Size: 4261 bytes --]
prev parent reply other threads:[~2014-08-01 12:45 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-08-01 9:58 open_ctree failed on 3.16.0 Frankie Fisher
2014-08-01 11:29 ` Duncan
2014-08-01 12:45 ` Frankie Fisher [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=53DB8BDF.9020509@terrorise.me.uk \
--to=frankie@terrorise.me.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 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.