Hi,
my iscsi volumes are all lvm created :-) But the server(s) dont have the device nodes any more.
So how may I create tham again? Or ist there an lvm-tool (option) to do this for me?
e.g. for:
--- Logical volume --- LV Name /dev/VGJBOD01/lvol0 VG Name VGJBOD01 LV UUID IK35sK-bL9B-MeMv-2co6-XtOd-RCxK-lUpank LV Write Access read/write LV Status NOT available LV Size 4,77 TB Current LE 1251375 Segments 1 Allocation inherit Read ahead sectors auto
Any hint would make my happy!
Thanks a lot an best regards,
Götz
On 11/12/2009 12:47 PM, Götz Reinicke - IT-Koordinator wrote:
my iscsi volumes are all lvm created :-) But the server(s) dont have the device nodes any more.
once the blockdev is visible to the os:
vgchange -ay
Karanbir Singh wrote:
On 11/12/2009 12:47 PM, Götz Reinicke - IT-Koordinator wrote:
my iscsi volumes are all lvm created :-) But the server(s) dont have the device nodes any more.
once the blockdev is visible to the os:
vgchange -ay
You me lvchange -ay ?
What I do is vgimport then lvchange -ay
Here's the init script I use to mount SAN LVM volumes -
http://portal.aphroland.org/~aphro/mount_san.init
Back from RHEL 4.x days when it didn't support iSCSI for mounting at boot, I still use it even now since it works, so have no reason to change.
nate
On 11/12/2009 01:03 PM, nate wrote:
vgchange -ay
You me lvchange -ay ?
no, I mean 'vgchange -ay'. That will do whatever is needed to bring the /dev/mapper/<VolGroup/<lv's> up and ensure the kernel is aware of them.
Karanbir Singh schrieb:
On 11/12/2009 12:47 PM, Götz Reinicke - IT-Koordinator wrote:
my iscsi volumes are all lvm created :-) But the server(s) dont have the device nodes any more.
once the blockdev is visible to the os:
vgchange -ay
Thanks a lot and a thousand kotaus to you. You saved my day!
I'm back online ...
Cheers,
Götz