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:35:23 +0200 [thread overview]
Message-ID: <ohlcn5$gm5$1@blaine.gmane.org> (raw)
In-Reply-To: <CAJCQCtQj1-0Nxm9cp16gjjROq7yhU1-sThOEcTR4gwcWRRhLmA@mail.gmail.com>
Op 12-06-17 om 01:00 schreef Chris Murphy:
> On Sun, Jun 11, 2017 at 4:13 AM, Koen Kooi <koen@dominion.thruhere.net> wrote:
>>
>>> Op 11 jun. 2017, om 12:05 heeft Koen Kooi <koen@dominion.thruhere.net> het volgende geschreven:
>>>
>>>>
>>>> Op 11 jun. 2017, om 06:20 heeft Chris Murphy <lists@colorremedies.com> het volgende geschreven:
>>>>
>>>> On Fri, Jun 9, 2017 at 1:57 PM, Hugo Mills <hugo@carfax.org.uk> wrote:
>>
>> [..]
>>
>>>> I'd say take a btrfs-image and put it up somewhere and also file a
>>>> bug. The fsck should not crash.
>>>
>>> I’ll create a bugzilla account and file a bug for that.
>>
>> Done: https://bugzilla.kernel.org/show_bug.cgi?id=196031
>>
>> Btrfs-image is still running, will put it online when it has finished. It’s already 1.2G:
>>
>> koen@beast:~$ du -ms /data/backup/btrfs.img
>> 1205 /data/backup/btrfs.img
>
> Hopefully you're using -s -t4 -c9 but if not you can at least compress
> it after the fact but that takes even longer.
I wasn't using '-s', after I did it and ran it again it shrunk from 14GiB to 733MiB:
https://dominion.thruhere.net/btrfs.img
xz -9 -e wouldn't only compressed that 14GiB file to 13.99GiB, so I wonder why '-s' seems to make such a difference.
regards,
Koen
next prev parent reply other threads:[~2017-06-12 6:35 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 [this message]
2017-06-11 22:58 ` Chris Murphy
2017-06-12 5:18 ` Koen Kooi
2017-06-12 6:12 ` Koen Kooi
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='ohlcn5$gm5$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 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.