From: devel@roosoft.ltd.uk
To: "linux-btrfs@vger.kernel.org" <linux-btrfs@vger.kernel.org>
Subject: Re: Problems balancing BTRFS
Date: Fri, 22 Nov 2019 13:20:10 +0000 [thread overview]
Message-ID: <e382e662-b09f-c9f3-e589-44560a7b9b97@casa-di-locascio.net> (raw)
In-Reply-To: <1de2144f-361a-4657-662f-ac1f17c84b51@gmx.com>
On 22/11/2019 13:10, Qu Wenruo wrote:
>
> On 2019/11/22 下午8:37, devel@roosoft.ltd.uk wrote:
>> So been discussing this on IRC but looks like more sage advice is needed.
> You're not the only one hitting the bug. (Not sure if that makes you
> feel a little better)
Hehe.. well always help to know you are not slowly going crazy by oneself.
>>
>> The csum error is from data reloc tree, which is a tree to record the
>> new (relocated) data.
>> So the good news is, your old data is not corrupted, and since we hit
>> EIO before switching tree blocks, the corrupted data is just deleted.
>>
>> And I have also seen the bug just using single device, with DUP meta and
>> SINGLE data, so I believe there is something wrong with the data reloc tree.
>> The problem here is, I can't find a way to reproduce it, so it will take
>> us a longer time to debug.
>>
>>
>> Despite that, have you seen any other problem? Especially ENOSPC (needs
>> enospc_debug mount option).
>> The only time I hit it, I was debugging ENOSPC bug of relocation.
>>
As far as I can tell the rest of the filesystem works normally. Like I
show scrubs clean etc.. I have not actively added much new data since
the whole point is to balance the fs so a scrub does not take 18 hours.
So really I am not sure what to do. It only seems to appear during a
balance, which as far as I know is a much needed regular maintenance
tool to keep a fs healthy, which is why it is part of the
btrfsmaintenance tools
Are there some other tests to try and isolate what the problem appears
to be?
Thanks.
--
==
D LoCascio
Director
RooSoft Ltd
next prev parent reply other threads:[~2019-11-22 13:41 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-22 12:37 Problems balancing BTRFS devel
2019-11-22 13:10 ` Qu Wenruo
2019-11-22 13:20 ` devel [this message]
2019-11-22 13:56 ` Qu Wenruo
2019-11-22 14:07 ` devel
2019-11-22 15:32 ` devel
2019-11-23 0:09 ` Qu Wenruo
2019-11-23 12:53 ` devel
2019-11-23 16:20 ` Chris Murphy
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=e382e662-b09f-c9f3-e589-44560a7b9b97@casa-di-locascio.net \
--to=devel@roosoft.ltd.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 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).