You are not logged in.

#1 2012-01-19 00:09:11

timothy
Member
Registered: 2012-01-18
Posts: 4

Checking for file conflicts: could not get filesystem information

When I try to install a new package with pacman 4 I got the following warning just after pacman has done "checking for file conflicts":

warning: could not get filesystem information for /var/lib/ntp/etc/resolv.conf (deleted): No such file or directory

After the warning message is printed, the installation continues normally.  This warning message has never shown up before.
I have ntpd running in a chroot as a non-root user (instructions).

I am wondering if anyone else gets the same warning message and if this 'problem' can be solved.

I forgot to say: the file is still there according to ls and is not empty, but the contents differs form the /etc/resolv.conf-file.

tim@tim-notebook:~$ cat /var/lib/ntp/etc/resolv.conf && echo && cat /etc/resolv.conf 
# Generated by NetworkManager

# Generated by NetworkManager
nameserver 192.168.1.1

Last edited by timothy (2012-01-19 00:15:51)

Offline

#2 2012-01-19 10:25:52

karol
Archivist
Registered: 2009-05-06
Posts: 25,440

Re: Checking for file conflicts: could not get filesystem information

Please check which package does /var/lib/ntp/etc/resolv.conf belong to.

Offline

#3 2012-01-19 18:55:51

timothy
Member
Registered: 2012-01-18
Posts: 4

Re: Checking for file conflicts: could not get filesystem information

I'm not sure how to do that or I do not know exactly what you mean.

tim@tim-notebook:~$ pkgfile -gs "*etc/resolv.conf"
core/filesystem
extra/archboot

But you probably already knew that.

Running pacman with the --debug option did not gave me any more clues.  All I know now, is that this message is printed when the moundpoints are examined:

stderr 'pacman -Syu--debug' output wrote:

(...)
debug: checking possible conflict: /var/lib/
debug: file is a directory, not a conflict
debug: checking available disk space
warning: could not get filesystem information for /var/lib/ntp/etc/resolv.conf (deleted): No such file or directory
debug: mountpoint: /var/lib/ntp/proc
debug: mountpoint: /var/lib/ntp/lib
debug: mountpoint: /var/lib/ntp/etc/services
debug: mountpoint: /tmp
(...)

Offline

#4 2012-01-19 19:41:02

karol
Archivist
Registered: 2009-05-06
Posts: 25,440

Re: Checking for file conflicts: could not get filesystem information

I meant running 'pacman -Qo /var/lib/ntp/etc/resolv.conf' - if this file exists at all.

Offline

#5 2012-01-19 19:47:00

timothy
Member
Registered: 2012-01-18
Posts: 4

Re: Checking for file conflicts: could not get filesystem information

Alright, thank you for your help.  It seems "no package owns /var/lib/ntp/etc/resolv.conf".
I tried to look in the source code and found out this message is printed when 'statvfs()' fails.  Not sure why it fails...

Offline

#6 2012-07-18 05:11:55

karamaz0v
Member
From: Argentina
Registered: 2012-07-18
Posts: 10

Re: Checking for file conflicts: could not get filesystem information

I'm having exactly this same warning message since I configured ntpd following those same instructions.

Did you solve it in some way?

Offline

#7 2012-07-20 18:45:39

timothy
Member
Registered: 2012-01-18
Posts: 4

Re: Checking for file conflicts: could not get filesystem information

I didn't quite 'solved' it.
I found out that it has nothing to do with packman as I was assuming.  'mount' shows nothing strange, but 'cat /proc/mounts' does: "/dev/(...) /var/lib/ntp/etc/resolv.conf\040(deleted) (...)".  Doing

# umount /var/lib/ntp/etc/resolv.conf && mount /var/lib/ntp/etc/resolv.conf

'solves' this problem until next reboot.
I've never found out why mount doesn't do its work properly.

Offline

Board footer

Powered by FluxBB