From: Vladimir Panteleev <thecybershadow@gmail.com>
To: Qu Wenruo <quwenruo.btrfs@gmx.com>, linux-btrfs@vger.kernel.org
Subject: Re: "kernel BUG" and segmentation fault with "device delete"
Date: Sat, 6 Jul 2019 15:09:45 +0000 [thread overview]
Message-ID: <961c2cca-8e06-fb74-2462-d2d1eb014193@gmail.com> (raw)
In-Reply-To: <4a7c1c7b-bc1e-4aba-7a9d-581c0272aa86@gmx.com>
[-- Attachment #1.1: Type: text/plain, Size: 1111 bytes --]
On 06/07/2019 05.51, Qu Wenruo wrote:
>> 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?
If I use -mdevid with the device ID of the device I'm trying to remove
(2), I see the crash.
If I use -mvrange with a range covering one byte past a problematic
virtual address, I see the crash.
Not sure if you had anything else / specific in mind. Here is a log of
my experiments so far:
https://dump.thecybershadow.net/da241fb4b6e743b01a7e9f8734f70d6e/scratch.txt
> And did the problem always happen at the same block group?
Upon reviewing my logs, it looks like for "device remove" it always
tries to move block group 1998263943168 first, upon which it crashes.
For "balance", it seems to vary - looks like there is at least one other
problematic block group at 48009543942144.
Happy to do more experiments or test kernel patches. I have a VM set up
with a COW view of the devices, so I can do destructive tests too.
--
Best regards,
Vladimir
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next prev parent reply other threads:[~2019-07-06 15:09 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
2019-07-06 15:09 ` Vladimir Panteleev [this message]
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=961c2cca-8e06-fb74-2462-d2d1eb014193@gmail.com \
--to=thecybershadow@gmail.com \
--cc=linux-btrfs@vger.kernel.org \
--cc=quwenruo.btrfs@gmx.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;
as well as URLs for NNTP newsgroup(s).