We use LVM on our servers and although we have yet to have a crash (I
know it's coming) my understanding is the same as yours.

However, we build our LVMs on a RAID5 set, so that mitigates the problem
somewhat. We can swap out a problematic drive without issue.

I highly recommend against booting into an LVM, however. Assuming you
have enough space, a small 80GB drive (or whatever the smallest that you
can buy now) makes a good boot/OS drive. That way you can hedge your
bets for the machine booting even if and when the LVM becomes messed up.

J

On Fri, 2007-03-09 at 09:01 -0500, R A L Carter wrote:
> Hi Folks,
> 
> Does anyone have experience with the Logical Volume Manager (LVM)?  From what 
> I read it seems to solve the problem of finding out,too late, that some of 
> the partitions on you HD are too small and others are too big. 
> 
> However, it also seems to give up one of the big advantages of partitioning: 
> if one logical volume (virtual partition) within a volume group (a set of 
> logical volumes) becomes corrupted then it seems to me that the whole of the 
> volume group is corrupted.  If this is correct then logical partitions are 
> not really protected from corruption of other logical partitions in the same 
> volume group.
> 
> Does this sound right?
> 
> Robin
> 
> _______________________________________________
> clug-talk mailing list
> [email protected]
> http://clug.ca/mailman/listinfo/clug-talk_clug.ca
> Mailing List Guidelines (http://clug.ca/ml_guidelines.php)
> **Please remove these lines when replying
> 
-- 
Key fingerprint: BDE0 DE52 B8C0 0CDF 7653 E5A2 D861 7877 0D3B 813E
http://www.jonwatson.ca
+1.403.770.2837

"Trying to learn to hack on a DOS or Windows machine or under MacOS is
like trying to learn to dance while wearing a body cast" - ESR



_______________________________________________
clug-talk mailing list
[email protected]
http://clug.ca/mailman/listinfo/clug-talk_clug.ca
Mailing List Guidelines (http://clug.ca/ml_guidelines.php)
**Please remove these lines when replying

Reply via email to