OK, I got it to work using your workaround. Thanks, Stuart.
NEXT QUESTION...
How do I get LVM to put all the extents of the ramdisk BEFORE any of the extents of the raid array? Even if I list the pvs, ramdisk first, in the lvcreate command and/or start with the ramdisk in a vgcreate followed by adding the raid array in a vgextend... it always ignores the ramdisk and only assigns extents from the raid array. (I suppose it is putting the ramdisk at the end, where it is useless for my purposes.)
TIA,
Larry
On 5/12/08, Larry Dickson <ldickson@cuttedge.com> wrote:
I got the workaround - it crossed in the mail.However, let me follow up your (and Stuart's) point. Are you saying that an unmounted LVM volume will mess up the boot, even if the volume in question is not mapped to boot or /? I was proceeding under the assumption that LVM would be happy to sew the pieces together again later, even if the data in them is trashed.Larry
On 5/12/08, Charles Marcus <CMarcus@media-brokers.com> wrote:On 5/12/2008, Larry Dickson (ldickson@cuttedge.com) wrote:
> A way around all this overprotectiveness would be highly appreciated.
It is not 'over-protectiveness'... I would call it 'highly *desired*
protectiveness'.
A workaround has already been provided...
--
Best regards,
Charles
_______________________________________________
linux-lvm mailing list
linux-lvm@redhat.com
https://www.redhat.com/mailman/listinfo/linux-lvm
read the LVM HOW-TO at http://tldp.org/HOWTO/LVM-HOWTO/
_______________________________________________ linux-lvm mailing list linux-lvm@redhat.com https://www.redhat.com/mailman/listinfo/linux-lvm read the LVM HOW-TO at http://tldp.org/HOWTO/LVM-HOWTO/
