[Bug 1090597] [NEW] Recent update killed my NAS mount

[neon John]

Public bug reported:

Release is 12.04 LTS running Gnome in the "fallback" (normal) mode.

Two updates have come in since I last rebooted.  When I rebooted today,
my Western Digital NAS World Book Edition would not mount using NFS.
Here are the /etc/fstab entries that I've tried.

#192.168.0.253:/nfs/Public	/media/public nfs nolock
#192.168.0.253:/nfs/Download	/media/download nfs nolock

# 192.168.0.253:/nfs/Public  /media/public nfs nfsvers=3,hard,intr,auto,nolock 0 0
# 192.168.0.253:/nfs/Download  /media/download nfs nfsvers=3,hard,intr,auto,nolock 0 0

192.168.0.253:Public	/media/public smbfs
192.168.0.253:Download	/media/download smbfs

192.168.0.253:usb1-1share1 /media/2tb smbfs


The top two are what I've been using for several years.  the middle pair (and many variations) are what I've tried based on reading other NFS bug reports.  The 3rd pair of statements using smbfs DOES mount the partitions as SAMBA shares so I know that the NAS isn't hosed.  In the process of debugging, I upgraded the NAS firmware to the latest version.

The last line, usb1-1share1, has always been required to mount an
external drive connected to the NAS.

Here is the output of "sudo mount -a"

jgd at neonjohn:/etc$ sudo mount -a -v
mount: proc already mounted on /proc
mount: 192.168.0.253:usb1-1share1 already mounted on /media/2tb
mount: UUID=4459465f-5994-4726-b0ec-75853e5e5084 already mounted on /media/1tbb
mount.nfs: timeout set for Fri Dec 14 18:14:12 2012
mount.nfs: trying text-based options 'nfsvers=4,nolock,addr=192.168.0.253,clientaddr=100.74.9.243'
mount.nfs: mount(2): Protocol not supported
mount.nfs: Protocol not supported
mount.nfs: timeout set for Fri Dec 14 18:14:12 2012
mount.nfs: trying text-based options 'nolock,vers=4,addr=192.168.0.253,clientaddr=100.74.9.243'
mount.nfs: mount(2): Protocol not supported
mount.nfs: trying text-based options 'nolock,addr=192.168.0.253'
mount.nfs: prog 100003, trying vers=3, prot=6
mount.nfs: portmap query retrying: RPC: Timed out
mount.nfs: prog 100003, trying vers=3, prot=17
mount.nfs: portmap query failed: RPC: Timed out
mount.nfs: mount to NFS server '192.168.0.253:/nfs/Download' failed: timed out, giving up

Mounting the partitions as SAMBA shares gets me back to work but I don't
like it.  No idea yet what that style mount will do to SubVersion.

John

** Affects: nfs-utils (Ubuntu)
     Importance: Undecided
         Status: New

-- 
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/1090597

Title:
  Recent update  killed my NAS mount

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

Bug description:
  Release is 12.04 LTS running Gnome in the "fallback" (normal) mode.

  Two updates have come in since I last rebooted.  When I rebooted
  today, my Western Digital NAS World Book Edition would not mount using
  NFS.  Here are the /etc/fstab entries that I've tried.

  #192.168.0.253:/nfs/Public	/media/public nfs nolock
  #192.168.0.253:/nfs/Download	/media/download nfs nolock

  # 192.168.0.253:/nfs/Public  /media/public nfs nfsvers=3,hard,intr,auto,nolock 0 0
  # 192.168.0.253:/nfs/Download  /media/download nfs nfsvers=3,hard,intr,auto,nolock 0 0

  192.168.0.253:Public	/media/public smbfs
  192.168.0.253:Download	/media/download smbfs

  192.168.0.253:usb1-1share1 /media/2tb smbfs

  
  The top two are what I've been using for several years.  the middle pair (and many variations) are what I've tried based on reading other NFS bug reports.  The 3rd pair of statements using smbfs DOES mount the partitions as SAMBA shares so I know that the NAS isn't hosed.  In the process of debugging, I upgraded the NAS firmware to the latest version.

  The last line, usb1-1share1, has always been required to mount an
  external drive connected to the NAS.

  Here is the output of "sudo mount -a"

  jgd at neonjohn:/etc$ sudo mount -a -v
  mount: proc already mounted on /proc
  mount: 192.168.0.253:usb1-1share1 already mounted on /media/2tb
  mount: UUID=4459465f-5994-4726-b0ec-75853e5e5084 already mounted on /media/1tbb
  mount.nfs: timeout set for Fri Dec 14 18:14:12 2012
  mount.nfs: trying text-based options 'nfsvers=4,nolock,addr=192.168.0.253,clientaddr=100.74.9.243'
  mount.nfs: mount(2): Protocol not supported
  mount.nfs: Protocol not supported
  mount.nfs: timeout set for Fri Dec 14 18:14:12 2012
  mount.nfs: trying text-based options 'nolock,vers=4,addr=192.168.0.253,clientaddr=100.74.9.243'
  mount.nfs: mount(2): Protocol not supported
  mount.nfs: trying text-based options 'nolock,addr=192.168.0.253'
  mount.nfs: prog 100003, trying vers=3, prot=6
  mount.nfs: portmap query retrying: RPC: Timed out
  mount.nfs: prog 100003, trying vers=3, prot=17
  mount.nfs: portmap query failed: RPC: Timed out
  mount.nfs: mount to NFS server '192.168.0.253:/nfs/Download' failed: timed out, giving up

  Mounting the partitions as SAMBA shares gets me back to work but I
  don't like it.  No idea yet what that style mount will do to
  SubVersion.

  John

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