On Fri, 18 Aug 2006, Kay Sievers wrote: > On Fri, 2006-08-18 at 08:59 -0700, Andrew Pimlott wrote: > > On Fri, Aug 18, 2006 at 02:13:53PM +0200, Kay Sievers wrote: > > > It's almost impossible to make libvolume_id stricter, in most cases, > > > even the kernel mounts a mkswap formatted (and obviously corrupt) fat > > > volume just fine and allows writing to it. > > > > Ok, thanks for the explanation. > > > > > It's mkswap which is horribly broken here and needs to be fixed. > > > > Hopefully the bug I filed with util-linux will produce some change. > > That would be nice. In case you need to argue, the mkfs.ext* tools and > mkfs.reisferfs tools invalidate the start and the end (md raid) of the > volume too, to overwrite old signatures after having the same problems. > > > > You can just use dd and clean the volume before reformatting it. > > > > Right--I've done that to the partition, and now I have no problem. > > Yeah, but it's bad, that we need to do this after that issue is known > for more than a year now. > > Thanks, > Kay
on the same line it would be cool if mkswap checked what it is doing. as currently it doesn't do much: you can easily recover any mkswaped partition. regards -- maks -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
