karmic has seen the end of its life and is no longer receiving any
updates. Marking the karmic task for this ticket as Won't Fix.
** Changed in: udev (Ubuntu Karmic)
Status: Triaged = Won't Fix
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
And even that wasn't enough to stop all the warnings. Apparently
lvdisplay doesn't set an error code if there were zero results. The
following should catch that situation and stop the last of it:
ENV{DM_UUID}==LVM-*, PROGRAM=/bin/sh -ec 'set -- $(lvm lvdisplay -C
-o vg_name,lv_name --noheadings
I think I got it. In /lib/udev/rules.d/65-dmsetup.rules there's this
line:
ENV{DM_UUID}==LVM-*, PROGRAM=/bin/sh -c 'set `lvm lvdisplay -C -o
vg_name,lv_name --noheadings /dev/$name` ; echo $1/$2',
SYMLINK+=$result
which is a particularly fragile piece of shell script that doesn't do
any error
If this is the same bug as https://bugs.launchpad.net/bugs/483890, and
I'm not sure that it is, then it is still in lucid. Lucid is apparently
better, but not fixed.
I ran some tests over the last few days. Using the script I attached to
483890 I can reproduce the problem in seconds on karmic.
I'm seeing similar problems in a similar situation. I'm not doing
backups but I am creating and removing a sequence of lv's and snapshots.
Mine are on amd64 karmic. I don't believe I've seen these on lucid with
the same code, (which only proves I haven't done enough testing :).
If this is a
Has anyone tested whether this is fixed in Lucid?
It would be a shame to make an LTS release with this bug.
It's slightly frightening to see /var/log/syslog filled by more than 50% by
these messages on servers that use snapshots for backups (I have that on some
Karmic machines). It might be a
Im seeing the same thing when creating and removing an lvm snapshots.
However it doesn't seem to effect the system or use of the lvm in my
case.
--
rename(/dev//.udev-tmp, /dev//) failed: Invalid cross-device link
https://bugs.launchpad.net/bugs/444563
You received this bug notification because
I can confirm this is happening to me on a running machine, making it hang (
not responding to pings whatsoever ).
What i have is a script that creates a snapshot of a lvm volume, mounts it and
starts a backup program, which then backups on another drive.
It's not any of the usual system
** Tags added: ubuntu-boot-experience
--
rename(/dev//.udev-tmp, /dev//) failed: Invalid cross-device link
https://bugs.launchpad.net/bugs/444563
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
This bug also appears when using LVM mirrors at least when resyncing.
For testing purposes I have created six LVM partitions on two physical
drives:
s...@karhuherra:~$ sudo lvs -a -o +devices
LV VGAttr LSize Origin Snap% Move Log Copy% Convert
Devices
The bug also appears with LVM mirrors without resyncing. I have no
snapshots, only two mirrors with their log on the disk.
But I must say, that since the last time I commented on this bug, all
boots were successful for me. I always get the messages and there is a
little time in which nothing
Removing snapshots also removes these messages, but they come back after
taking new snapshots.
--
rename(/dev//.udev-tmp, /dev//) failed: Invalid cross-device link
https://bugs.launchpad.net/bugs/444563
You received this bug notification because you are a member of Ubuntu
Bugs, which is
I can confirm this.
Before updating to 9.10 I took a snapshot of my root partition. From then on I
kept seeing the 'failed: Invalid cross-device link' message and experienced
delays of several seconds each time the message was printed during a boot.
After reading this thread I removed the
After removing the snapshot volume I have not seen this error again.
Not during boot and not in the log files.
--
rename(/dev//.udev-tmp, /dev//) failed: Invalid cross-device link
https://bugs.launchpad.net/bugs/444563
You received this bug notification because you are a member of Ubuntu
Bugs,
I also see these (usually 4 lines of) messages during each boot on a
Karmic (i386 alternate cd) install (no upgrade) using LVM2 with
snapshots.
From /var/log/daemon.log:
Dec 2 06:53:28 laptop udevd-work[699]: rename(/dev//.udev-tmp, /dev//)
failed: Invalid cross-device link
--
While doing snapshots for backups I also this occasionally among the
other errors:
upstart-udev-bridge[25372]: Disconnected from Upstart
upstart-udev-bridge main process (25372) terminated with status 1
upstart-udev-bridge main process ended, respawning
--
rename(/dev//.udev-tmp, /dev//)
This occurs for me (many rename(/dev//.udev-tmp, /dev//) failed:
Invalid cross-device link errors) at boot, if LVM2 snapshots exist. In
my case, I often make snapshots of / and /var so that rollback of
package updates is possible.
--
rename(/dev//.udev-tmp, /dev//) failed: Invalid cross-device
(Coming from bug 483890)
I only see this happening when creating/removing snapshots for backup
not while booting. In addition to rename(/dev//.udev-tmp, /dev//)
failed... I also get rmdir(/dev/) failed: Device or resource busy and
some error messages when creating the snapshots:
Path
PhilW and Jean-Damien Bouvier, I can confirm your problem of the
'sometimes missing root partition', but that is not this bug. (Point me
in the right direction of you know what bug it is, because it is a
pretty critical one.)
--
rename(/dev//.udev-tmp, /dev//) failed: Invalid cross-device link
Well, I see and know nothing except the many udevd-work errors and the
sometimes (not frequently) delayed availability of the logical volumes.
But I'm willing to investigate further, and I already have a little bit
of experience in working (and debugging) of initial ramdisks. So if you
could tell
So far, I guess that the boot really fails.
I get the following message :
Mount of root filesystem failed.
A maintenance shell will now be started
CONTROL-D will terminate this shell and reboot the system
I wait for 15 minutes but nothing happened.
Another time, I get One or more of the mounts
This bug affects me, too. I upgraded yesterday from Jaunty to Karmic
with the update-manager. Since then, a lot of these udev errors appear
while booting, but boot is successful. I'm using LVM for everything
except /boot, but without snapshots (but with mirrored LVs). If you need
more information,
This appears for me when manipulating LVM snapshots.
** Also affects: udev (Ubuntu Karmic)
Importance: High
Status: Triaged
** Changed in: udev (Ubuntu Karmic)
Milestone: None = karmic-updates
** Changed in: udev (Ubuntu Karmic)
Importance: High = Low
--
** Summary changed:
- errors while booting: Invalid cross-device link
+ rename(/dev//.udev-tmp, /dev//) failed: Invalid cross-device link
--
rename(/dev//.udev-tmp, /dev//) failed: Invalid cross-device link
https://bugs.launchpad.net/bugs/444563
You received this bug notification because you
24 matches
Mail list logo
