Skip to contentSkip to conversation

your mail

linux-lvm Heinz Mauelshagen 5 participants 5 messages Feb 17, 1999 1 message not in the archive

lore
Share & tools
lore

A message that is not in the archive (sent off-list or not yet received): 99021711471501.00456@piglet

#1 lore raw
Quoted 4 lines

Hello,

Firstly great product,

Thanks.

Quoted 3 lines

but have a couple of questions

1. will we be able to use this as our boot disk [vg00]

Yes, but not supported with the standard distribution. Hope to have supprt in the next release.

Quoted 2 lines

2. has anyone tested if lilo can handle /dev/vg00/lvol1 so it knows how to

No, it can't because it deals with sectors on a single boot disk.

You have to have a (small) boot partition (for eg. /dev/sda5) to boot from and have to change to the real-root-dev in a LV after activating volume groups.

Quoted 2 lines

boot the kernel, I would assume changes would need to be made to allow lilo to issue a vgchange on the [vg00] volume group.

LILO had to be enhanced to be able to load sectors from multiple disks if the root logical volume is not continuous.
If it must stay continuous for LILO to be able to address kernel sectors to load there would not be a real enhancement compared
to booting from a hard disk partition.
On Intel compatible PCs BIOS restrictions limiting the number of BIOS addressable disks apply too (LILO uses the BIOS).

Quoted 3 lines

Or could we leave
/boot as a disk section and build into the kernel the ability to active [vg00] ??

Yes, we could boot with LILO form a partition based boot FS and enhance the LVM driver init stuff to activate LV root.
But this driver overhead is not necessary, if we boot from a small partition based fs anyway.
OTOH it would make sense if LILO could directly load the kernel image from a LV.

Quoted 2 lines

3. are there plans for LVM-MIRRORING

Yes, but no fixed time frame 8*(

Quoted 3 lines

4. for allowing root on lvm, is their anny recommended file system sizes and should contingous be set for /boot ?

/boot must be in a regular disk partition containing basic commands, device specials and LVM driver/commands.
About 20-30MB should be sufficient to set this up.

Quoted 4 lines

Sorry if some of these questions have been duplicated, at time of writing couldn't see anything in the archive listing.

Maybe you like to subscribe to our new linux-lvm maling list at [email protected] by sending a "subscribe linux-lvm" in the body of the mail to [email protected].

Regards,
Heinz

--

=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-

Systemmanagement C/S Deutsche Telekom AG
Entwicklungszentrum Darmstadt
Heinz Mauelshagen Otto-Roehm-Strasse 71c
Senior Systems Engineer Postfach 10 05 41

                                                 64205 Darmstadt
[email protected]                      Germany
                                                 +49 6151 886-425
                                                          FAX-386

=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-

#2 lore raw
Quoted 3 lines · Heinz

/boot must be in a regular disk partition containing basic commands, device specials and LVM driver/commands.
About 20-30MB should be sufficient to set this up.

IMO this could even be less if initrd is used.
We may need about 1-2 MB per kernel image + 1-2 MB for the initial utilities (shell, vgchange, mount).

Michael

--

Michael Marxmeier           Marxmeier Software GmbH
E-Mail: [email protected]      Besenbruckstrasse 9
Voice : +49 202 2431440     42285 Wuppertal, Germany
Fax   : +49 202 2431420     http://www.msede.com/
#3 lore raw

Hi

I am using the md raid stuff
(http://www.kernel.org/pub/linux/daemons/raid/) right now. For the md stuff both problems (booting md root device and shutdown) were solved in one way or another. The last time I checked initrd had been used for booting. I have not tracked how the shutdown problem has been resolved. Some cleanup may be moved into the unmount call.

As I used AIX before I am waiting for LVM since a long time. I am glad it is finally here. Now, only JFS must be implemented. Anyone on more details on this (URLs)?

tnx for the great work
- tom

Quoted 9 lines · Michael Marxmeier
Quoted 3 lines · Heinz

/boot must be in a regular disk partition containing basic commands, device specials and LVM driver/commands.
About 20-30MB should be sufficient to set this up.

IMO this could even be less if initrd is used.
We may need about 1-2 MB per kernel image + 1-2 MB for the initial utilities (shell, vgchange, mount).

Quoted 7 lines

Michael

--

Michael Marxmeier           Marxmeier Software GmbH
E-Mail: [email protected]      Besenbruckstrasse 9
Voice : +49 202 2431440     42285 Wuppertal, Germany
Fax   : +49 202 2431420     http://www.msede.com/

--
* Thomas Haas <mailto:[email protected]>
* SoftWired AG <http://www.softwired-inc.com/>
* Technoparkstr. 1 *** CH-8005 Zurich *** +41-1-4452370

#4 lore raw

[linux-lvm] LVM, MD and LLD

Hello,

I have been reading LVM and MD code. It looks like both of these can be merged eventually. The code changes in ll_rw_block for LVM and MD are similar, and it would be nice to have coherent single RAID subsystem in the kernel. Also, I'm not sure how many of you are aware of LLD work from MIT. LLD is "Logical Disk" which tries to solve problems that are usually solved by LFS or other extent based FS with journaling. The neat idea behind LLD is that rather than motifying the FS or writing a new FS to support large extent based I/O coupled with journaling, you can do this at block I/O level, under FS layer. The example software implementation is based on MINIX and a bit outdated. However, it seems reasonable to start looking into merging this into LVM framework.
Of course, given the "free time" if I can manage, I would be very willing to help in the effort, since I am interested in such a thing. Finally, great work all you LVM folks!

Signature · 4 lines
Hwa Jin Bae
PSO Systems Inc
[email protected]   
http://www.pso.com
#5 lore raw
In reply to Michael Marxmeier
Quoted 8 lines · Michael Marxmeier
Quoted 3 lines · Heinz

/boot must be in a regular disk partition containing basic commands, device specials and LVM driver/commands.
About 20-30MB should be sufficient to set this up.

IMO this could even be less if initrd is used.
We may need about 1-2 MB per kernel image + 1-2 MB for the initial utilities (shell, vgchange, mount).

How about a special boot area inside a boot-configured root volume group? That way, lilo could be modified to run the second stage boot loader which could then be as heavyweight as anyone needs it.

Isn't this sort of how hpux handles it?

-Shawn
<=========== America Held Hostage ===========>
Day 2219 for the poor and the middle class.
Day 2238 for the rich and the dead.
703 days remaining in the Raw Deal.
<============================================>