[ale] Examining pre-existing LVM

[Jeff Hubbs]

Yeah, I'm thinking now I shouldn't have run vgcreate; the information in 
the dd'ed files made as described in the article now reflects my vge and 
vgf volume groups.  Where I'm stuck now is that I don't have any devices 
/dev/vge and /dev/vgf and vgscan --mknodes prints out those volume 
groups but makes no new nodes.  One other possibility is that the two 
disks were put in a vg together and I suppose I could re-do vgcreate to 
accomplish that, but I'm still concerned that I won't be able to 
generate a /dev/vgef or whatever.

- Jeff

Giulio (lists) wrote:
> On Thursday 20 March 2008, Jeff Hubbs wrote:
>   
>> I think you mean "vgchange -a y".  The output is:
>>
>>   0 logical volume(s) in volume group "vgf" now active
>>   0 logical volume(s) in volume group "vge" now active
>>   1 logical volume(s) in volume group "vg0" now active
>>
>> Ignore vg0; that's a different volume group.
>>
>> I'd already gone "vgcreate vge /dev/sde1" and "vgcreate vgf
>> /dev/sdf1", hence the vge and vgf.  Where I seem to be stuck is
>> getting LVM2 to "bring up" the LVs in the VGs.
>>     
>
> Yes, "-a y" is correct.
>
> I do not think the vgcreate was needed as you already seemed to have 
> an existing LVM setup on both disks.
>
> The article linked before had some info as to how to extract the LVM 
> header information from the disks. Hopefully it will be still there. 
>
> Giulio  
> _______________________________________________
> Ale mailing list
> Ale at ale.org
> http://mail.ale.org/mailman/listinfo/ale
>
>