Bug#624414: changes in squeeze affecting a smooth NFS upgrade/use

[Luk Claes]

Package: release-notes
Severity: normal

Hi

I keep telling me I should write something that could be included into the Release Notes about things people should be aware of when using NFS in squeeze. Instead of trying to have a coherent text I'll just list some topics:

- default NFS uses version 4 in squeeze, one can work around failures to mount because of this by mentioning the -vers=3 option explicitly when mounting (or in fstab)
- when using Kerberos default encryption has changed, one can work around it by specifying an older encryption type explicitly (-sec=...) when mounting
- the chance that NFS related daemons are not started at boot are increased both for NFS clients as well as NFS servers, can be worked round by restarting portmap (or rpcbind), nfs-common and nfs-kernel-server in that order for the ones that are installed
- NFSv4 needs the idmap daemon to be started, can be worked around by updating /etc/default/nfs-common (and /etc/default/nfs-kernel-server) to have NEED_IDMAPD=yes and restart nfs-common (and nfs-kernel-server)
- for switching the server exports to NFSv4 one needs to specify a root of all exported filesystems specified by including the fsid=0 (or fsid=root) option, one does not need to specify fsid for any other exported filesystem unless it has no uuid (in that case use a small integer that will be used like the uuid)

Cheers

Luk

[David Prévot]

Control: tags -1 moreinfo

Hi Luk,

Post by Luk Claes
Package: release-notes
Severity: normal
Hi
I keep telling me I should write something that could be included into the Release Notes about things people should be aware of when using NFS in squeeze.

Is this issue still relevant for Wheezy? I suspect it isn’t and advise
the RN wizard to close it (I may do so myself next time I come across
this bug report unless more information is provided).

Regards

David

P.-S.: keeping context for your convenience.

Post by Luk Claes
- default NFS uses version 4 in squeeze, one can work around failures to mount because of this by mentioning the -vers=3 option explicitly when mounting (or in fstab)
- when using Kerberos default encryption has changed, one can work around it by specifying an older encryption type explicitly (-sec=...) when mounting
- the chance that NFS related daemons are not started at boot are increased both for NFS clients as well as NFS servers, can be worked round by restarting portmap (or rpcbind), nfs-common and nfs-kernel-server in that order for the ones that are installed
- NFSv4 needs the idmap daemon to be started, can be worked around by updating /etc/default/nfs-common (and /etc/default/nfs-kernel-server) to have NEED_IDMAPD=yes and restart nfs-common (and nfs-kernel-server)
- for switching the server exports to NFSv4 one needs to specify a root of all exported filesystems specified by including the fsid=0 (or fsid=root) option, one does not need to specify fsid for any other exported filesystem unless it has no uuid (in that case use a small integer that will be used like the uuid)

[Debian Bug Tracking System]

Post by David Prévot
tags -1 moreinfo

Bug #624414 [release-notes] changes in squeeze affecting a smooth NFS upgrade/use
Added tag(s) moreinfo.
--
624414: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=624414
Debian Bug Tracking System
Contact ***@bugs.debian.org with problems

[Debian Bug Tracking System]

Your message dated Sat, 29 Apr 2017 10:37:00 +0000
with message-id <892c8f4b-b84d-ceee-7d4c-***@thykier.net>
and subject line Re: Bug#624414: changes in squeeze affecting a smooth NFS upgrade/use
has caused the Debian Bug report #624414,
regarding changes in squeeze affecting a smooth NFS upgrade/use
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ***@bugs.debian.org
immediately.)