Arch Linux

radoshow

Member

From: Burgas,BG

Registered: 2011-01-28

Posts: 25

filesystem upgrade - manual intervention required

http://www.archlinux.org/news/filesyste … equired-1/
How to fix the problem:

2012-06-07

As of filesystem-2012.6-2 the folders /var/run and /var/lock will be replaced by symlinks to /run and /run/lock, respectively.

On most systems this is already the case, as initscripts create the symlinks on boot. However, these symlinks are not owned by any package, which is what we are fixing with this upgrade.

If the symlinks are already in place on your system (which should be the case for most people), then you can simply perform

# pacman -Syu --ignore filesystem && pacman -S filesystem --force

Otherwise, if /var/run or /var/lock are directories (e.g. if you are using systemd and never booted with initscripts) you need to delete the directories before performing the update. As these directories are used at runtime, it is recommended to shutdown any background tasks before performing

# rm -rf /var/run /var/lock && pacman -Syu && reboot

Note: In general, it is strongly advised to avoid the --force switch as it is not safe. However, in this particular case it is safe, and suggested to avoid having to manually delete the /var/run or /var/lock symlinks.

Lastly, on upgrading filesystem users of kernels prior to linux-3.4 will get a warning about permissions on /sys. This is nothing to worry about, as of linux-3.4 the permissions will be 555, and this upgrade reflects this in the filesystem package.

What error you will see:

# pacman -Syy
:: Synchronizing package databases...
 core                     103,7 KiB  1001K/s 00:00 [----------------------] 100%
 extra                   1402,3 KiB  3,39M/s 00:00 [----------------------] 100%
 community               1691,1 KiB  2,88M/s 00:01 [----------------------] 100%

# pacman -Syu
:: Synchronizing package databases...
 core is up to date
 extra is up to date
 community is up to date
:: Starting full system upgrade...
resolving dependencies...
looking for inter-conflicts...

Targets (4): filesystem-2012.6-2  icu-49.1.2-1  libsystemd-185-1
             systemd-tools-185-1

Total Installed Size:   29,33 MiB
Net Upgrade Size:       0,23 MiB

Proceed with installation? [Y/n] y
(4/4) checking package integrity                   [----------------------] 100%
(4/4) loading package files                        [----------------------] 100%
(4/4) checking for file conflicts                  [----------------------] 100%
error: failed to commit transaction (conflicting files)
filesystem: /var/lock exists in filesystem
filesystem: /var/run exists in filesystem
Errors occurred, no packages were upgraded.

Frenzy

New member

From: Long Beach, CA

Registered: 2012-04-13

Posts: 7

Re: filesystem upgrade - manual intervention required

http://www.archlinux.org/ on the front page.

Well it mentions to having to remove /var/run and /var/lock.I ran the command they recommended rm -rf /var/run /var/lock && pacman -Syu && reboot and everything went smoothly.

Last edited by Frenzy (2012-06-07 13:23:16)

radoshow

Member

From: Burgas,BG

Registered: 2011-01-28

Posts: 25

Re: filesystem upgrade - manual intervention required

http://www.archlinux.org/ on the front page.

Well it mentions to having to remove /var/run and /var/lock.I ran the command they recommended rm -rf /var/run /var/lock && pacman -Syu && reboot and everything went smoothly.

Thank you.Now everything is ОК.

Frenzy

New member

From: Long Beach, CA

Registered: 2012-04-13

Posts: 7

Re: filesystem upgrade - manual intervention required

No problem just here to help.