-
Notifications
You must be signed in to change notification settings - Fork 28
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
UUID is shared between all partitions #130
Comments
@rumblpak thanks for bringing this up, I'm not a btrfs user on my fio drive so haven't encountered this! Afaik UUID_SUB is a btrfs-ism, and is used for volumes, no other FS seems to use it(?). The solution won't work for anyone not using btrfs, as it would return empty. The solution could be to run the UUID_SUB rule before the UUID rule? |
I’m actually a zfs user, still though, I’m just using fdisk to create two partitions and putting zfs on top of that. I feel like there could be a change to help both use-cases. |
@rumblpak today I learned. Never noticed the UUID_SUB with blkid before for my ZFS volumes on Linux. I do think you can add the UUID_SUB, that said it will still execute the UUID rule leaving you with the last entry as the main UUID, which probably is not desirable. In my case when testing it shows an empty for UUID_SUB, so no harm there. Getting the UUID correct icw the UUID_SUB would require some more finagling it seems. |
I do think adding this before the UUID line would fix it for newer versions of udev where the
I've noticed that the symlinks for |
iomemory-vsl/tools/udev/rules.d/60-persistent-fio.rules
Line 38 in 0a12f15
Using this blkid output, all partitions share the same uuid which causes the last partition to be the only partition listed in
/dev/disk/by-uuid
. This could be fixed by using UUID_SUB like this:I'm not 100% sure why this is happening locally to me but that definitely fixes populating
/dev/disk/by-uuid/
for me.The text was updated successfully, but these errors were encountered: