I suspect I have a similar problem to the reporter of this bug. I have
a swap partition that is set up as an encrypted dm device with a random
key, using the cryptsetup package. cryptsetup now has a test that calls
vol_id, which thinks that my partition is vfat:
% sudo /lib/udev/vol_id /dev/hda2
ID_FS_USAGE=filesystem
ID_FS_TYPE=vfat
ID_FS_VERSION=FAT32
ID_FS_UUID=
ID_FS_LABEL=
ID_FS_LABEL_SAFE=
% sudo mount -t vfat /dev/hda2 /mnt/tmp
mount: /dev/hda2: can't read superblock
Inspecting this partition, I see clearly "MSDOS5.0", presumably the
long-preserved remnants of a vfat filesystem. However, since the kernel
refuses to mount the partition as vfat, it seems that vol_id could apply
a stricter check.
I realize that vol_id can never be perfect, since the device metadata
may be consistent with multiple formats. And I agree that device
initialization tools (like mkswap) should zero out part of the device.
But it would still help to make vol_id more exact, because this issue
evidently bites users in practice. Perhaps there could be flags for
quick-and-dirty check versus more complete check.
I can send the strace output from running vol_id on this partition if
somebody would like to look at it.
Andrew
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
