<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<meta content="text/html;charset=ISO-8859-1" http-equiv="Content-Type">
</head>
<body bgcolor="#ffffff" text="#000000">
<font face="Arial">Thanks for the great help David. I will look at the
red hat example site and possibly consider suse. In the meantime I
found a good how to
<a class="moz-txt-link-freetext" href="http://www.linuxsa.org.au/tips/disk-partitioning.html">http://www.linuxsa.org.au/tips/disk-partitioning.html</a> what do you think
of his partition choices for workstation setup example at end? He
doesn't list a swap partition in there but i guess it's because that
goes without saying and it's always twice the size of your RAM right?<br>
<br>
btw - I was going to try LV setup on Kubuntu and use the evms gui to
administer the thing.<br>
<br>
Rob<br>
</font><br>
<a class="moz-txt-link-abbreviated" href="mailto:david.harrison@stress-free.co.nz">david.harrison@stress-free.co.nz</a> wrote:
<blockquote cite="mid2B57918B-AA3C-4595-AF1C-EE3E063C8EF2@stress-free.co.nz" type="cite">
<div>
<div>On 26/10/2006, at 3:39 PM, Rob Collins wrote:</div>
<br class="Apple-interchange-newline">
<blockquote type="cite"><font face="Arial">sorry, slip of hand, /boot
should have been written simply "/". Thanks for the advice, leaving
10mb spare sounds like sound tip, wasn't aware of ext3 shrink problem.
Does this also mean that I will have problems resizing up and down my
ext3 LV's? If that's the case, this defeats the whole reason I'm
trying to use LVM. </font></blockquote>
<br>
</div>
<div>This is a good Red Hat article on resizing LVM with ext3:</div>
<div><a href="http://kbase.redhat.com/faq/FAQ_96_4842.shtm">http://kbase.redhat.com/faq/FAQ_96_4842.shtm</a></div>
<div><br class="khtml-block-placeholder">
</div>
<div>Resizing LVM upwards is not too much of an issue but I have had
random issues when shrinking that have either been traced back to LVM
itself or a corruption in the overlaid filesystem. I've found shrinking
is not really an issue because in reality it's very rare that you are
going to shrink a filesystem if you start out small and grow it to suit
your needs.</div>
<div><br class="khtml-block-placeholder">
</div>
<div>I find it generally better to work with LVM on a functional
basis, for example 'server-files', 'video', 'user-data' rather than
thinking in terms of /usr or /home.</div>
<div>For example the 'user-data' volume would mount onto /home and
'video' volume on /home/video.</div>
<div>Once you think of it like that you'll may find determining the
'correct' size of your volumes a lot easier.</div>
<div><br class="khtml-block-placeholder">
</div>
<div>As per your last email the /var directory is used for logging,
caching and in the case of Debian/Ubuntu Web and ftp storage.</div>
<div>It's generally the most active part of your filesystem and over
time will grow to become quite large.</div>
<div><br class="khtml-block-placeholder">
</div>
<div>Don't worry too much about sorting your volumes/mount points out
all at once during the install process, it is relatively
straightforward to move your /var data to LVM later on if you find it
maybe worthwhile.</div>
<div><br class="khtml-block-placeholder">
</div>
<div>By the way if you are new to LVM then it maybe worthwhile giving
Suse a try. It provides support for LVM during the installation process
and Yast has an excellent GUI tool for managing LVM volumes post
install. Ubuntu is getting much better but its still not quite at the
same level as Suse when it comes to LVM.</div>
<div><br class="khtml-block-placeholder">
</div>
<div><br class="khtml-block-placeholder">
</div>
<div>David</div>
<div><br class="khtml-block-placeholder">
</div>
<div><br class="khtml-block-placeholder">
</div>
<div><br class="khtml-block-placeholder">
</div>
<br>
<pre wrap="">
<hr size="4" width="90%">
</pre>
</blockquote>
</body>
</html>