From: Martin Steigerwald <martin@lichtvoll.de>
To: Stefan Priebe - Profihost AG <s.priebe@profihost.ag>
Cc: "linux-btrfs@vger.kernel.org" <linux-btrfs@vger.kernel.org>
Subject: Re: runtime btrfsck
Date: Wed, 10 May 2017 09:48:07 +0200 [thread overview]
Message-ID: <1801706.Ls22q1bWhG@merkaba> (raw)
In-Reply-To: <5d86903f-96f8-b61c-16b0-15ba9ac48986@profihost.ag>
Stefan Priebe - Profihost AG - 10.05.17, 09:02:
> I'm now trying btrfs progs 4.10.2. Is anybody out there who can tell me
> something about the expected runtime or how to fix bad key ordering?
I had a similar issue which remained unresolved.
But I clearly saw that btrfs check was running in a loop, see thread:
[4.9] btrfs check --repair looping over file extent discount errors
So it would be interesting to see the exact output of btrfs check, maybe there
is something like repeated numbers that also indicate a loop.
I was about to say that BTRFS is production ready before this issue happened.
I still think it for a lot of setup mostly is, as at least the "I get stuck on
the CPU while searching for free space" issue seems to be gone since about
anything between 4.5/4.6 kernels. I also think so regarding absence of data
loss. I was able to copy over all of the data I needed of the broken
filesystem.
Yet, when it comes to btrfs check? Its still quite rudimentary if you ask me.
So unless someone has a clever idea here and shares it with you, it may be
needed to backup anything you can from this filesystem and then start over from
scratch. As to my past experience something like xfs_repair surpasses btrfs
check in the ability to actually fix broken filesystem by a great extent.
Ciao,
--
Martin
next prev parent reply other threads:[~2017-05-10 7:48 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-02 6:29 runtime btrfsck Stefan Priebe - Profihost AG
2017-05-06 5:56 ` Stefan Priebe - Profihost AG
2017-05-10 7:02 ` Stefan Priebe - Profihost AG
2017-05-10 7:18 ` Roman Mamedov
2017-05-10 7:36 ` Stefan Priebe - Profihost AG
2017-05-10 7:40 ` Hugo Mills
2017-05-10 8:40 ` Stefan Priebe - Profihost AG
2017-05-10 9:08 ` Hugo Mills
2017-05-10 9:20 ` Stefan Priebe - Profihost AG
2017-05-10 9:54 ` Hugo Mills
2017-05-10 11:23 ` Stefan Priebe - Profihost AG
2017-05-10 7:24 ` Marat Khalili
2017-05-10 7:48 ` Martin Steigerwald [this message]
2017-05-10 8:42 ` Stefan Priebe - Profihost AG
2017-05-10 8:52 ` Roman Mamedov
2017-05-11 14:03 ` Duncan
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=1801706.Ls22q1bWhG@merkaba \
--to=martin@lichtvoll.de \
--cc=linux-btrfs@vger.kernel.org \
--cc=s.priebe@profihost.ag \
/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