<!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 David and Scott, your tips were very useful
and helped me understand what I did not know and needed to know. As
Confucius once famously said - "you do not know what you do not know".
I ended up modelling the partitioning like this guys standard
workstation install:<br>
<br>
<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><br>
<br>
which goes like this:<br>
<br>
</font>
<pre>[alex@workstation alex]$ df
Filesystem 1k-blocks Used Available Use% Mounted on
/dev/hda13 85530 34264 46850 42% /
/dev/hda1 101089 6802 89068 7% /boot
/dev/hda6 1517920 154616 1286196 11% /home
/dev/hda12 2150420 20 2041160 0% /mnt/tmp
/dev/hda10 248895 27 236018 0% /tmp
/dev/hda5 2016016 1292380 621224 68% /usr
/dev/hda7 758936 37592 682792 5% /var
/dev/hda9 497829 657 471470 0% /var/log
/dev/hda8 758936 292 720092 0% /var/spool</pre>
<font face="Arial"><br>
I made all these mount points LVM volumes except for /boot and /swap,
which were small physical primary partitions /boot having a boot flag.
I did however change it slightly to include a /wnnt physical partition
(4GB) where I initially installed windows nt 4 workstation sp6a. The
Kubuntu with LVM installation went smoothly (although time consuming)
and (yay!) offered a GRUB install to mbr at the end!! Sweet, on first
bootup, GRUB had recognised everything including win nt and had bootup
options for it all at the GRUB menu. I am thrilled this has worked for
me and I feel like I know heaps more about the innards of Linux now!<br>
<br>
</font>Thank you again,<br>
<br>
Rob Collins<br>
<br>
PS - additionally forgot to physically split up hd's into smaller
partitions David, but at this stage don't have the energy to go through
all that again this soon!<br>
<br>
<a class="moz-txt-link-abbreviated" href="mailto:scott@slackisland.org">scott@slackisland.org</a> wrote:
<blockquote cite="mid1161837995.24035.25.camel@slackisland.org" type="cite">
<pre wrap="">On Thu, 2006-10-26 at 17:11 +1300, Rob Collins wrote:
</pre>
<blockquote type="cite">
<pre wrap="">Thanks Scott. I am a bit confused now though. I thought you create a
large "logical group" out of physical hard drives and partitions and
then divide the group up into smaller logical volumes which you can
assign mount points to???
</pre>
</blockquote>
<pre wrap=""><!---->
Sorry, I should have been more clear- you start out with the physical
volume, for example /dev/md0, and that consists of all of the hard
drives, partitions, whatever you want to add to the group. From this
physical volume you can create a single or multiple volume groups- I
usually only make one and name it something easy like "VolGroup", and
then from that volume group you can create the logical volumes. My
current system looks like this:
[root@aa2004100305002 scott]# pvscan
PV /dev/md0 VG VolGroup lvm2 [147.09 GB / 46.50 GB free]
Total: 1 [147.09 GB] / in use: 1 [147.09 GB] / in no VG: 0 [0 ]
[root@aa2004100305002 scott]# vgscan
Reading all physical volumes. This may take a while...
Found volume group "VolGroup" using metadata type lvm2
[root@aa2004100305002 scott]# lvscan
ACTIVE '/dev/VolGroup/LogVolRoot' [9.78 GB] inherit
ACTIVE '/dev/VolGroup/LogVolHome' [68.50 GB] inherit
ACTIVE '/dev/VolGroup/LogVolTmp' [3.91 GB] inherit
ACTIVE '/dev/VolGroup/LogVolUsr' [13.50 GB] inherit
ACTIVE '/dev/VolGroup/LogVolVar' [4.91 GB] inherit
When you are growing a filesystem you are basically taking leftover
space from the volume group- in this case "VolGroup", but you can also
add new physical volumes to that volume group (pop in another hard
drive, use vgextend) as well.
Cheers,
Scott VanDusen
</pre>
</blockquote>
</body>
</html>