Hello Ryan Harper
>
> This happens in the initramfs for kernels which include bcache module. After the rootfs is
> mounted and we've pivoted into system boot, then the udev cold-plug replay will repeat
> the disk add/change events
I run bcache in Redhat and Centos OS, I haven't met such issue.
I am wondering, if udev cold-plug needs replay, it should also
repeat the bcache change uevent which produced in bcache device
registering, if so, the /dev/bcache/{by-uuid, by-label} should be
also generated.
>
> but when the bcache register method runs a second time and
> finds a backing device, a bcacheN block device already has it open, so the module exits out
> the path of "device already registered" which prevents bcache from calling register_bdev()
> which is the only path where a backing device could call bch_cached_dev_run() which is
> responsible for emitting the KOBJ_CHANGE event which the bcache udev rules use to
> generate the /dev/bcache/{by-uuid, by-label} events.
I am just worry about that, If every disk change uevents triggerd a
bcache device change uevents, there would be a lot of output messages
like "/dev/bcache/{by-uuid, by-label} has existed, and it was
created again..."
Thanks
Tang Junhui
--
To unsubscribe from this list: send the line "unsubscribe linux-bcache" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
