On Fri, 2009-04-17 at 14:09 +0000, Julien Plissonneau Duquene wrote: > > The software is working exactly as designed. > > Probably not. > >From the /usr/share/doc/udev/NEWS.gz file:
Libvolume_id now always probes for all known filesystems, and does not stop at the first match. Some filesystems are marked as "exclusive probe", and if any other filesytem type matches at the same time, libvolume_id will, by default, not return any probing result. This is intended to prevent mis-detection with conflicting left-over signatures found from earlier file system formats. That way, we no longer depend on the probe-order in case of multiple competing signatures. In some setups the kernel allows to mount a volume with just the old filesystem signature still in place. This may damage the new filesystem and cause data-loss, just by mounting it. Because volume_id can not decide which one the correct signature is, the wrong signatures need to be removed manually from the volume, or the volume needs to be reformatted, to enable filesystem detection and possible auto-mounting. > Even then, if there is a design goal that states "when > there are two possible UUID do not report ANY" that design goal is plain > wrong and must go. > Feel free to discuss this with Upstream... subscribe kay-sievers Scott -- Scott James Remnant sc...@canonical.com -- udev fails to identify crypt_LUKS swap partition by uuid https://bugs.launchpad.net/bugs/362315 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
