[Bug 662711] Re: idmap should be started by default because mount.nfs now negotiates NFSv4 before NFSv3

[Launchpad Bug Tracker]

This bug was fixed in the package nfs-utils - 1:1.2.4-1ubuntu3

---------------
nfs-utils (1:1.2.4-1ubuntu3) precise; urgency=low

  * debian/nfs-common.defaults, debian/nfs-common.idmapd.upstart: idmapd
    should always be started automatically, because we can no longer assume
    that a mount of type 'nfs' in /etc/fstab is not nfs4.  This also lets
    things work by default with nfs4 autofs.  LP: #662711.
  * Move /var/lib/nfs/rpc_pipefs to /run/rpc_pipefs.  This does not belong
    in /var/lib.
  * Ignore errors from mount if the filesystem is already mounted.
    LP: #811823.
 -- Steve Langasek <steve.langasek at ubuntu.com>   Thu, 27 Oct 2011 12:04:58 -0700

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

-- 
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:
  Fix Released

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