I'm not sure when this started happening, but it worked the last time I played with it two months ago. This is using the xen kernel. nfs v3 is unaffected, as are clients not running SLES11.
|
Code:
|
app-03:~ # mount.nfs4 (nfs server name):/share /mnt/share -v
mount.nfs4: timeout set for Mon Sep 7 15:34:12 2009
mount.nfs4: text-based options: 'clientaddr=10.x.x.x,addr=10.y.y.y'
mount.nfs4: mount(2): Invalid argument
mount.nfs4: an incorrect mount option was specified |
On the server, I see that idmapd receives some information from the server, but don't see that a client ever tries to connect. Attempting different security settings, or attempting to override the clientaddr or addr settings fails as well.
I'd submit a bug report, but the Novell Bug Report page throws an error. :-P