On Tue, Mar 07, 2006 at 09:05:20AM -0500, Lennart Sorensen wrote:
> It is correct behaviour. If cfdisk doesn't do the same thing if you
> use it to add a partition to an existing partition table, then
> cfdisk is broken. I suspect it only rearanged partitions made
> within one session, which is reasonable I suppose, and not unheard
> of in other fdisk implementations.
That appears to be what cfdisk does, yes; any logical partitions
created in the current session will be in order based on position on
the disk. Neither seems unreasonable, and it was simply the
difference that confused me. So no real problem here.
> You allocate a partition as LVM physical volume, then you go pick
> LVM setup at the top of the partition menu, and it will let you
> creat a volume group, and then logical volumes within it.
Yeah, I missed that option, I guess. Even in my subsequent meddling
with the expert install. Guess being an "expert" means you make
assumptions and don't read things carefully. Sorry. ;)
> (You don't want root on LVM at this time. Too messy.)
My thoughts exactly.
Also, subsequent readings of the LVM docs indicated I should also
create a single physical LVM volume per physical disk (for simplicity,
striping, etc.), unlike my inclination to divide it into chunks -- a
throwback to standard partitioning, I suppose, where having a 247-gig
partition was a recipe for inflexibility (unless you bought an even
bigger disk to move stuff onto).
So, my follow-up install:
Same system and image. Used 'expert'. I liked all the prompts, and
the defaults were usually fine. Liked how it confirmed the CD
identity. Very much liked the SSH-based installer, and that it asked
me to confirm the SSH host key.
It'd be nice if the SSH installer terminated connections more kindly
at the end, because it dropped in the middle of the screen and left my
terminal reversed and without a cursor. Not a big deal.
It did try to load the 'floppy' driver three times, once as part of
the CD detection process and twice by prompt later. All failed due to
lack of a floppy drive. Also not a big deal.
When it came time to set up the volume group, it misreported my
247.1-gig partition as a 43.82-gig partition, and used the
/dev/ide/... notation. (I'm guessing this is a udev-style thing I'm
just going to have to get used to, eh?) I had to double check the
partition table to make sure it wasn't wiping the wrong one (even
though the bus, disk, and partition all matched up).
Deleting it and recreating the volume group (wanted a different name)
reported 230.09 GB, which I guess is GiB? All the LVM stuff seems to
be in GiB, while the partitioner seems to be GB.
Back in the partition manager after the LVM setup, the fact that each
volume occupied two lines (and were all numbered #1) made things a bit
cramped and easier to lose track of things. A *very* minor wishlist
item would be to condense the information to one line, if possible,
perhaps as a numbered list under the LVM volume group heading.
Still worked, though, and was a fairly painless process. I liked that
I could finally set up the noexec, etc. properties at install time.
Final partition table:
Device Boot Start End Blocks Id System
/dev/hdc1 * 1 122 979933+ 83 Linux
/dev/hdc2 123 30401 243216067+ 5 Extended
/dev/hdc5 123 365 1951866 82 Linux swap / Solaris
/dev/hdc6 366 30401 241264138+ 8e Linux LVM
lvs:
LV VG Attr LSize Origin Snap% Move Copy%
home wisq_root -wi-ao 200.00G
tmp wisq_root -wi-ao 1.00G
usr wisq_root -wi-ao 5.00G
usr_local wisq_root -wi-ao 3.00G
var wisq_root -wi-ao 10.00G
var_exec wisq_root -wi-ao 1.00G
var_tmp wisq_root -wi-ao 1.00G
Thanks for another great install. :)
Attachment:
signature.asc
Description: Digital signature