[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 Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1019938 Title: SettingUpNFSHowTo possible mistake To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-docs/+bug/1019938/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1019938] Re: SettingUpNFSHowTo possible mistake
** Tags added: wiki -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1019938 Title: SettingUpNFSHowTo possible mistake To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-docs/+bug/1019938/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 1019938] Re: SettingUpNFSHowTo possible mistake
2012/7/12, b khosravi : > UNSUBSCRIBE > > 2012/7/6, Song Gao : >> OK. A feedback from NFS community indicates that, the reason why >> replacing /some-dir with /export/some-dir solved the problem was that, >> NFSv4 client failed to find the right path on NFS server, so it fell >> back to NFSv2. >> >> However, in the reply from mail list(http://www.spinics.net/lists/linux- >> nfs/msg31326.html ), Bruce also mentioned an outdated part in this >> document. Following is the quoted text: >> >>> The advice to use "fsid=0" in the ubuntu howto is out of date. With a >>> recent server you should just export and mount /export/tigers as you >>> would with NFSv3. >> >> -- >> You received this bug notification because you are subscribed to ubuntu- >> docs in Ubuntu. >> https://bugs.launchpad.net/bugs/1019938 >> >> Title: >> SettingUpNFSHowTo possible mistake >> >> Status in “ubuntu-docs” package in Ubuntu: >> New >> >> 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/nfsnfsrw,bg,hard,intr00 >> into: >> some-host:/export/some-dir/nfsnfsrw,bg,hard,intr0 >> 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 >> > -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1019938 Title: SettingUpNFSHowTo possible mistake To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-docs/+bug/1019938/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 1019938] Re: SettingUpNFSHowTo possible mistake
UNSUBSCRIBE 2012/7/6, Song Gao : > OK. A feedback from NFS community indicates that, the reason why > replacing /some-dir with /export/some-dir solved the problem was that, > NFSv4 client failed to find the right path on NFS server, so it fell > back to NFSv2. > > However, in the reply from mail list(http://www.spinics.net/lists/linux- > nfs/msg31326.html ), Bruce also mentioned an outdated part in this > document. Following is the quoted text: > >> The advice to use "fsid=0" in the ubuntu howto is out of date. With a >> recent server you should just export and mount /export/tigers as you >> would with NFSv3. > > -- > You received this bug notification because you are subscribed to ubuntu- > docs in Ubuntu. > https://bugs.launchpad.net/bugs/1019938 > > Title: > SettingUpNFSHowTo possible mistake > > Status in “ubuntu-docs” package in Ubuntu: > New > > 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/nfsnfsrw,bg,hard,intr00 > into: > some-host:/export/some-dir/nfsnfsrw,bg,hard,intr0 > 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 > -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1019938 Title: SettingUpNFSHowTo possible mistake To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-docs/+bug/1019938/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1019938] Re: SettingUpNFSHowTo possible mistake
OK. A feedback from NFS community indicates that, the reason why replacing /some-dir with /export/some-dir solved the problem was that, NFSv4 client failed to find the right path on NFS server, so it fell back to NFSv2. However, in the reply from mail list(http://www.spinics.net/lists/linux- nfs/msg31326.html ), Bruce also mentioned an outdated part in this document. Following is the quoted text: > The advice to use "fsid=0" in the ubuntu howto is out of date. With a > recent server you should just export and mount /export/tigers as you > would with NFSv3. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1019938 Title: SettingUpNFSHowTo possible mistake To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-docs/+bug/1019938/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
