On 1 December 2017 at 08:18, Duncan <1i5t5.duncan@xxxxxxx> wrote: > > When udev sees a device it triggers > a btrfs device scan, which lets btrfs know which devices belong to which > individual btrfs. But once it associates a device with a particular > btrfs, there's nothing to unassociate it -- the only way to do that on > a running kernel is to successfully complete a btrfs device remove or > replacement... and your replace didn't complete due to error. > > Of course the other way to do it is to reboot, fresh kernel, fresh > btrfs state, and it learns again what devices go with which btrfs > when the appearing devices trigger the udev rule that triggers a > btrfs scan. Or reload the btrfs module. -- To unsubscribe from this list: send the line "unsubscribe linux-btrfs" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
