Most applications which play with these sort of things do so by making sure the declared size of the file system (which has to be read from the file system) matches the actual size of the device. Otherwise, an explicit EVMS meta-data check at the end of the original file system may be fine.
** Description changed: Binary package hint: nautilus This bug may in fact be part of HAL. - Nautilus for me lists two volumes which I am allowed to mount: 245 MB - Volume and a 59.6GB Volume. Double clicking these icons in Nautilus - CORRUPTS MY DATA. + Nautilus for me lists a volume which I am allowed to mount: 245 MB + Volume. Double clicking this icon in Nautilus CORRUPTS MY DATA. The 245 MB Volume is representative of /dev/sda2, which is in actuality - an EVMS volume which is ALREADY MOUNTED as /dev/evms/boot. The 59.6GB - Volume is the "first 59.6GB" of a 400GB XFS file system which spans - /dev/sda4 and a few different MD devices. This is ALREADY MOUNTED as - /dev/evms/shares. + an EVMS volume which is ALREADY MOUNTED as /dev/evms/boot. This is DANGEROUS. ** Changed in: nautilus (Ubuntu) Sourcepackagename: nautilus => hal -- allows mounting of partitions that are already mounted (corruption!) https://launchpad.net/bugs/76177 -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
