Problems with LVM 0.6
First off, I had trouble compiling the tools. I got a warning that "LVM_BLK_MAJOR" was undeclared, when compiling tools/lib/lvm_tab_get_free_blk_dev.c
Since I could not find any defination anywhere for LVM_BLK_MAJOR, I assumed that some sort of name change was not properly propegated, and renamed all occurances of "LVM_BLK_MAJOR" to "LVM_BLOCK_MAJOR" in tools/lib/lvm_tab_get_free_blk_dev.c, and the compile completed successfully.
However,
I am now having problems when creating a second Logica volume. These are the steps I took
Using fdisk, created 3 partitions, /dev/sdb2, /dev/sdb3, and /dev/sdb4, and set the partition type to FE. (Note that /dev/sdb1 is a swap partition).
pvcreate /dev/sdb[23]
vgcreate test_vg /dev/sdb[23]
lvcreate -L1500 -nlv1 test_vg
mke2fs /dev/test_vg/lv1
(this created a very small filesystem. Apperently the -L is not assuming a size modifier of Megabyte)
I deleted the test logical volume with
lvremove -f /dev/test_vg/lv1
and created two new logical volumes with
lvcreate -L1500M -nlv1 test_vg
lvcreate -L3G -nlv2 test_vg
mke2fs /dev/test_vg/lv1
mke2fs /dev/test_vg/lv2
mount /dev/test_vg/lv1 /mnt1
suceeded, but
mount /dev/test_vg/lv2 /mnt2
said that either lv2 or mnt2 was already mounted
I did a ls -l of /dev/test_vg and have the following
total 0
crw-r----- 1 root root 109, 0 Mar 4 10:54 group brw-r----- 1 root root 58, 0 Mar 4 10:55 lv1 brw-r----- 1 root root 58, 0 Mar 4 10:56 lv2
Why do lv1 and lv2 have the exact same major and minor values??? Is this related to my possibly incorrect assumption above that LVM_BLK_MAJOR needed to be renamed to LVM_BLOCK_MAJOR????
Has anybody else seen problems like this?
Or is it something that I've done wrong?
Anybody out there who can help me?
Steve Brueggeman
[email protected]
[email protected]
Hi Steve,
Quoted 4 lines · Steve Brueggeman
First off, I had trouble compiling the tools. I got a warning that "
LVM_BLK_MAJOR" was undeclared, when compilingtools/lib/lvm_tab_get_free_blk_dev.c
Seems to me, that your patch was not successfull. LVM_BLK_MAJOR is to be defined in $LINUX_SRC/include/linux/major.h. Look for a .rej file in that directory (btw. this should be done after every patch ;-)). The sequence in the INSTALL file should be changed: first patch the kernel sources, then build the tools. The other things is, that, if you apply the patch to a already patched source (ex. to update LVM0-5alpha to 0.6_also_alpha), the new module source is inserted to the beginning of the source file, both versions are in it and the compiler is the talking to you, telling you funny things ;-). Perhaps there should be upgrade-patches-from-xx-to-yy ?
One very very heavy problem i ran in yesterday was, that the dynamic creation of the /dev/lvm device-file with devfs does not work in lvm-0.6 anymore (sorry, i didn't search why). So i have to create the /dev/lvm after loading the lvm-module before i can vgscan.
Btw. what are the files vgscan creates in /etc are used for. Is it possible to suppress creation (or even rw-access) to these files if they already exist? Background is, that i have to fsck and remount,rw my root-fs before i can use lvm. Is that really neccessary?
But, after all that criticism, cheers for this software! It is what i waited for! Let`s get it stable quickly!
Ciao
Klaus
Signature · 6 lines
Klaus Strebel [email protected] EIGNER + PARTNER AG - The Engineering Warehouse Company - <http://www.ep-ag.com> ----------------------------------------------------------------------- In Heaven there will be no DOS, no Intel, and above all, no Bill Gates.