You are not logged in.
Sometimes I really wonder if any testing is done before new packages are moved in from testing.
mount -a -t nfs
mount.nfs: access denied by server while mounting <xxxxxxxxxxxxxxxxxx>
Here is a line from the /etc/exports on the server:
<xxxxxxxxxxxxxxxxxx> 192.168.1.0/24(sync,no_root_squash,rw,nohide)
And an equivalent line from the fstab on the clients:
<xxxxxxxxxxxxxxxxxx> <yyyyyyyyy> nfs noatime,bg,hard,rsize=32768,wsize=32768 0 0
Server is running latest lts kernel.
Clients are running latest kernel.
PS: This setup has been running flawlessly for ages (years).
PS2: Again:
Is there any testing done before new packages are moved in from testing?
Offline
Downgrading nfs-utils to previous version -> 1.2.2 -> restores full functionality -> fixes the problem.
Offline
Downgrading nfs-utils to previous version -> 1.2.2 -> restores full functionality -> fixes the problem.
i really don't understand how a simple downgrade for only one package can work since newer nfs-utils is compiled against krb5 instead of heimdal. My guesses is that you didn't fully updated your system in the first place?
Give what you have. To someone, it may be better than you dare to think.
Offline
There was a full update (apart from the two pulseaudio packages which I do not have installed since it introduces noise in my music).
Downgrade was only needed in the server part, for the functionality to return.
Last edited by wantilles (2011-05-13 17:25:10)
Offline
care to report this issue on our tracker and provide some logs?
Give what you have. To someone, it may be better than you dare to think.
Offline
1. Which logs would help?
2. The problem, in this specific case, is that all pacman funcionality is centrally placed on the nfs v3 server (in shared directories) via symlinks.
So if a client boots and cannot mount the nfs v3 shares, no changes in packages can be applied on the client.
Last edited by wantilles (2011-05-13 17:25:32)
Offline