So we have actually two bugs here:
- for some reason my blkid cache borke and was never fixed subsequently; blkid 
correctly detects the proper type for devices when I disable the cache, but it 
seems to trust an existing cache for the device type; here this is clearly 
incorrect and breaks; I don't know what the cache is meant for, so I guess we 
need to include the e2fsprogs upstream people in the loop here
- blkid's -w flag is unimplemented/broken; I don't really care, just spotted it 
while debugging

-- 
Wrong type in blkid cache causes fsck on boot to fail
https://bugs.launchpad.net/bugs/316322
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.

-- 
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

Reply via email to