← Back to team overview

documentation-packages team mailing list archive

[Bug 1019938] Re: SettingUpNFSHowTo possible mistake

 

Please note that the page in question is a wiki page which anybody can edit - including you. ;-)
https://help.ubuntu.com/community/WikiGuide
Since you seem to know how it should be changed, it would be great if you could fix it.

Due to the nature of the community help wiki, you can't request changes
to it in the form of bug reports.

** Changed in: ubuntu-docs (Ubuntu)
       Status: New => Invalid

-- 
You received this bug notification because you are a member of
Documentation Packages, which is subscribed to ubuntu-docs in Ubuntu.
https://bugs.launchpad.net/bugs/1019938

Title:
  SettingUpNFSHowTo possible mistake

Status in “ubuntu-docs” package in Ubuntu:
  Invalid

Bug description:
  In "NFSv4 client" section, "Note that nfs-server:/export is not
  necessary in NFSv4" is probably not true.

  I have a 32 nodes KVM cluster. NFS, host filesystem, KVM storage pool,
  are all placed on SSD. KVM guests are connected to host through virtio
  drived GB ethernet.

  I followed this guide to configure NFS:
  https://help.ubuntu.com/community/SettingUpNFSHowTo

  The problem was that, when I execute a program simultaneously (through
  cssh) on 32 nodes, there were always a number of nodes that
  encountered "input/output error". The /var/log/messages on client
  shows "state manager failed on NFSv4 server with error 10022".

  Interestingly, by changing the item in /etc/fstab from:
      some-host:/some-dir    /nfs    nfs    rw,bg,hard,intr    0    0
  into:
      some-host:/export/some-dir    /nfs    nfs    rw,bg,hard,intr    0    0
  fixed the problem.

  I don't know how exactly this happens. It's probably caused by some problem in NFS server when it tries to find the right path when  all 32 clients are trying to mount NFS at the same time.
  It's probably a bug in NFS but before it is fixed in NFS, should the Wiki give the instruction that /export is necessary?

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