Le lundi 15 octobre 2012 à 19:20 +0200, Stefan Seyfried a écrit :
Am 15.10.2012 18:53, schrieb Dimstar / Dominique Leuenberger:
Hi all,
the latest filesystem package received some script magic, trying to rename /var/lock to /var/lock.migrated and finally adding some symlinking to /run/lock, which is the new location for the lock folder.
Unfortunately, on my machine, this fails for some reason (currently unknown to me):
Installing: filesystem-12.3-3.1 ...............................................................................................[error] Installation of filesystem-12.3-3.1 failed: (with --nodeps --force) Error: Subprocess failed. Error: RPM failed: error: unpacking of archive failed on file /var/lock: cpio: rename failed - Is a directory error: filesystem-12.3-3.1.x86_64: install failed error: filesystem-12.3-2.1.x86_64: erase skipped
Trying to do this move manually results in: # mv /var/lock /var/lock.migrated mv: cannot move ‘/var/lock’ to ‘/var/lock.migrated’: Device or resource busy
On my Factory box with filesystem-12.3-2.1, a tmpfs is mounted on /var/lock -- and I guess you cannot rename busy mountpoints...
which is why I used "umount -l /var/lock" before the rename. It allows
access to the underlying directory (and renaming it) even if there are
process still accessing the mount point.
And in my tests, it was working it (same for /var/run). Unfortunately,
it looks like "something" not visible with lsof / fuser is
using /var/lock, which is preventing mv to work properly and I have no
idea what it might be.
--
Frederic Crozat