Am Mittwoch, 6. September 2006 11:16 schrieb ext Stephen Liu:

> > Am Mittwoch, 6. September 2006 03:12 schrieb ext Stephen Liu:
> > > I think following warning is critical;
> > > device-mapper : dm-linear : Device lookup failed
> > > device-mapper : error adding target to table
> >
> > Did you compile dm into the kernel (or: Is the dm-mod modules
> > loaded?)?
>
> At time of installation I ran;
> # modprobe dm-mod
> No printout
>
> Afterwards I found it for "Loading the LVM2 module".  I ran LVM not
> LVM2 so I did not care it further.

There is no LVM2 module.

> I think following warning is a major problem;
> device-mapper : dm-linear : Device lookup failed
> device-mapper : error adding target to table

From the EVMS FAQ:

"Q.  I'm running on a 2.6 kernel and some or all of my volumes fail to get 
activated. The volumes don't show up in the /dev/evms/ directory and I get 
the following errors in my kernel log: 
device-mapper: dm-linear: Device lookup failed
device-mapper: error adding target to table

A.  You probably need to apply the bd-claim patch to your kernel. See 
http://evms.sf.net/install/kernel.html#bdclaim for more details about this 
patch and other possible options."

The problem is that beginning with kernel 2.6 it is no longer allowed to 
talk to devices via different paths (i.e. /dev/hda1 and /dev/evms/hda1). So 
evms_activate (or: the device-mapper) will have problems creating a mapping 
when the device is allready used via a different path. However, from the 
other mails in this thread, I don't see where this is happening.

Are you using both lvm2 tools _and_ EVMS? Then it is clear that the latter 
will fail.

Bye...

        Dirk
-- 
Dirk Heinrichs          | Tel:  +49 (0)162 234 3408
Configuration Manager   | Fax:  +49 (0)211 47068 111
Capgemini Deutschland   | Mail: [EMAIL PROTECTED]
Hambornerstraße 55      | Web:  http://www.capgemini.com
D-40472 Düsseldorf      | ICQ#: 110037733
GPG Public Key C2E467BB | Keyserver: www.keyserver.net

Attachment: pgpogdN0iYwoH.pgp
Description: PGP signature

Reply via email to