From: Koen Kooi <koen@dominion.thruhere.net>
To: linux-btrfs@vger.kernel.org
Subject: Re: Filesystem won't mount (open_ctree failed) or repair (BUG_ON)
Date: Mon, 12 Jun 2017 08:12:05 +0200 [thread overview]
Message-ID: <ohlbbf$v35$1@blaine.gmane.org> (raw)
In-Reply-To: <CAJCQCtS=S1jkcLtAyC18iNMQehsXMMFytvPz05YwMcs+JHLEag@mail.gmail.com>
Op 12-06-17 om 00:58 schreef Chris Murphy:
[..]
> Also worth trying btrfs check --mode=lowmem. This doesn't repair but
> is a whole new implementation so it might find the source of the
> problem better than the current fsck.
I ran it under 'catchsegv' to give more data where it segfaults, here's the log:
https://dominion.thruhere.net/btrfsck-lowmem.txt.gz
It's 688K compressed and 16MiB uncompressed.
regards,
Koen
prev parent reply other threads:[~2017-06-12 6:12 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-06-09 19:12 Filesystem won't mount (open_ctree failed) or repair (BUG_ON) Koen Kooi
2017-06-09 19:57 ` Hugo Mills
2017-06-09 20:10 ` Koen Kooi
2017-06-11 4:20 ` Chris Murphy
2017-06-11 10:05 ` Koen Kooi
2017-06-11 10:13 ` Koen Kooi
2017-06-11 23:00 ` Chris Murphy
2017-06-12 6:35 ` Koen Kooi
2017-06-11 22:58 ` Chris Murphy
2017-06-12 5:18 ` Koen Kooi
2017-06-12 6:12 ` Koen Kooi [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='ohlbbf$v35$1@blaine.gmane.org' \
--to=koen@dominion.thruhere.net \
--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