| 1 |
Thanks. The forums seem to have some active LVM discussion. |
| 2 |
|
| 3 |
Kelly Price wrote: |
| 4 |
> You'll want the forums. Take the elevator back down to the third |
| 5 |
> floor, http://forums.gentoo.org . If you want a more interactive |
| 6 |
> responce, take it down to the lobby and hook up on the FreeNode IRC |
| 7 |
> Tram. It should take you to #gentoo. |
| 8 |
> |
| 9 |
> On 5/15/06, Joe Harvell <jharvell@××××××.net> wrote: |
| 10 |
>> I am in the process of installing Gentoo on an x86 from the 2006.0 |
| 11 |
>> installer CD using the 2.4 kernel profile. I created an LVM2 volume |
| 12 |
>> group with logical volumes / filesystems for '/', '/usr', '/var', |
| 13 |
>> '/opt', and '/home'. I had no problems mounting those filesystems and |
| 14 |
>> then chrooting into that environment and performing the base install. I |
| 15 |
>> compiled the 2.4.32-r4 kernel from gentoo-sources with no problems, and |
| 16 |
>> created the initial ram disk by hand so that I could bring up the LVM2 |
| 17 |
>> volumes. |
| 18 |
>> |
| 19 |
>> The problem I am having is when I boot into the initrd. I run vgscan |
| 20 |
>> with no apparent problems, and it finds the volume group. When I run |
| 21 |
>> 'vgchange -ay <vgname>, I notice three problems: |
| 22 |
>> |
| 23 |
>> 1. There are entries in /dev/mapper/<vgname>-<lvname>, but no symlinks |
| 24 |
>> in the form /dev/<vgname>/<lvname> --> /dev/mapper/<vgname>/<lvname>. I |
| 25 |
>> run 'lvm vgmknodes' and it remedies this. |
| 26 |
>> |
| 27 |
>> 2. I see five complaints from 'vgchange -ay <vgname>' (one for each LV) |
| 28 |
>> as follows: |
| 29 |
>> |
| 30 |
>> on stderr: device-mapper: table ioctl failed: Invalid argument |
| 31 |
>> on console (from dm-mod driver): device-mapper: one of name or uuid must |
| 32 |
>> be supplied, cmd (12) |
| 33 |
>> |
| 34 |
>> I ran vgchange under strace and here is the following snippet: |
| 35 |
>> |
| 36 |
>> open("/dev/mapper/control", O_RDWR|O_LARGEFILE) = 9 |
| 37 |
>> ioctl(9, DM_DEV_STATUS, 0x8109958) = -1 ENXIO (No such device or |
| 38 |
>> address) |
| 39 |
>> ioctl(9, DM_DEV_STATUS, 0x8109958) = -1 ENXIO (No such device or |
| 40 |
>> address) |
| 41 |
>> ioctl(9, DM_DEV_STATUS, 0x8109958) = -1 ENXIO (No such device or |
| 42 |
>> address) |
| 43 |
>> mlockall(MCL_CURRENT|MCL_FUTURE) = 0 |
| 44 |
>> brk(0x8936000) = 0x8936000 |
| 45 |
>> brk(0x8b1e000) = 0x8b1e000 |
| 46 |
>> getpriority(PRIO_PROCESS, 0) = 20 |
| 47 |
>> setpriority(PRIO_PROCESS, 0, -18) = 0 |
| 48 |
>> ioctl(9, DM_DEV_STATUS, 0x8109958) = -1 ENXIO (No such device or |
| 49 |
>> address) |
| 50 |
>> ioctl(9, DM_DEV_STATUS, 0x8109958) = -1 ENXIO (No such device or |
| 51 |
>> address) |
| 52 |
>> ioctl(9, DM_DEV_STATUS, 0x8109958) = -1 ENXIO (No such device or |
| 53 |
>> address) |
| 54 |
>> ioctl(9, DM_DEV_STATUS, 0x8109958) = -1 ENXIO (No such device or |
| 55 |
>> address) |
| 56 |
>> ioctl(9, DM_DEV_STATUS, 0x8109958) = -1 ENXIO (No such device or |
| 57 |
>> address) |
| 58 |
>> ioctl(9, DM_DEV_STATUS, 0x8109958) = -1 ENXIO (No such device or |
| 59 |
>> address) |
| 60 |
>> ioctl(9, DM_DEV_STATUS, 0x8109958) = -1 ENXIO (No such device or |
| 61 |
>> address) |
| 62 |
>> ioctl(9, DM_DEV_STATUS, 0x8109958) = -1 ENXIO (No such device or |
| 63 |
>> address) |
| 64 |
>> ioctl(9, DM_DEV_STATUS, 0x8109958) = -1 ENXIO (No such device or |
| 65 |
>> address) |
| 66 |
>> stat64("/dev/ide/host0/bus0/target0/lun0/part10", {st_mode=S_IFBLK|0600, |
| 67 |
>> st_rdev=makedev(3, 10), ...}) = 0 |
| 68 |
>> stat64("/dev/ide/host0/bus0/target0/lun0/part11", {st_mode=S_IFBLK|0600, |
| 69 |
>> st_rdev=makedev(3, 11), ...}) = 0 |
| 70 |
>> stat64("/dev/ide/host0/bus0/target0/lun0/part12", {st_mode=S_IFBLK|0600, |
| 71 |
>> st_rdev=makedev(3, 12), ...}) = 0 |
| 72 |
>> ioctl(9, DM_DEV_CREATE, 0x8109958) = 0 |
| 73 |
>> ioctl(9, DM_TABLE_STATUS, 0x8109958) = -1 EINVAL (Invalid argument) |
| 74 |
>> write(2, " ", 2) = 2 |
| 75 |
>> write(2, "device-mapper: table ioctl faile"..., 51) = 51 |
| 76 |
>> write(2, "\n", 1) = 1 |
| 77 |
>> |
| 78 |
>> 3. When I try to mount the filesystem in that LV, it fails. I tried |
| 79 |
>> with different filesystem types and it's the same result. From within |
| 80 |
>> the 2.4 kernel based initrd, it fails. If I reboot into the 2.6 kernel |
| 81 |
>> based installer environment, no problem. |
| 82 |
>> |
| 83 |
>> This looks like an incompatibility between the lvm2 and/or device-mapper |
| 84 |
>> library code and the kernel device-mapper code. Here are the versions |
| 85 |
>> installed in the new installation and its initrd: |
| 86 |
>> |
| 87 |
>> lvm2-2.02.05 |
| 88 |
>> device-mapper-1.02.03 |
| 89 |
>> gentoo-sources-2.4.32-r4 |
| 90 |
>> |
| 91 |
>> livecd 2.4 # ls -l /etc/make.profile |
| 92 |
>> lrwxrwxrwx 1 root root 51 May 11 18:09 /etc/make.profile -> |
| 93 |
>> /usr/portage/profiles/default-linux/x86/no-nptl/2.4 |
| 94 |
>> |
| 95 |
>> -- |
| 96 |
>> gentoo-embedded@g.o mailing list |
| 97 |
>> |
| 98 |
>> |
| 99 |
> |
| 100 |
> |
| 101 |
|
| 102 |
-- |
| 103 |
gentoo-embedded@g.o mailing list |
Archives