On Thu, Jun 04, 2009 at 07:07:58AM +0100, Bhasker C V wrote: > On Wed, 3 Jun 2009, Zhengquan Zhang wrote: > >> On Thu, Jun 04, 2009 at 08:23:05AM +1000, Alex Samad wrote: >>> On Wed, Jun 03, 2009 at 01:46:27PM -0500, Boyd Stephen Smith Jr. wrote: >>>> In <20090603174408.ga25...@m364d1.ece.northwestern.edu>, Zhengquan Zhang >>>> wrote: >>>>> Can I say the best practice for lvm is to create a single partition for >>>>> the harddrive and single PV on it >>> >>> [snip] >>> >>>> You definitely want separate LVs for any partition (non-system) users can >>>> write to, to avoid running out of space on your / partition. I usually go >>>> overboard and have separate partitions for: >>>> /boot # If / is on LVM; not LV >>> >>> I would suggest to never put / or /boot on a lvm partition and at most >>> to put it on a raid1 set. Why incase something goes wrong, raid1 i much >>> easier to dissect then lvm (and especially lvm on raid) >> >> Does that mean, lvm on raid is easier to dissect than lvm alone? > Be it RAID or not. The easy and best-near-resurrection method > would be to somehow backup the /etc/lvm periodically. This will help > you to restore the LVM VGs and LVs safely.
I already do daily backup of /etc, etc.. Thanks for pointing out the importance of this though, I never thought /etc/lvm is that useful. Zhengquan -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
