Post new topic   Reply to topic
View previous topic Printable version Log in to check your private messages View next topic
Author Message
qordOffline
15 Post subject: [solved] nfs / rpc broken by d-u  PostPosted: 28.03.2011, 22:31



Joined: 2010-12-14
Posts: 7

Status: Offline
Hello!

It seems that todays update of nfs-common and nfs-kernel-server to version 1.2.3 breaks nfs.

I have one aptosid client that connects to a squeeze-based nfs-server which had issued with rpc.statd on the client. That could be fixed with switching from nfs3 to nfs4 (which doesn't use statd).

My second setup has aptosid client and server and I get the following in the syslog when starting nfs-kernel-server:

      Code:

Mar 29 00:28:32 rei kernel: [348501.247873] svc: failed to register lockdv1 RPC service (errno 97).
Mar 29 00:28:32 rei kernel: [348501.247981] NFSD: Using /var/lib/nfs/v4recovery as the NFSv4 state recovery directory
Mar 29 00:28:32 rei kernel: [348501.248115] NFSD: starting 90-second grace period
Mar 29 00:28:32 rei rpc.mountd[3627]: mountd: could not create listeners


Mounting shares on the client fails with a "permission denied" message...

-cord
 
 View user's profile Send private message  
Reply with quote Back to top
arwaOffline
Post subject: RE: nfs / rpc broken by d-u  PostPosted: 30.03.2011, 08:18



Joined: 2010-09-11
Posts: 183

Status: Offline
I have the problem that after the latest D-U the system does not even boot anymore because the system hangs when trying to start statd. Is there a way to skip the statd?

I currently booted a backup partition. To solve the issue I will rename (deactivate) the nfs-common startup script in /etc/init.d/. Is there a better way to do this?

Is there a disadvantage of using nfs4?

Does NFS on your first client work with nfs4?

Thanks,
arwa
 
 View user's profile Send private message  
Reply with quote Back to top
blackholeOffline
Post subject: RE: nfs / rpc broken by d-u  PostPosted: 30.03.2011, 12:13



Joined: 2010-09-12
Posts: 110

Status: Offline
My system can boot but some "failed" messages. Nfs is no working
 
 View user's profile Send private message  
Reply with quote Back to top
qordOffline
Post subject: Re: RE: nfs / rpc broken by d-u  PostPosted: 30.03.2011, 15:01



Joined: 2010-12-14
Posts: 7

Status: Offline
      arwa wrote:

Is there a disadvantage of using nfs4?

Does NFS on your first client work with nfs4?


After converting the aptosid-squeeze setup to nfs4 it all seemed to work until I noticed that idmapping was broken and all files on the nfs drives belonged to nouser:nogroup (which had interesting effects on the backup that is made via nfs on that system...).

I reverted the system to nfs-common 1.2.2 from the testing repo and put nfs-common on "hold", that worked.

-cord
 
 View user's profile Send private message  
Reply with quote Back to top
belzeOffline
Post subject: RE: Re: RE: nfs / rpc broken by d-u  PostPosted: 30.03.2011, 19:26



Joined: 2010-09-13
Posts: 100

Status: Offline
can anyone find a bug number in debian for this bug?
I can't update to NFS4 nor on my server nor on aptosid... for me this is a very HOT problem!!!
 
 View user's profile Send private message  
Reply with quote Back to top
DeepDayzeOffline
Post subject: RE: Re: RE: nfs / rpc broken by d-u  PostPosted: 31.03.2011, 00:32



Joined: 2010-09-11
Posts: 616
Location: USA
Status: Offline
There's a bug here:

http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=620059

One solution is to replace portmap with rpcbind as portmap does not currently support IPv6. Apparently the updated nfs packages now make use of IPv6 as a requirement

EDIT: Rpcbind works for me as well with the new NFS packages


Last edited by DeepDayze on 31.03.2011, 00:38; edited 1 time in total
 
 View user's profile Send private message  
Reply with quote Back to top
coincoinOffline
Post subject: RE: Re: RE: nfs / rpc broken by d-u  PostPosted: 31.03.2011, 00:32



Joined: 2011-03-31
Posts: 1

Status: Offline
Use rpcbind instead of portmap (see debian bug #620059).
 
 View user's profile Send private message  
Reply with quote Back to top
arwaOffline
Post subject:   PostPosted: 31.03.2011, 15:23



Joined: 2010-09-11
Posts: 183

Status: Offline
Yes, indeed, with rpcbind everything works fine again.

As info regarding the hanging boot when starting statd: This just happens about every second boot. After a reset the kernel may boot again, so that you do not need any special tricks to get into the system for installing rpcbind.
 
 View user's profile Send private message  
Reply with quote Back to top
belzeOffline
Post subject:   PostPosted: 01.04.2011, 00:04



Joined: 2010-09-13
Posts: 100

Status: Offline
thanks a lot!
 
 View user's profile Send private message  
Reply with quote Back to top
detaosOffline
Post subject:   PostPosted: 01.04.2011, 23:17
Team Member


Joined: 2010-08-26
Posts: 166
Location: floating in the ether
Status: Offline
Confirmed and marked as solved.

_________________
#aptosid-art ftw!
(what would cleary do?)
 
 View user's profile Send private message Send e-mail Visit poster's website  
Reply with quote Back to top
blackholeOffline
Post subject:   PostPosted: 11.04.2011, 13:36



Joined: 2010-09-12
Posts: 110

Status: Offline
I have some error messages at boot:

      Quote:
rpcbind: Cannot open '/var/run/rpcbind/rpcbind.xdr' file for reading, errno 2
(No such file or directory)
 
 View user's profile Send private message  
Reply with quote Back to top
Display posts from previous:     
Jump to:  
All times are GMT - 12 Hours
Post new topic   Reply to topic
View previous topic Printable version Log in to check your private messages View next topic
Powered by Zafenio