| 1 |
On Monday 15 February 2010 21:23:54 walt wrote: |
| 2 |
> Anyone else having problems mounting nfs shares with nfs-utils-1.2.1? |
| 3 |
> |
| 4 |
> 'mount.nfs' complains I'm passing it a bad nfs option no matter what |
| 5 |
> options I give it, including no options. |
| 6 |
> |
| 7 |
> Strace shows that nfs.mount is passing a weird-looking IP address |
| 8 |
> string to the 'mount' system call (man 2 mount), e.g.: |
| 9 |
> |
| 10 |
> mount("k2:/media/d", "/mnt/nfs", "nfs", 0, |
| 11 |
> "addr=192.168.0.100,vers=4,client"...) = -1 EINVAL |
| 12 |
|
| 13 |
|
| 14 |
At first glance I suspect you have nfs v4 support and the server does not like |
| 15 |
it. |
| 16 |
|
| 17 |
The USE flag changed at 1.1.6-r1 from nonfsv4 to nfsv4 so if you did not |
| 18 |
change USE you will get the exact opposite support between the earliest and |
| 19 |
most recent version in portage. |
| 20 |
|
| 21 |
<pet hate> |
| 22 |
Don't you just hate negative USE flags on the lines of no* ? You have to |
| 23 |
switch then on to not get something. Far better to have a positive flag and |
| 24 |
enable it by default in the profile. Not to mention the confusion that |
| 25 |
changing it later causes, witness this case here. |
| 26 |
|
| 27 |
|
| 28 |
|
| 29 |
|
| 30 |
|
| 31 |
> ^^^^^^^^^^^^^^ |
| 32 |
> |
| 33 |
> When I revert back to nfs-utils-1.1.4-r1 the IP address string is |
| 34 |
> back to normal and the mount works correctly, e.g.: |
| 35 |
> |
| 36 |
> mount("k2:/media/d", "/mnt/nfs", "nfs", 0, "addr=192.168.0.100") = 0 |
| 37 |
> |
| 38 |
> Something is tacking on those extra chars after the IP address, but |
| 39 |
> I'm not sure yet where that string is actually generated. |
| 40 |
> |
| 41 |
> Any ideas? |
| 42 |
|
| 43 |
-- |
| 44 |
alan dot mckinnon at gmail dot com |
Archives