Forums before death by AOL, social media and spammers... "We can't have nice things"
|    alt.os.linux.suse    |    Suse is actually not that bad    |    138,051 messages    |
[   << oldest   |   < older   |   list   |   newer >   |   newest >>   ]
|    Message 136,453 of 138,051    |
|    Carlos E.R. to grinch    |
|    Re: nfs problem with tumbleweed    |
|    10 Dec 17 21:23:18    |
      From: robin_listas@es.invalid              On 2017-12-10 18:30, grinch wrote:       > On 09/12/17 20:35, Carlos E.R. wrote:       >> mount -v /mnt       >       > mount.nfs: timeout set for Sun Dec 10 17:13:02 2017       > mount.nfs: trying text-based options 'vers=4.2,addr=192.168.1.       ,clientaddr=192.168.1.30'       > mount.nfs: mount(2): Protocol not supported       > mount.nfs: trying text-based options 'vers=4.1,addr=192.168.1.       ,clientaddr=192.168.1.30'       > mount.nfs: mount(2): Input/output error       > mount.nfs: mount system call failed       >       > Am I correct in thinking that vers-4.2 and 4.1 refers to the nfs version       > because my nas is version 3 only and is so old it wont upgrade              Yes, it refers to the nfs protocol version, I understand.                     Try in fstab:              192.168.1.6:/volume1/homes /mnt nfs3 defaults 0 0              I don't remember if "nfs3" is valid syntax, though. I do know that       "nfs4" is valid because I use it. And I remember that I tried once       "nfs3" syntax, but not what happened ;-)              --       Cheers, Carlos.              --- SoupGate-Win32 v1.05        * Origin: you cannot sedate... all the things you hate (1:229/2)    |
[   << oldest   |   < older   |   list   |   newer >   |   newest >>   ]
(c) 1994, bbs@darkrealms.ca