You are not logged in.
Pages: 1
[root@killterm3 ~]# modprobe dm-mod
[root@killterm3 ~]# pvcreate --metadatasize 250k /dev/sdf2
Writing physical volume data to disk "/dev/sdf2"
Physical volume "/dev/sdf2" successfully created
[root@killterm3 ~]# vgcreate ultrakid /dev/sdf2
Volume group "ultrakid" successfully created
[root@killterm3 ~]# lvcreate -L 10G ultrakid -n encrypted
/dev/mapper/ultrakid-encrypted: open failed: No such file or directory
/dev/ultrakid/encrypted: not found: device not cleared
Aborting. Failed to wipe start of new LV.
Unable to deactivate open ultrakid-encrypted (254:0)
Unable to deactivate failed new LV. Manual intervention required.
[root@killterm3 ~]# file /dev/mapper/ultrakid-encrypted
/dev/mapper/ultrakid-encrypted: symbolic link to `../dm-0'
[root@killterm3 ~]# file /dev/dm-0
/dev/dm-0: block special
The device is there. What's going on?
Offline
I've looked over your commands and I don't see anything obviously wrong. The only thing that stands out is that you modify the size of the metadata. I wonder if 250k is a sane size? Why are you changing that? You do know that the LVM metadata isn't the same thing as a journal on ext3 or ext4 right? I think the metadata is what delayed any responses here because few, if any of us, are tweaking that parameter and the rest seems okay.
Offline
Yeah, I suppose I'll keep trying. I'm using 250k for metadata to align my LVM2 system to the 128k erase block size my USB flash drive uses.
Offline
Someone else posted about a nearly identical issue here. I suggested he try the verbose and debug flags, but he never responded.
BTW, this is probably all my fault, because I just migrated to LVM and the Universe hates me.
But whether the Constitution really be one thing, or another, this much is certain - that it has either authorized such a government as we have had, or has been powerless to prevent it. In either case, it is unfit to exist.
-Lysander Spooner
Offline
Pages: 1