I had this problem when I first upgraded to Gutsy, then I removed
"evms", and it went away.
Then we had an automatic upgrade come through, and it installed "evms-
activate", and now I have the problem back. I can not remove or kill the
evms-activate process, it's grayed out.
The only way to get m
I have three such exclude lines in mine. Instructions above are just
for sysfs_devices stanza? Yep, that change alone worked.
I hope this will actually be fixed for the Gutsy release. It's really
bad. I appeared to be averaging over 80% CPU from this before I modified
the evms.conf file. Thing
Another option, which I did, is to change the evms.conf's line "exclude
[ ]" to "exclude [ * ]".
--
Device-mapper errors: dm-linear, lookup failed
https://bugs.launchpad.net/bugs/115616
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu
Yes. The new evms caused my laptop to fail to boot. LiveCD -> chroot
-> aptitude remove evms resolved the issue.
On 10/5/07, Cimmo <[EMAIL PROTECTED]> wrote:
> so someone on Gutsy have tried new version of the package?
>
> --
> Device-mapper errors: dm-linear, lookup failed
> https://bugs.launch
so someone on Gutsy have tried new version of the package?
--
Device-mapper errors: dm-linear, lookup failed
https://bugs.launchpad.net/bugs/115616
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
ubuntu-bugs mailing list
ubuntu
Removal of the "evms" package resolved the problem on my Samsung Q20.
--
Device-mapper errors: dm-linear, lookup failed
https://bugs.launchpad.net/bugs/115616
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
ubuntu-bugs mailing
This is not only an EVMS related bug. I currently use Device Mapper to
access the host protected area of my laptop's HD. I can't create a
partition for it (that makes my dual-booted Windows crash), but a linear
devicemap can make this part accessable for linux. Ofcourse since
there's now the lim
evms (2.5.5-26ubuntu1) gutsy; urgency=low
* Merge from debian unstable, remaining changes:
- call evms_activate from a udev rule when appropriate block devices
are detected.
- ubuntu maintainer address
* debian/patches/99-suse-dos_plugin_activation.patch:
- Patch taken from S
Martin now I think evms is removed from default packages, so if you have
updated from a previous release you still have it (you have to manually
remove it), if you install a fresh gutsy no, so I think bother anymore
about this is useless.
the side effect about this is for example when you put a cd
Sorry I did not want to spam. I just wanted to say that the problem
occurred again on a second machine. I did not know that evms was a
default package in a previous release. In that case the whole situation
is even worse. I can imagine that most "normal" users will not be able
to understand why the
because evms is intalled by default
please try to don't spam this list :q
--
Device-mapper errors: dm-linear, lookup failed
https://bugs.launchpad.net/bugs/115616
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
ubuntu-bugs ma
Happened again when I updated my Laptop to Gutsy today. I had to remove
evms. I don't understand why it was installed at all.
--
Device-mapper errors: dm-linear, lookup failed
https://bugs.launchpad.net/bugs/115616
You received this bug notification because you are a member of Ubuntu
Bugs, which
i had the same problem, and removing emvs (i dont know why it was
installed though) solved the problem. one thing: external drives are no
longer automounted when plugged in at boot-time, i have to unplug and
re-plug them in order to be mounted. this worked with evms installed.
--
Device-mapper er
I also have this issue but would like to add one more thing: Compiz
didn't run for me. Even manually enabling it I get an error saying
Compiz can't start.
After removing evms last night, this morning when I tried enabling
Compiz again, it worked fine this time. Normal & Extra visual effects
work.
Look at bug #144200, closely related if not the same.
--
Device-mapper errors: dm-linear, lookup failed
https://bugs.launchpad.net/bugs/115616
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs
P.S. udevd is eating up 23% of system resource.
--
Device-mapper errors: dm-linear, lookup failed
https://bugs.launchpad.net/bugs/115616
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists
I've had the same problem on Kubuntu Gutsy.
--
Device-mapper errors: dm-linear, lookup failed
https://bugs.launchpad.net/bugs/115616
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubu
I get this too, I installed gutsy (amd64 if it matters) and can't boot
when I use the 2.6.22-12 kernel. When I try to boot normally the screen
just goes black and sits there, when I boot in the safe mode I get the
error message over and over until I restart the system:
device_mapper: table: 254:2
Removing evms needs to be handled by the upgrade-manager.
** Changed in: evms (Ubuntu)
Target: None => ubuntu-7.10-rc
--
Device-mapper errors: dm-linear, lookup failed
https://bugs.launchpad.net/bugs/115616
You received this bug notification because you are a member of Ubuntu
Bugs, which
Sep 28 22:53:15 localhost kernel: [ 763.952000] device-mapper: table: 254:0:
linear: dm-linear: Device lookup failed
Sep 28 22:53:15 localhost kernel: [ 763.952000] device-mapper: ioctl: error
adding target to table
<-- error in infinite loop
Linux 2.6.22-12-generic #1 SMP Sun Sep 23 18:11:30
I have the same , kernel 2.6.22-12-386. udevd get 76% CPU. Gutsy.
--
Device-mapper errors: dm-linear, lookup failed
https://bugs.launchpad.net/bugs/115616
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
ubuntu-bugs mailing list
Same for me. Booting 2.6.20, fixing NVIDIA driver, finding this bug
report and removing evms worked for me. Actually I upgraded only with
the console. I hope this problem will be fixed for the friends of
aptitude dist-upgrade, too.
--
Device-mapper errors: dm-linear, lookup failed
https://bugs.la
Same here (using linux-image-2.6.22-12-generic/gutsy uptodate
2.6.22-12.36).
--
Device-mapper errors: dm-linear, lookup failed
https://bugs.launchpad.net/bugs/115616
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
ubuntu-bugs m
Same here upon dist-upgrade to Gutsy. Nothing new to add, though; my
experience was a combination of the above.
Killing udevd and uninstalling evm worked for me.
--
Device-mapper errors: dm-linear, lookup failed
https://bugs.launchpad.net/bugs/115616
You received this bug notification because y
I also did an upgrade from Feisty today, and I also encountered a flood
of these:
Sep 18 13:40:24 lapedb kernel: [ 178.476000] device-mapper: ioctl:
error adding target to table
(my nvidia module wasn't loaded so my machine got stuck in textmode spawning
this message)
So I ssh'ed to it, kill
The latest `update-manager -d` from Feisty is now prompting to remove
the evms packages, but they are not completely removed, so the user must
still manually remove the evms packages.
--
Device-mapper errors: dm-linear, lookup failed
https://bugs.launchpad.net/bugs/115616
You received this bug no
I had the same problem after upgrading to Gusty. dmesg was full of
nothing but:
device-mapper: ioctl: error adding target to table
device-mapper: table: 254:1: linear: dm-linear: Device lookup failed
And udevd was using 70%CPU!
Removing all *evms* pakages fixed the problem. Hopefully the develop
the solutions is already provided by link provided by Richard Kleeman:
from:
http://evms.sourceforge.net/install/kernel.html#bdclaim
The end result is that a single disk cannot be used both for EVMS and for
mounting the kernel's built-in partitions.
There are three solutions to this problem.
I applied the fix to /etc/evms.conf and stopped and then started
(restart hung) both evms and udev .
its all fixed now , lets push this out to the repos.
--
Device-mapper errors: dm-linear, lookup failed
https://bugs.launchpad.net/bugs/115616
You received this bug notification because you are a
I upgraded from feisty yesterday afternoon, I had the same problem. A
"sudo apt-get --purge remove evms" solved the problem for me
--
Device-mapper errors: dm-linear, lookup failed
https://bugs.launchpad.net/bugs/115616
You received this bug notification because you are a member of Ubuntu
Bugs,
This cured two bugs! My second slave drive was not mounting, and now it
does.
--
Device-mapper errors: dm-linear, lookup failed
https://bugs.launchpad.net/bugs/115616
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
ubuntu-bugs
Also had this problem with Gutsy alpha 5. I had evms installed (along
with evms-ncurses). No idea how, when or why.
I've been killing and restarting this process manually. I hope this
clears up the problem as it has for others. Thanks for the tip.
--
Device-mapper errors: dm-linear, lookup
here with kubuntu feisty and kernel 2.6.20-16 no problem, compiled by myself
kernel 2.6.22.5 and same message error.
Tried Leonel changes and it worked, however don't know what happens whit this.
--
Device-mapper errors: dm-linear, lookup failed
https://bugs.launchpad.net/bugs/115616
You receive
___
on /etc/evms.conf in sysfs_devices added :
exclude = [ * ]
___
This fix worked for me, but is it correct? Will it break things in the
future???
--
Device-mapper errors: dm-linear, lookup failed
https://bugs.launchpad.net/bugs/115616
You received this bug notifica
on /etc/evms.conf in sysfs_devices added :
exclude = [ * ]
and got fixed
--
Device-mapper errors: dm-linear, lookup failed
https://bugs.launchpad.net/bugs/115616
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
ubuntu-bug
I can confirm this is happening on gutsy (yesterdays dist-upgrade).
Removing evms also seemed to make the messages go away.
Wolf, press CTRL-ALT F1 to get a terminal.
--
Device-mapper errors: dm-linear, lookup failed
https://bugs.launchpad.net/bugs/115616
You received this bug notification beca
Gutsy with yesterday's dist-upgrades is showing the same error. I eventually
get a login screen, but entry of name and pass return me to login screen [CTRL]
[Alt] [F1] shows me a continually incrementing list
[ 320.xx] device-mapper: table: 254:0: linear: dm-linear: Device lookup
failed.
I
I saw the same thing today when upgraded from feisty. Removing evms
fixed it. The CPU usage of udevd made my T23 almost unusable which could
be a real problem when trying to fix it.
--
Device-mapper errors: dm-linear, lookup failed
https://bugs.launchpad.net/bugs/115616
You received this bug noti
I also had this and removed evms to fix, on amd64 gutsy.
--
Device-mapper errors: dm-linear, lookup failed
https://bugs.launchpad.net/bugs/115616
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-b
I have also the same problem, so i have just removed evms, thanks for
the quicky fix.
--
Device-mapper errors: dm-linear, lookup failed
https://bugs.launchpad.net/bugs/115616
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
ubu
Bump.
I saw this also. My laptop would never finish booting after I upgraded
to gutsy, with said messages on console. Could boot with an old kernel,
and removing evms "fixed" the problem.
--
Device-mapper errors: dm-linear, lookup failed
https://bugs.launchpad.net/bugs/115616
You received this
I had the same problem. The udevd was using lot of CPU and writing the
same messages over and over again to kernel.log. Stopping and starting
udevd again worked for the session, but it started doing the same thing
again after a reboot. Removing evms fixed the thing also between
reboots.
(Kernel: 2
As a work around, excluding any devices which are mounted externally to
evms in sysfs_devices section of /etc/evms.conf works fine and allows
the continuing use of evms to manage devices which are not otherwise
mounted.
I guess this only works if you are using entirely separate disks in
evms.
--
SergeyS , as reported in one of the duplicates, removing evms should fix
the problem (at least waiting for a proper solution).
--
Device-mapper errors: dm-linear, lookup failed
https://bugs.launchpad.net/bugs/115616
You received this bug notification because you are a member of Ubuntu
Bugs, which
I have the same problem and I use evms... I could not boot to 2.6.22
kernel :-(, but I can boot to 2.6.20. Do you have a workaround for the
problem?
--
Device-mapper errors: dm-linear, lookup failed
https://bugs.launchpad.net/bugs/115616
You received this bug notification because you are a member
Just upgrading to gutsy and have the same issue. Kernel log is full of
messages:
[ 2860.30] device-mapper: ioctl: error adding target to table
[ 2860.30] device-mapper: table: 254:0: linear: dm-linear: Device lookup
failed
[EMAIL PROTECTED]:~# ps aux | grep udev
root 2669 56.8 6.7
In case that's not obvious from the above, "aptitude remove evms" gets
rid of the problem. I suppose if you don't know what evms is, then
you're probably not using it (unless someone else configured your
system; you should ask them then).
--
Device-mapper errors: dm-linear, lookup failed
https://
Scott is uploading an evms package with a fix pulled from SuSe.
** Changed in: linux-source-2.6.22 (Ubuntu)
Status: Needs Info => Rejected
** Changed in: evms (Ubuntu)
Importance: Undecided => High
Assignee: Kyle McMartin => Scott James Remnant
Status: Needs Info => In Progr
Kyle is looking into what we can do to properly handle this.
** Changed in: linux-source-2.6.22 (Ubuntu)
Assignee: (unassigned) => Kyle McMartin
Status: Rejected => Needs Info
** Also affects: evms (Ubuntu)
Importance: Undecided
Status: Unconfirmed
** Changed in: evms (Ubun
Confirmed that this appears to be the problem. If I exclude all devices
lin the sysfs_devices section of /etc/evms.conf then the problem
disappears.
As mentioned above I am a bit concerned how many other users may hit
this snag if evms has been installed "without their knowledge" so to
speak..
Is evms not installed by default? If it is will not the error that I am seeing
trip up other users as well?
I don't recall ever installing evms optionally.
Just trying to understand how this issue may effect the run of the mill
user.
I will filp the off switch in /etc/evms.conf as suggested a
Definitely, we used to carry the bd_claim patch, but after review, we've
decided not to include it anymore because of the more important problems
it allows.
This link explains how to correctly use evms with stock kernels.
http://evms.sourceforge.net/install/kernel.html#bdclaim
** Changed in: lin
Googling this reveals the following which may (or may not) be relevant:
http://evms.sourceforge.net/faq.html (see the Volume Activation section)
--
Device-mapper errors: dm-linear, lookup failed
https://bugs.launchpad.net/bugs/115616
You received this bug notification because you are a member of
Please don't confirm. There's still no evidence that this is a kernel
bug. It could very well be a udev bug.
** Changed in: linux-source-2.6.22 (Ubuntu)
Status: Confirmed => Unconfirmed
--
Device-mapper errors: dm-linear, lookup failed
https://bugs.launchpad.net/bugs/115616
You received t
** Changed in: linux-source-2.6.22 (Ubuntu)
Status: Unconfirmed => Confirmed
--
Device-mapper errors: dm-linear, lookup failed
https://bugs.launchpad.net/bugs/115616
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
ubuntu
** Summary changed:
- Error Messages
+ Device-mapper errors: dm-linear, lookup failed
--
Device-mapper errors: dm-linear, lookup failed
https://bugs.launchpad.net/bugs/115616
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
ubu
101 - 156 of 156 matches
Mail list logo
