You are not logged in.
Ran pacman -Syu today (as I do every day) and while it was upgrading the filesystem package I got the following output:
warning: extracting /etc/passwd as /etc/passwd.pacnew
warning: extracting /etc/fstab as /etc/fstab.pacnew
warning: extracting /etc/group as /etc/group.pacnew
warning: extracting /etc/shadow as /etc/shadow.pacnew
warning: extracting /etc/ld.so.conf as /etc/ld.so.conf.pacnew
error: could not extract /usr/var (Directory not empty)
error: errors occurred while upgrading filesystem
(1/4) upgrading filesystem [#####################] 100%
Should I be worried? To me it just looks like it was trying to create an already existing directory and bailed out. Looking at the filelist of filesystem reveals no files in that directroy so I don't think there is any problem, or is there?
PC: Antec P182B | Asus P8Z77-V PRO | Intel i5 3570k | 16GB DDR3 | GeForce 450GTS | 4TB HDD | Pioneer BDR-207D | Asus Xonar DX | Altec Lansing CS21 | Eizo EV2736W-BK | Arch Linux x86_64
HTPC: Antec NSK2480 | ASUS M3A78-EM (AMD 780G) | AMD Athlon X3 425 | 8GB DDR2 | GeForce G210 | 2TB HDD | Arch Linux x86_64
Server: Raspberry Pi (model B) | 512MB RAM | 750GB HDD | Arch Linux ARM
Offline
/usr/var/ is a symlink to /var/ here, not a directory.
So is /usr/var/ a real directory, and if yes, which files does it contain ? And which packages own these files ?
It could have been caused by this : http://bugs.archlinux.org/task/7484
pacman roulette : pacman -S $(pacman -Slq | LANG=C sort -R | head -n $((RANDOM % 10)))
Offline
$ ls /usr/var/ -l
total 8
-rw-rw-rw- 1 root root 229 26 jun 19.22 lbreakout2.hscr
drwxr-xr-x 3 root root 4096 18 jun 07.29 run
$ pacman -Qo /usr/var/lbreakout2.hscr
/usr/var/lbreakout2.hscr is owned by lbreakout2 2.6beta_7-1
$ ls /usr/var/run/ -l
total 4
drwx------ 2 root root 4096 18 jun 07.29 wesnothd
# ls /usr/var/run/wesnothd/ -l
total 0
So lbreakout2 and wesnoth might be to blame here.
PC: Antec P182B | Asus P8Z77-V PRO | Intel i5 3570k | 16GB DDR3 | GeForce 450GTS | 4TB HDD | Pioneer BDR-207D | Asus Xonar DX | Altec Lansing CS21 | Eizo EV2736W-BK | Arch Linux x86_64
HTPC: Antec NSK2480 | ASUS M3A78-EM (AMD 780G) | AMD Athlon X3 425 | 8GB DDR2 | GeForce G210 | 2TB HDD | Arch Linux x86_64
Server: Raspberry Pi (model B) | 512MB RAM | 750GB HDD | Arch Linux ARM
Offline
I think it's only pacman that is to blame , it probably overwrote the /usr/var/ -> /var/ symlink when installing lbreakout2 .
Anyway, I'm not sure why /usr/var/ is a symlink to /var/ , so I don't know if having a real /usr/var/ directory could cause issues. But I don't think so..
You can still repair it manually if you like, by moving the stuff in /usr/var/ back to /var/ , and then restoring the symlink.
But this will break next time you upgrade a package with a file in /usr/var/ , with a broken pacman.
pacman roulette : pacman -S $(pacman -Slq | LANG=C sort -R | head -n $((RANDOM % 10)))
Offline
I'd advise to uninstall lbreakout2 and wesnoth , THEN remove any left over files in /usr/var/ and restore the symlink.
After that you can try installing those packages again.
Disliking systemd intensely, but not satisfied with alternatives so focusing on taming systemd.
(A works at time B) && (time C > time B ) ≠ (A works at time C)
Offline
I'd advise to uninstall lbreakout2 and wesnoth , THEN remove any left over files in /usr/var/ and restore the symlink.
After that you can try installing those packages again.
That will just cause pacman to overwrite the symlink again when reinstalling those packages, and [vEX] will just have the original problem all over again. (see the bug that shining has referred to).
Offline
So the best solution would seem to be to wait for a new pacman that fixes the bug and then remove the packages, fix the symlink (reinstalling filesystem should be do the trick, yes I'm to lazy to do it myself :-p) and then install the packages?
PC: Antec P182B | Asus P8Z77-V PRO | Intel i5 3570k | 16GB DDR3 | GeForce 450GTS | 4TB HDD | Pioneer BDR-207D | Asus Xonar DX | Altec Lansing CS21 | Eizo EV2736W-BK | Arch Linux x86_64
HTPC: Antec NSK2480 | ASUS M3A78-EM (AMD 780G) | AMD Athlon X3 425 | 8GB DDR2 | GeForce G210 | 2TB HDD | Arch Linux x86_64
Server: Raspberry Pi (model B) | 512MB RAM | 750GB HDD | Arch Linux ARM
Offline
While you wait for an update to pacman, you could do the following:
* uninstall any packages that have put files in /usr/var
* add the following line to /etc/fstab
/var /usr/var none bind 0 0
* mount /usr/var
* reinstall the packages from step 1.
Note that pacman will still give you errors when updating the filesystem package, something along the lines of "could not extract /usr/var, mountpoint busy", but this isn't anything to worry about.
Offline
Do any developers know about this yet? I'm having this problem too and would like to see an official fix...
Last edited by jftaylor21 (2007-08-04 14:44:22)
Offline
Do any developers know about this yet? I'm having this problem too and would like to see an official fix...
In case you missed the bug report :
http://bugs.archlinux.org/task/7484#comment17865
pacman roulette : pacman -S $(pacman -Slq | LANG=C sort -R | head -n $((RANDOM % 10)))
Offline