Patrik Lundquist posted on Fri, 01 Dec 2017 10:29:43 +0100 as excerpted: > On 1 December 2017 at 08:18, Duncan <1i5t5.dun...@cox.net> 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.
Thanks. Yes. With a monolithic kernel I tend to forget about that (and as I have a btrfs root it wouldn't be possible anyway), but indeed, unloading/reloading the btrfs kernel module clears the btrfs device state tracking as effectively as a reboot. Good point! =:^) -- Duncan - List replies preferred. No HTML msgs. "Every nonfree program has a lord, a master -- and if you use the program, he is your master." Richard Stallman -- To unsubscribe from this list: send the line "unsubscribe linux-btrfs" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
