From: Qu Wenruo <quwenruo.btrfs@gmx.com>
To: Vladimir Panteleev <thecybershadow@gmail.com>,
linux-btrfs@vger.kernel.org
Subject: Re: "kernel BUG" and segmentation fault with "device delete"
Date: Sat, 6 Jul 2019 13:51:38 +0800 [thread overview]
Message-ID: <4a7c1c7b-bc1e-4aba-7a9d-581c0272aa86@gmx.com> (raw)
In-Reply-To: <8c221f86-b550-fcd6-aef1-13570270a559@gmail.com>
[-- Attachment #1.1: Type: text/plain, Size: 786 bytes --]
On 2019/7/6 下午1:13, Vladimir Panteleev wrote:
[...]
>> I'm not sure if it's the degraded mount cause the problem, as the
>> enospc_debug output looks like reserved/pinned/over-reserved space has
>> taken up all space, while no new chunk get allocated.
>
> The problem happens after replace-ing the missing device (which succeeds
> in full) and then attempting to remove it, i.e. without a degraded mount.
>
>> Would you please try to balance metadata to see if the ENOSPC still
>> happens?
>
> The problem also manifests when attempting to rebalance the metadata.
Have you tried to balance just one or two metadata block groups?
E.g using -mdevid or -mvrange?
And did the problem always happen at the same block group?
Thanks,
Qu
>
> Thanks!
>
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next prev parent reply other threads:[~2019-07-06 5:54 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-07-05 4:39 "kernel BUG" and segmentation fault with "device delete" Vladimir Panteleev
2019-07-05 7:01 ` Vladimir Panteleev
2019-07-05 9:42 ` Andrei Borzenkov
2019-07-05 10:20 ` Vladimir Panteleev
2019-07-05 21:48 ` Chris Murphy
2019-07-05 22:04 ` Chris Murphy
2019-07-05 21:43 ` Chris Murphy
2019-07-06 0:05 ` Vladimir Panteleev
2019-07-06 2:38 ` Chris Murphy
2019-07-06 3:37 ` Vladimir Panteleev
2019-07-06 17:36 ` Chris Murphy
2019-07-06 5:01 ` Qu Wenruo
2019-07-06 5:13 ` Vladimir Panteleev
2019-07-06 5:51 ` Qu Wenruo [this message]
2019-07-06 15:09 ` Vladimir Panteleev
2019-07-20 10:59 ` Vladimir Panteleev
2019-08-08 20:40 ` Vladimir Panteleev
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=4a7c1c7b-bc1e-4aba-7a9d-581c0272aa86@gmx.com \
--to=quwenruo.btrfs@gmx.com \
--cc=linux-btrfs@vger.kernel.org \
--cc=thecybershadow@gmail.com \
/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