This content has been marked as final. Show 3 replies
897966 wrote:This only works if you have a Storage Connect plugin that can work with your storage to actually resize the LUN.
I use a FibreChannel Storage Array correctly assigned to VM Server and I need to expand the size of the LUN I use as repository for VM's.
I've tryed expanding it directly from the web interface provided with the Storage Array resulting the VM server crashed and I needed to reinstall it because, I suppose, this procedure it's not correct.
What is the correct procedure to expand the FCP LUN size and make the VM servers and the VM Manager correctly recnognize the expanded LUN?There isn't one for an unmanaged LUN. The easiest option is to create a new LUN and have multiple storage repositories. Otherwise, you will need to resize the LUN on the FC-SAN, make sure the servers all see the resized LUN (which may require a rolling reboot depending on the HBAs in your servers) and then use tunefs.ocfs2 to resize the volume.
thank you for the answers.
I've verified that the correct way to do this resize is to unmount the ocfs2 filesystem from the Oracle VM servers, resize the lun from the Storage Array management Console and then mount again the filesystem on the Oracle VM servers.
I've managed to make the Oracle VM Servers recognize the expanded LUN but I'm NOT unable to mount it back again as ocfs2 filesystem
My problem is how to make the correct resize of the ocfs2 partition?? Do I need to stop the ocfs2 service too?? Can someone suggest me the caorrect procedure including the resize procedure using fdisk???
Thanks in advance!! ;)
Here are the commands I use:
1) mounted.ocfs2 -f
/dev/mapper/3600508b40008e2000000a000009d0000 o2cb 4c9751b019e84c0f G oraclevmsrv *<-FILESYSTEM LUN IS CORRECTLY WORKING*
/dev/mapper/3600508b40008e2000000a00000b10000 o2cb 4c9751b019e84c0f G Not mounted *<-REPOSITORY LUN IS NOT MOUNTED*
2) cat /etc/mtab
/dev/mapper/3600508b40008e2000000a000009d0000 /poolfsmnt/0004fb00000500005bdcb6a81a0d6011 ocfs2 rw,_netdev,heartbeat=global 0 0 *<-FILESYSTEM LUN IS CORRECTLY WORKING*
3) mount.ocfs2 /dev/mapper/3600508b40008e2000000a00000b10000 /OVS/Repositories/
mount.ocfs2: Device or resource busy while mounting /dev/mapper/3600508b40008e2000000a00000b10000 on /OVS/Repositories/. Check 'dmesg' for more information on this error.
[ 86.767438] o2hb: Heartbeat started on region 0004FB00000500005BDCB6A81A0D6011 (dm-0)
[ 87.058717] OCFS2 1.8.0
[ 87.070657] o2dlm: Joining domain 0004FB00000500005BDCB6A81A0D6011 ( 0 ) 1 nodes
[ 87.093002] ocfs2: Mounting device (253,0) on (node 0, slot 0) with ordered data mode.
[ 87.184846] o2dlm: Joining domain ovm ( 0 ) 1 nodes
[ 88.771347] o2hb: Region 0004FB00000500005BDCB6A81A0D6011 (dm-0) is now a quorum device
[ 255.987308] o2dlm: Leaving domain ovm
[ 255.988170] o2dlm: Joining domain ovm ( 0 ) 1 nodes
[ 930.837688] o2dlm: Joining domain 0004FB0000050000CD3EE5CACD23D92A ( 0 ) 1 nodes
[ 935.251307] o2dlm: Leaving domain 0004FB0000050000CD3EE5CACD23D92A