I've reviewed the kernel code, and there are no unexpected changes w.r.t the CACHED_UUID change event. So I don't think we will need any kernel changes which is good.
With the small change to the 60-persistent-storage.rules to not attempt to create a /dev/disk/by-uuid symlink for the backing device; instead we want to only create a /dev/bcache/by-uuid symlink to the bcacheN device (that is associated with the backing device).
OK.
I've reviewed the kernel code, and there are no unexpected changes w.r.t the CACHED_UUID change event. So I don't think we will need any kernel changes which is good.
With the small change to the 60-persistent- storage. rules to not attempt to create a /dev/disk/by-uuid symlink for the backing device; instead we want to only create a /dev/bcache/by-uuid symlink to the bcacheN device (that is associated with the backing device).
# by-label/by-uuid links (filesystem metadata), skip bcache backing,caching devices, handled in 69-bcache.rules FS_TYPE} =="bcache" , GOTO="skip_ fs_uuid_ enc" FS_USAGE} =="filesystem| other|crypto" , ENV{ID_ FS_UUID_ ENC}==" ?*", SYMLINK+ ="disk/ by-uuid/ $env{ID_ FS_UUID_ ENC}" FS_USAGE} =="filesystem| other|crypto" , ENV{ID_ FS_LABEL_ ENC}==" ?*", SYMLINK+ ="disk/ by-label/ $env{ID_ FS_LABEL_ ENC}" skip_fs_ uuid_enc"
ENV{ID_
ENV{ID_
ENV{ID_
LABEL="
And then with my previously proposed changed to 69-bcache.rules in place
https:/ /github. com/g2p/ bcache- tools/pull/ 29/files
The test-case works just fine.