Dermot Paikkos wrote: > Hi, > >> -----Original Message----- >> From: urgrue [mailto:urgrue@xxxxxxxxxxx] >> Sent: 19 August 2008 11:27 >> >> Correct. You dont expand the PV, you make a new partition with fdisk > in >> the new space and then create a pv on it, add it to the vg with >> vgextend, and the lvextend and then ext2online/resize2fs/whatever to >> expand the fs. > >>> Right now I am considering deleting the RAID container completely > and >>> re-creating and restoring rather than waste any more time but before >>> I do I'd like to hear it if sounds like the procedure is bound to >>> fail. >>> >>> At the moment I think the best I can hope for is that the volume > will >>> be fine but the extra disk-space will never be seen? >>> >> if you dont see the new space in fdisk, you might have to reboot, or > do >> echo "- - -" > /sys/class/scsi_host/hostXXX/scan. > > Do you mean the new space on the expanded RAID logical drive or a > completely new RAID container? > I mean the new space on the existing RAID drive. If you used the RAID tools to expand the existing array onto the same logical drive as before, then from linux's point of view the underlying disk just "got bigger", and it may require a reboot or the scsi scan i mentioned to get linux to notice. If you made a new logical drive, then it will appear as a new disk (in linux). This too will require either a reboot or the scsi scan. Either way, you then have to use fdisk to make a partition on the new space and then pvcreate etc. -- To unsubscribe from this list: send the line "unsubscribe linux-admin" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
