[opensuse-factory] Leap 15.0 Beta: I can't make NFS work as client using YaST
Hi, I tried to setup NFS as client first using YaST. I told it to open the firewall port (it does not stick when I fire YaST again), then to browse the network for hosts: finds none. So I type the IP. Then I try to select directories: finds none. Then I tick "NFSv4share": it finds some (and incorrect, IMO): / /data /home_aux /var They are incorrect, I think, because the exports file on the server has: /data/storage_c/repositorios_zypp/ .... /home/ ... /home1/ ... /home_aux/ ... /data/storage_b/ ... /var/spool/news/ ... I tried with /data, and did not work: linux-9vao:~ # mount -v /data/data_nfs_tc/ mount.nfs4: timeout set for Sun Mar 11 14:15:33 2018 mount.nfs4: trying text-based options 'vers=4.2,addr=192.168.1.14,clientaddr=192.168.1.128' mount.nfs4: mount(2): Device or resource busy linux-9vao:~ # mount -v /data/data_nfs_tc/ mount.nfs4: timeout set for Sun Mar 11 14:16:54 2018 mount.nfs4: trying text-based options 'vers=4.2,addr=192.168.1.14,clientaddr=192.168.1.128' mount.nfs4: mount(2): Device or resource busy linux-9vao:~ # I later copied an entry from fstab from another install, and it worked instantly. Why doesn't YaST work, is it a bug, or work in progress, or a firewall problem somewhere, or what? -- Cheers / Saludos, Carlos E. R. (from 42.2 x86_64 "Malachite" at Telcontar)
Carlos E. R. wrote:
Hi,
I tried to setup NFS as client first using YaST. I told it to open the firewall port (it does not stick when I fire YaST again), then to browse the network for hosts: finds none.
FWIW, I never use that yast module, but I tried the same on my leap15 test system (no firewall) - it found four hosts offering NFS, that worked fine.
So I type the IP.
On the first attempt, I entered the name. Worked fine.
Then I try to select directories: finds none.
I got the list of exported directories. /home /srv/nfsroot/office... /srv/nfsroot/hpsrv0... /srv/nfsroot/zotac1
Then I tick "NFSv4share": it finds some (and incorrect, IMO):
/ /data /home_aux /var
They are incorrect, I think, because the exports file on the server has:
I got / /srv /home That does look odd. Ignoring those, the fstab is correctly amended and the nfs share could be mounted. (manually).
Why doesn't YaST work, is it a bug, or work in progress, or a firewall problem somewhere, or what?
Try stopping the firewall, repeat the exercise and see if that changes the behaviour. -- Per Jessen, Zürich (8.4°C) http://www.dns24.ch/ - your free DNS host, made in Switzerland. -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
On Mon, Mar 12, 2018 at 9:57 AM, Per Jessen <per@computer.org> wrote: ...
I got the list of exported directories.
/home /srv/nfsroot/office... /srv/nfsroot/hpsrv0... /srv/nfsroot/zotac1
Then I tick "NFSv4share": it finds some (and incorrect, IMO):
/ /data /home_aux /var
They are incorrect, I think, because the exports file on the server has:
I got
/ /srv /home
That does look odd.
Not for NFSv4. In NFSv4 design all exported resources belong to a single (virtual) tree. So this is actually correct - as long as you can drill down and see nested resources. And Carlos tried to mount using NFSv4. Of course he did not explain whether "copied fstab entries" were using NFSv3 or not, so we have no idea if this is the reason for this problem. -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
Andrei Borzenkov wrote:
On Mon, Mar 12, 2018 at 9:57 AM, Per Jessen <per@computer.org> wrote: ...
I got the list of exported directories.
/home /srv/nfsroot/office... /srv/nfsroot/hpsrv0... /srv/nfsroot/zotac1
Then I tick "NFSv4share": it finds some (and incorrect, IMO):
/ /data /home_aux /var
They are incorrect, I think, because the exports file on the server has:
I got
/ /srv /home
That does look odd.
Not for NFSv4. In NFSv4 design all exported resources belong to a single (virtual) tree. So this is actually correct - as long as you can drill down and see nested resources.
Right, thanks for explaining that. I did have some nagging suspicion like that, but I couldn't remember. Yast does not enable any drilling into lower level directories. Similar situation in Leap42.3, except I don't see /srv being listed. Anyway, I'll leave it to Carlos to pursue the issue. -- Per Jessen, Zürich (8.4°C) http://www.dns24.ch/ - free dynamic DNS, made in Switzerland. -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Monday, 2018-03-12 at 11:06 +0300, Andrei Borzenkov wrote:
On Mon, Mar 12, 2018 at 9:57 AM, Per Jessen <per@computer.org> wrote:
I used YaST because it should open the proper ports in the firewall, and I have no idea how to do that now ;-) Also because it sets to start the proper services (nfs, rpc, whatever).
...
I got the list of exported directories.
/home /srv/nfsroot/office... /srv/nfsroot/hpsrv0... /srv/nfsroot/zotac1
Then I tick "NFSv4share": it finds some (and incorrect, IMO):
/ /data /home_aux /var
They are incorrect, I think, because the exports file on the server has:
I got
/ /srv /home
That does look odd.
Not for NFSv4. In NFSv4 design all exported resources belong to a single (virtual) tree. So this is actually correct - as long as you can drill down and see nested resources.
And Carlos tried to mount using NFSv4. Of course he did not explain whether "copied fstab entries" were using NFSv3 or not, so we have no idea if this is the reason for this problem.
192.168.1.14:/data/storage_c/repositorios_zypp/ /data/data_nfs_tc nfs4 defaults,rw,noauto,_netdev,nfsvers=4 0 0 This line worked instantly. I simply copied the line across from working 42.3 install. - -- Cheers, Carlos E. R. (from openSUSE 42.3 x86_64 "Malachite" at Telcontar) -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iEYEARECAAYFAlqm7HkACgkQtTMYHG2NR9U2TACgh/1Yf6dxgf76ZeN2ACczq0GX InIAoIENxgaQWIe+FzwIsSyF1ax+TFbz =g8fQ -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
On 03/12/2018 10:09 PM, Carlos E. R. wrote:
On Monday, 2018-03-12 at 11:06 +0300, Andrei Borzenkov wrote:
Not for NFSv4. In NFSv4 design all exported resources belong to a single (virtual) tree. So this is actually correct - as long as you can drill down and see nested resources.
And Carlos tried to mount using NFSv4. Of course he did not explain whether "copied fstab entries" were using NFSv3 or not, so we have no idea if this is the reason for this problem.
192.168.1.14:/data/storage_c/repositorios_zypp/ /data/data_nfs_tc nfs4 defaults,rw,noauto,_netdev,nfsvers=4 0 0
This line worked instantly. I simply copied the line across from working 42.3 install.
And I doubt the original line was fully generated by yast2-nfs-client without some user intervention to refine the mount options. That line contains "nfsvers=4" which is the right and correct way of specifying the version nowadays. Unfortunately, yast2-nfs-client in 42.3 still used the legacy way, which is specifying "nfs4" in the vfstype column and no particular mount option. That is still not corrected in Leap15. So it behaves exactly the same than 42.3. So you should do exactly what you did in 42.3 - specifying the directory "by hand" (not trusting NFSv4 autodiscovery) and improving the mount options also by hand. No chance yast2-nfs-client in 42.3 generated that line automatically without the user helping it a bit. Cheers. -- Ancor González Sosa YaST Team at SUSE Linux GmbH -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
On 2018-03-13 10:31, Ancor Gonzalez Sosa wrote:
On 03/12/2018 10:09 PM, Carlos E. R. wrote:
On Monday, 2018-03-12 at 11:06 +0300, Andrei Borzenkov wrote:
Not for NFSv4. In NFSv4 design all exported resources belong to a single (virtual) tree. So this is actually correct - as long as you can drill down and see nested resources.
And Carlos tried to mount using NFSv4. Of course he did not explain whether "copied fstab entries" were using NFSv3 or not, so we have no idea if this is the reason for this problem.
192.168.1.14:/data/storage_c/repositorios_zypp/ /data/data_nfs_tc nfs4 defaults,rw,noauto,_netdev,nfsvers=4 0 0
This line worked instantly. I simply copied the line across from working 42.3 install.
And I doubt the original line was fully generated by yast2-nfs-client without some user intervention to refine the mount options.
Yes, of course, that line has been adjusted over the years. -- Cheers / Saludos, Carlos E. R. (from 42.2 x86_64 "Malachite" at Telcontar)
On 03/11/2018 09:49 PM, Carlos E. R. wrote:
Hi,
I tried to setup NFS as client first using YaST. I told it to open the firewall port (it does not stick when I fire YaST again), then to browse the network for hosts: finds none. So I type the IP.
yast2-nfs-client has never had the ability to find NFSv4 hosts, they don't announce themselves like NFSv3 hosts did. That's not specific to Leap15 or the firewall.
Then I try to select directories: finds none.
Then I tick "NFSv4share": it finds some (and incorrect, IMO):
/ /data /home_aux /var
They are incorrect, I think, because the exports file on the server has:
/data/storage_c/repositorios_zypp/ .... /home/ ... /home1/ ... /home_aux/ ... /data/storage_b/ ... /var/spool/news/ ...
I tried with /data, and did not work:
linux-9vao:~ # mount -v /data/data_nfs_tc/ mount.nfs4: timeout set for Sun Mar 11 14:15:33 2018 mount.nfs4: trying text-based options 'vers=4.2,addr=192.168.1.14,clientaddr=192.168.1.128' mount.nfs4: mount(2): Device or resource busy linux-9vao:~ # mount -v /data/data_nfs_tc/ mount.nfs4: timeout set for Sun Mar 11 14:16:54 2018 mount.nfs4: trying text-based options 'vers=4.2,addr=192.168.1.14,clientaddr=192.168.1.128' mount.nfs4: mount(2): Device or resource busy linux-9vao:~ #
I later copied an entry from fstab from another install, and it worked instantly.
Why doesn't YaST work, is it a bug, or work in progress, or a firewall problem somewhere, or what?
As Andrei replied. That's how NFSv4 works. You should see exactly the same behavior with any version of yast2-nfs-client talking to an NFSv4 server. No matter whether you are using Leap 42.X, Leap 15 or openSUSE 13.X. NFSv4 will only return one level at a time and yast2-nfs-client has never had the ability to browse down the reported tree. That being said, there are other things regarding NFS and versioning that has changed between 42.X and 15, so copying entries may still have an slightly different behavior. We plan to adjust yast2-nfs-client to make those changes obvious enough. When done, it will be explained in one of our usual blog post. ;-) Cheers. -- Ancor González Sosa YaST Team at SUSE Linux GmbH -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Monday, 2018-03-12 at 12:23 +0100, Ancor Gonzalez Sosa wrote:
On 03/11/2018 09:49 PM, Carlos E. R. wrote:
Hi,
I tried to setup NFS as client first using YaST. I told it to open the firewall port (it does not stick when I fire YaST again), then to browse the network for hosts: finds none. So I type the IP.
yast2-nfs-client has never had the ability to find NFSv4 hosts, they don't announce themselves like NFSv3 hosts did. That's not specific to Leap15 or the firewall.
Ah, so that's why. I thought it might be that some port needed to be opened on server or client.
Then I try to select directories: finds none.
Then I tick "NFSv4share": it finds some (and incorrect, IMO):
/ /data /home_aux /var
They are incorrect, I think, because the exports file on the server has:
/data/storage_c/repositorios_zypp/ .... /home/ ... /home1/ ... /home_aux/ ... /data/storage_b/ ... /var/spool/news/ ...
I tried with /data, and did not work:
linux-9vao:~ # mount -v /data/data_nfs_tc/ mount.nfs4: timeout set for Sun Mar 11 14:15:33 2018 mount.nfs4: trying text-based options 'vers=4.2,addr=192.168.1.14,clientaddr=192.168.1.128' mount.nfs4: mount(2): Device or resource busy linux-9vao:~ # mount -v /data/data_nfs_tc/ mount.nfs4: timeout set for Sun Mar 11 14:16:54 2018 mount.nfs4: trying text-based options 'vers=4.2,addr=192.168.1.14,clientaddr=192.168.1.128' mount.nfs4: mount(2): Device or resource busy linux-9vao:~ #
I later copied an entry from fstab from another install, and it worked instantly.
Why doesn't YaST work, is it a bug, or work in progress, or a firewall problem somewhere, or what?
As Andrei replied. That's how NFSv4 works. You should see exactly the same behavior with any version of yast2-nfs-client talking to an NFSv4 server. No matter whether you are using Leap 42.X, Leap 15 or openSUSE 13.X. NFSv4 will only return one level at a time and yast2-nfs-client has never had the ability to browse down the reported tree.
Well, it is the first time I tried "NFSv4share", but without that the list of exported directories should show. I have seen it other times. For instance, on the same laptop running 42.3 now: minas-tirith:~ # nfs-ls -D nfs://192.168.1.14 Failed to get exports for server 192.168.1.14. minas-tirith:~ # and takes two minutes to say so. minas-tirith:~ # nfs-ls -D nfs://isengard.valinor Failed to get exports for server isengard.valinor. minas-tirith:~ # However, doing it locally on the server the answer is instant-fast: cer@Telcontar:~> nfs-ls -D nfs://127.0.0.1 nfs://127.0.0.1/data/storage_c/repositorios_zypp nfs://127.0.0.1/home nfs://127.0.0.1/home1 nfs://127.0.0.1/home_aux nfs://127.0.0.1/data/storage_b nfs://127.0.0.1/var/spool/news cer@Telcontar:~> So this hints at a firewall issue. I see the server drops connections to port DPT=20048 as I do it. Indeed, I stop the SuSEfirewall2 on the server, and it works instantly on the client: minas-tirith:~ # time nfs-ls -D nfs://telcontar.valinor nfs://telcontar.valinor/data/storage_c/repositorios_zypp nfs://telcontar.valinor/home nfs://telcontar.valinor/home1 nfs://telcontar.valinor/home_aux nfs://telcontar.valinor/data/storage_b nfs://telcontar.valinor/var/spool/news real 0m0.023s user 0m0.000s sys 0m0.004s minas-tirith:~ # Solving this is not an issue for this list, but if you happen to know why it happens, I'd appreciate it ;.)
That being said, there are other things regarding NFS and versioning that has changed between 42.X and 15, so copying entries may still have an slightly different behavior. We plan to adjust yast2-nfs-client to make those changes obvious enough. When done, it will be explained in one of our usual blog post. ;-)
Cheers.
Ok! :-) - -- Cheers, Carlos E. R. (from openSUSE 42.3 x86_64 "Malachite" at Telcontar) -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iEYEARECAAYFAlqm8NcACgkQtTMYHG2NR9XQ1QCfa2V4Mc/ngmuPrHgRUusoC6Q2 3J0An2EAjJgGG2UVo0L6einNE+htl1XL =VyrY -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
participants (4)
-
Ancor Gonzalez Sosa -
Andrei Borzenkov -
Carlos E. R. -
Per Jessen