I was finally able to remove the missing device. I updated the bug report, but in case anyone else has this problem I wanted to update here as well.
I deleted all snapshot subvolumes on the pool (between 20 and 30), and was able to delete the missing device then without issue. This took two tries, because the first time I did not wait for btrfs-cleanup to finish actually deleting the subvolumes (as it does this in the background.) The second time I deleted the subvolumes then waited until all disk activity (reported by iotop) had ceased, and re-mounted the pool to be sure. After that the rebalance/delete worked without issue. I am not certain if this is because of a bug with rebalancing snapshots or because the some bad data that was causing the segfault just happened to be in the snapshots. On Tue, Jul 7, 2015 at 12:45 PM, David Wilhelm <[email protected]> wrote: > Thanks. I've submitted it as issue 101141 > > https://bugzilla.kernel.org/show_bug.cgi?id=101141 > > >> That looks like the kind of thing you need a developer for. You've >> already reported it here, but sticking a copy of what you've >> discovered so far into bugzilla.kernel.org may help it not to get >> lost. >> >> Hugo. >> >> -- >> Hugo Mills | "I don't like the look of it, I tell you." >> hugo@... carfax.org.uk | "Well, stop looking at it, then." >> http://carfax.org.uk/ | >> PGP: E2AB1DE4 | The >> Goons -- To unsubscribe from this list: send the line "unsubscribe linux-btrfs" in the body of a message to [email protected] More majordomo info at http://vger.kernel.org/majordomo-info.html
