[Bug 662711] Re: NFS user/group mapping not working in 10.10

[Steve Langasek]

On Wed, Aug 17, 2011 at 06:51:31AM -0000, exa wrote:
> This bug persists in Ubuntu 11.04 on amd64. The nfsv4 is absolutely not
> working, can anybody tell me why this terrible code is the default?

It's not "terrible code".  NFSv4 works perfectly well if configured.

> Please remove this non-functional kernel server thing from the
> distribution,

That's not a reasonable request by any measure.  It's perfectly functional
for many people - myself included.

> I'll check again about NEED_IDMAPD, it's probably set on my system.

I don't know why you think it's "probably set on your system".  It wouldn't
be set by default.  If it *is* set on your system and you're experiencing
problems, then you're seeing a different issue than this one.

> BTW, this is likely a 64-bit problem, as that number is -2, right? Maybe
> it's an exceptionally bad programming error. I guess I won't see this
> problem on i386.

Incorrect.

> in this case, why is the nfs-user-server package removed from the
> distribution,

Because that's a dead project with a variety of other deficiencies, and the
Debian package maintainer requested its removal.

> why are the choices being limited despite the fact that this bug has not
> been solved for over a year?

nfs-user-server was removed well before this bug became an issue.

> Or are you not testing these things on 64-bit machines?

This has nothing to do with 32- vs 64-bit systems.  (NFSv4 works fine here
on 64-bit installs.)

> BTW, the claims that this can be fixed simply by changing the
> configuration seems to be wrong. The default config in 11.04 already
> turns on that non-working idmapd.

idmapd is turned on by default only on servers, and on clients which specify
nfs4 as a filesystem type in /etc/fstab.  Because mount.nfs now negotiates
NFSv4 first if available, this is no longer the correct default behavior; we
should instead start idmapd unconditionally.

So this is definitely a bug - but it's also one for which there is a trivial
workaround.  Either edit /etc/default/nfs-common to start idmapd, or if your
server advertises NFSv4 but is not configured to do id mapping correctly,
use nfsvers=3 in your mount options.


-- 
Steve Langasek                   Give me a lever long enough and a Free OS
Debian Developer                   to set it on, and I can move the world.
Ubuntu Developer                                    http://www.debian.org/
slangasek at ubuntu.com                                     vorlon at debian.org


** Changed in: nfs-utils (Ubuntu)
   Importance: Undecided => Medium

** Changed in: nfs-utils (Ubuntu)
       Status: Confirmed => Triaged

** Summary changed:

- NFS user/group mapping not working in 10.10
+ idmap should be started by default because mount.nfs now negotiates NFSv4 before NFSv3

-- 
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to nfs-utils in Ubuntu.
https://bugs.launchpad.net/bugs/662711

Title:
  idmap should be started by default because mount.nfs now negotiates
  NFSv4 before NFSv3

Status in “nfs-utils” package in Ubuntu:
  Triaged

Bug description:
  I have a NFS client/server setup where both client and server are
  Ubuntu 10.10 (both upgraded from 10.4)

  To make UID and GID mapping trivial, I've made sure that clients and
  server all have the same users and groups with the same IDs. This used
  to work fine. However now the client is always displaying 4294967294
  for the UID and GID but - and here is the strange bit - if I create a
  file on the client it shows up on the server with the correct user and
  group (but on the client still with 4294967294).

  I posted this originally on the forums, and decided to file this bug
  when 2 other people reported having the same problem since upgrading
  to 10.10. In both cases they were using Ubuntu as client and Solaris
  as server. See thread here:
  http://ubuntuforums.org/showthread.php?p=9983624

  Additional info:

  /etc/exports line on the server:
  data/fileserver 192.168.1.0/255.255.255.0(rw,sync,no_subtree_check)

  /etc/fstab line on the client:
  htpc:/data/fileserver /data/fileserver nfs defaults 0 0

  Trying to chown a file on the client gives the error "chown: changing
  ownership of `somefile': Invalid argument"

  ProblemType: Bug
  DistroRelease: Ubuntu 10.10
  Package: nfs-common 1:1.2.2-1ubuntu1
  ProcVersionSignature: Ubuntu 2.6.35-22.34-generic 2.6.35.4
  Uname: Linux 2.6.35-22-generic x86_64
  NonfreeKernelModules: nvidia
  Architecture: amd64
  Date: Mon Oct 18 15:40:16 2010
  ProcEnviron:
   PATH=(custom, user)
   LANG=en_US.utf8
   SHELL=/bin/bash
  SourcePackage: nfs-utils

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nfs-utils/+bug/662711/+subscriptions