The kernel uevent for CACHED_UUID isn't the right way to go long term; all of the information we want is present in the superblock of the devices as they are probed; If we have a 69-bcache.rules with a helper that uses bcache-super-show; we could drop the Ubuntu sauce patch we have; it's just noise (and now it's somewhat unreliable, this bug shows that).
@Rafael
It's in both places:
https:/ /github. com/koverstreet /bcache- tools/pull/ 1
I can update the PR there as well; though I don't think upstream cares as Kent's working on bcachefs instead of bcache AFAICT.
> I see that you are trying to come up with something nor relying in the kernel fix (to throw the variables again after pivot root, etc..)
I think after the systemd discussion upstream:
https:/ /github. com/systemd/ systemd/ pull/16317
The kernel uevent for CACHED_UUID isn't the right way to go long term; all of the information we want is present in the superblock of the devices as they are probed; If we have a 69-bcache.rules with a helper that uses bcache-super-show; we could drop the Ubuntu sauce patch we have; it's just noise (and now it's somewhat unreliable, this bug shows that).