[Bug 1037192] Re: NFS shares are mounted with wrong clientaddr or not at all

[sandro dentella]

I have a related problem in the sense that an LTSP fat client can't nfs
mount /home. Mounting by hand  succedes w/o any problem and also running
'mountall' from command line, but when boot finises /home is not
mounted. I'm on Ubuntu 12.04 and mountall  2.36.

I added same debug info as suggested in mountall.conf logging to
/dev/mountall.log and I see that the last part states:

montaggio di /home
local 3/3 remote 0/0 virtual 11/11 swap 0/0
local 3/3 remote 0/0 virtual 11/11 swap 0/0
mount /home [639] uscito normalmente
local 3/3 remote 0/0 virtual 11/11 swap 0/0

"uscito normalmente" means normal exit. I wanted to check if at that
point  /home is mounted but I couldn't manage to log the output of df:

  df -h > /dev/df.log 2>&1    does not log anything nor creates an empty
file. Any suggestion on the origin of the problem or on  further test to
do?

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

Title:
  NFS shares are mounted with wrong clientaddr or not at all

Status in “mountall” package in Ubuntu:
  New

Bug description:
  With the following fstab:

  proc /proc proc nodev,noexec,nosuid 0 0
  /dev/mapper/vg0-fat_client / ext4 relatime,errors=remount-ro 0 1
  /dev/mapper/vg0-swap none swap sw 0 0
  spitzer:/opt /opt nfs4 auto 0 0
  spitzer:/home /home nfs4 auto 0 0

  The  /opt and /home are sometimes not mounted at all, and sometimes
  with the wrong clientaddr:

  $ mount | grep nfs
  rpc_pipefs on /var/lib/nfs/rpc_pipefs type rpc_pipefs (rw)
  spitzer:/home on /home type nfs4 (rw,clientaddr=0.0.0.0,addr=192.168.1.2)
  spitzer:/opt on /opt type nfs4 (rw,clientaddr=0.0.0.0,addr=192.168.1.2)

  Since this happens on all clients (they all get same clientaddr), this
  results in a frozen mount (cf
  http://thread.gmane.org/gmane.linux.nfs/47780)

  The "spitzer" host is only reachable via a tinc VPN, and mounting (or
  remounting) manually after boot always works and results in the
  correct clientaddr, so I believe that mountall is attempting to mount
  this too early.

  ProblemType: Bug
  DistroRelease: Ubuntu 10.04
  Package: mountall 2.15.3
  ProcVersionSignature: Ubuntu 3.0.0-23.39~lucid1-server 3.0.36
  Uname: Linux 3.0.0-23-server x86_64
  Architecture: amd64
  Date: Wed Aug 15 12:16:17 2012
  ProcEnviron:
   PATH=(custom, user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: mountall

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mountall/+bug/1037192/+subscriptions