On Sun, Aug 30, 2009 at 02:48:50AM +0200, Thomas Bächler wrote: > > We already use 1.0.7, the problem only occurs with old volumes, created > by 1.0.6 and older (which probably not everyone wants to wipe out). It's > a legacy we are now carrying around. > Could you add a hack to your userspace to determine which of the 64k at the front of the disk is in use by LUKS, and zap the sectors that aren't (and then set a flag in the LUKS superblock so you only have to do this once)? It could be possible to reorder the detection algorithms to put LUKS ahead of the tests ext2/3/4 (and in the past when I was the sole maintainer of blkid I've done that sort of thing before), but really, depending on that kind of ordering is really a bad idea; it's better to fix a filesystem's utilities to do the right thing at mkfs time and if necessary to do any fixups in the filesystem's fsck utility. Yes, I know that LUKS isn't properly speaking a filesystem, but the same principle holds. - Ted -- To unsubscribe from this list: send the line "unsubscribe util-linux-ng" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
