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 mounts ( i.e. it's /srv/storage ).
Mar 7 03:00:02 blackwing udevd-work[32289]: rename(/dev//.udev-tmp, /dev//) failed: Invalid cross-device link
Mar 7 03:00:02 blackwing udevd-work[9338]: rename(/dev//.udev-tmp, /dev//) failed: Invalid cross-device link
Mar 7 03:00:02 blackwing udevd-work[22424]: rename(/dev//.udev-tmp, /dev//) failed: Invalid cross-device link
Mar 7 03:00:02 blackwing udevd-work[9338]: rename(/dev//.udev-tmp, /dev//) failed: Invalid cross-device link
Mar 7 03:00:02 blackwing udevd-work[32289]: rename(/dev//.udev-tmp, /dev//) failed: Invalid cross-device link
Mar 7 03:54:48 blackwing udevd-work[22429]: rename(/dev//.udev-tmp, /dev//) failed: Invalid cross-device link
Mar 7 03:54:48 blackwing udevd-work[22429]: rmdir(/dev/) failed: Device or resource busy
Mar 7 03:54:48 blackwing udevd-work[22429]: rmdir(/dev/) failed: Device or resource busy
The first events are when the backup starts ( 03:00:02 ). The second events are when the backup ends and the snapshot volume gets unmounted ( 03:54:48 ). After this point i loose connectivity with the machine.
The snapshot volume is never present at boot so i don't have any boot problems, but those hangs are getting very annoying since this is a live production server.
I don't understand why this is marked low, as it seems to be critical for the operation of the servers.
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 mounts ( i.e. it's /srv/storage ).
Mar 7 03:00:02 blackwing udevd-work[32289]: rename( /dev//. udev-tmp, /dev//) failed: Invalid cross-device link /dev//. udev-tmp, /dev//) failed: Invalid cross-device link /dev//. udev-tmp, /dev//) failed: Invalid cross-device link /dev//. udev-tmp, /dev//) failed: Invalid cross-device link /dev//. udev-tmp, /dev//) failed: Invalid cross-device link /dev//. udev-tmp, /dev//) failed: Invalid cross-device link
Mar 7 03:00:02 blackwing udevd-work[9338]: rename(
Mar 7 03:00:02 blackwing udevd-work[22424]: rename(
Mar 7 03:00:02 blackwing udevd-work[9338]: rename(
Mar 7 03:00:02 blackwing udevd-work[32289]: rename(
Mar 7 03:54:48 blackwing udevd-work[22429]: rename(
Mar 7 03:54:48 blackwing udevd-work[22429]: rmdir(/dev/) failed: Device or resource busy
Mar 7 03:54:48 blackwing udevd-work[22429]: rmdir(/dev/) failed: Device or resource busy
The first events are when the backup starts ( 03:00:02 ). The second events are when the backup ends and the snapshot volume gets unmounted ( 03:54:48 ). After this point i loose connectivity with the machine.
The snapshot volume is never present at boot so i don't have any boot problems, but those hangs are getting very annoying since this is a live production server.
I don't understand why this is marked low, as it seems to be critical for the operation of the servers.