1 |
Richard Fish schreef: |
2 |
> Phill MV wrote: |
3 |
> |
4 |
>> Well, *something* is trying to access a function that doesnt exist |
5 |
>> in NDB; whether we know what it does or why, I'm guessing it's a |
6 |
>> behaviour that shouldn't happen :P. |
7 |
>> |
8 |
>> I suppose whatever tries to access NDB has a bug in it... but what |
9 |
>> would that be? |
10 |
> |
11 |
> |
12 |
> |
13 |
> Do you have lvm installed (/sbin/lvm)? |
14 |
> |
15 |
> If so, the Gentoo startup script /sbin/rc will try to execute it |
16 |
> after starting udev to probe for physical volumes, volume groups, and |
17 |
> logical volumes. The default configuration of lvm probes _all_ block |
18 |
> devices, so this is a probable suspect. You can try adding a filter |
19 |
> to /etc/lvm/lvm.conf in this case, like so: |
20 |
> |
21 |
> filter = [ "r|/dev/nbd.*|" ] |
22 |
> |
23 |
> As for whether it should or shouldn't happen, I am not sure. I don't |
24 |
> know how common it is to use network block devices...it is |
25 |
> definitely a high-end feature. I would guess that anyone using nbd |
26 |
> would also be interested in using lvm, so it is probably more useful |
27 |
> to have lvm probe these devices if they exist. |
28 |
|
29 |
|
30 |
Well, insofar as it is a confirmation of anything, I can say that that |
31 |
explains the problem with nbd in my case; I have an lvm2 volume, managed |
32 |
by evms (which is also too hige-end for my use, but I'm kinda stuck with |
33 |
it now). Evms is also prone to probe every d*mn thing it can find, and |
34 |
of course the lvm plugin is in use, because I actually do have an lvm2 |
35 |
volume. So I can see how if nbd was available, it would want to check |
36 |
that as well, and both why removing it was necessary to make it stop, as |
37 |
well as why it was unnecessary for me in the first place. |
38 |
|
39 |
Thanks for the explanation. |
40 |
|
41 |
Holly |
42 |
-- |
43 |
gentoo-user@g.o mailing list |