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 > > I prefer not to use a partition table at all if I'm using the whole disk for > LVM.
I just read this from the lvm howto http://tldp.org/HOWTO/LVM-HOWTO/initdisks.html Not Recommended Using the whole disk as a PV (as opposed to a partition spanning the whole disk) is not recommended because of the management issues it can create. Any other OS that looks at the disk will not recognize the LVM metadata and display the disk as being free, so it is likely it will be overwritten. LVM itself will work fine with whole disk PVs. could you explain why it is good to use whole disk for lvm? > > >and separate LVs for /tmp /var /home > > 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 > /usr > /usr/local # For OS migrations. Could you elaborate on this, I'd really like to learn more about your setup. Do you put OS independent stuff in this? > /home > /opt > /srv > /var > /var/tmp # RAID 0 or other "fast" > /var/cache # RAID 0 or other "fast" > /tmp # Usually tmpfs; no LV This setup is intense. > > >and leave enough unassigned PE for later enlargement of certain LV? > > It is much easier to expand a filesystem than to shrink it. This is true > even if you aren't using LVM. I am thinking this is what I need to remember for my next installation. It is really not easy to shrink things... Thanks Boyd, this message helped me alot, -- Zhengquan -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
