From: Vladimir Panteleev <thecybershadow@gmail.com>
To: linux-btrfs@vger.kernel.org
Subject: Re: "kernel BUG" and segmentation fault with "device delete"
Date: Fri, 5 Jul 2019 07:01:27 +0000 [thread overview]
Message-ID: <29148fbd-c751-bbb4-3d9b-1abf90a26ae6@gmail.com> (raw)
In-Reply-To: <966f5562-1993-2a4f-0d6d-5cea69d6e1c6@gmail.com>
On 05/07/2019 04.39, Vladimir Panteleev wrote:
> The process reached a point where the last missing device shows as
> containing 20 GB of RAID1 metadata. At this point, attempting to delete
> the device causes the operation to shortly fail with "No space left",
> followed by a "kernel BUG at fs/btrfs/relocation.c:2499!", and the
> "btrfs device delete" command to crash with a segmentation fault.
Same effect if I try to use btrfs-replace on the missing device (which
works) and then try to delete it (which fails in the same way).
Also same effect if I try to balance the metadata (balance start -v -m
/mnt/a).
At this point this doesn't look like it is at all related to RAID10 or
btrfs_check_rw_degradable, just a bug somewhere with handling something
weird in the filesystem.
I'm out of ideas, so suggestions welcome. :)
--
Best regards,
Vladimir
next prev parent reply other threads:[~2019-07-05 7:01 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 [this message]
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
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=29148fbd-c751-bbb4-3d9b-1abf90a26ae6@gmail.com \
--to=thecybershadow@gmail.com \
--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