1 |
Cross posting is not very polite. How should we, on this list, know if |
2 |
someone has helped you yet? |
3 |
|
4 |
This is the same as being in a grocery store, when a new counter row is |
5 |
opened and a big lady bumps everyone aside just to be the first one in |
6 |
the row. How rude. |
7 |
|
8 |
Mark |
9 |
|
10 |
Joe Harvell wrote: |
11 |
> I am in the process of installing Gentoo on an x86 from the 2006.0 |
12 |
> installer CD using the 2.4 kernel profile. I created an LVM2 volume |
13 |
> group with logical volumes / filesystems for '/', '/usr', '/var', |
14 |
> '/opt', and '/home'. I had no problems mounting those filesystems and |
15 |
> then chrooting into that environment and performing the base install. |
16 |
> I compiled the 2.4.32-r4 kernel from gentoo-sources with no problems, |
17 |
> and created the initial ram disk by hand so that I could bring up the |
18 |
> LVM2 volumes. |
19 |
> |
20 |
> The problem I am having is when I boot into the initrd. I run vgscan |
21 |
> with no apparent problems, and it finds the volume group. When I run |
22 |
> 'vgchange -ay <vgname>, I notice three problems: |
23 |
> |
24 |
> 1. There are entries in /dev/mapper/<vgname>-<lvname>, but no |
25 |
> symlinks in the form /dev/<vgname>/<lvname> --> |
26 |
> /dev/mapper/<vgname>/<lvname>. I run 'lvm vgmknodes' and it remedies |
27 |
> this. |
28 |
> |
29 |
> 2. I see five complaints from 'vgchange -ay <vgname>' (one for each |
30 |
> LV) as follows: |
31 |
> |
32 |
> on stderr: device-mapper: table ioctl failed: Invalid argument |
33 |
> on console (from dm-mod driver): device-mapper: one of name or uuid |
34 |
> must be supplied, cmd (12) |
35 |
> |
36 |
> I ran vgchange under strace and here is the following snippet: |
37 |
> |
38 |
> open("/dev/mapper/control", O_RDWR|O_LARGEFILE) = 9 |
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 |
> ioctl(9, DM_DEV_STATUS, 0x8109958) = -1 ENXIO (No such device or |
44 |
> address) |
45 |
> mlockall(MCL_CURRENT|MCL_FUTURE) = 0 |
46 |
> brk(0x8936000) = 0x8936000 |
47 |
> brk(0x8b1e000) = 0x8b1e000 |
48 |
> getpriority(PRIO_PROCESS, 0) = 20 |
49 |
> setpriority(PRIO_PROCESS, 0, -18) = 0 |
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 |
> ioctl(9, DM_DEV_STATUS, 0x8109958) = -1 ENXIO (No such device or |
67 |
> address) |
68 |
> stat64("/dev/ide/host0/bus0/target0/lun0/part10", |
69 |
> {st_mode=S_IFBLK|0600, st_rdev=makedev(3, 10), ...}) = 0 |
70 |
> stat64("/dev/ide/host0/bus0/target0/lun0/part11", |
71 |
> {st_mode=S_IFBLK|0600, st_rdev=makedev(3, 11), ...}) = 0 |
72 |
> stat64("/dev/ide/host0/bus0/target0/lun0/part12", |
73 |
> {st_mode=S_IFBLK|0600, st_rdev=makedev(3, 12), ...}) = 0 |
74 |
> ioctl(9, DM_DEV_CREATE, 0x8109958) = 0 |
75 |
> ioctl(9, DM_TABLE_STATUS, 0x8109958) = -1 EINVAL (Invalid argument) |
76 |
> write(2, " ", 2) = 2 |
77 |
> write(2, "device-mapper: table ioctl faile"..., 51) = 51 |
78 |
> write(2, "\n", 1) = 1 |
79 |
> |
80 |
> 3. When I try to mount the filesystem in that LV, it fails. I tried |
81 |
> with different filesystem types and it's the same result. From within |
82 |
> the 2.4 kernel based initrd, it fails. If I reboot into the 2.6 |
83 |
> kernel based installer environment, no problem. |
84 |
> |
85 |
> This looks like an incompatibility between the lvm2 and/or |
86 |
> device-mapper library code and the kernel device-mapper code. Here |
87 |
> are the versions installed in the new installation and its initrd: |
88 |
> |
89 |
> lvm2-2.02.05 |
90 |
> device-mapper-1.02.03 |
91 |
> gentoo-sources-2.4.32-r4 |
92 |
> |
93 |
> livecd 2.4 # ls -l /etc/make.profile |
94 |
> lrwxrwxrwx 1 root root 51 May 11 18:09 /etc/make.profile -> |
95 |
> /usr/portage/profiles/default-linux/x86/no-nptl/2.4 |
96 |
> |
97 |
-- |
98 |
gentoo-admin@g.o mailing list |