[opensuse] Yast nfs4 error
Hi Yast NFS Client gives me the option to choose a share and select nfsv4. If I select the share I want from the drop down list it will not mount the share. I think the dialogue is wrong. e.g. if /home is exported and I select /home from the drop down list it will not mount. For nfs4 it should change /home to / As I see it, yast is trying to do this: mount -t nfs4 myserver:/home /somewhere but it should be doing this mount -t nfs4 myserver:/ /somewhere Is this a bug in Yast? I can mount it manually, but what should I put in fstab to make it mount? Thanks L x -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
lynn wrote:
Hi Yast NFS Client gives me the option to choose a share and select nfsv4. If I select the share I want from the drop down list it will not mount the share. I think the dialogue is wrong. e.g. if /home is exported and I select /home from the drop down list it will not mount. For nfs4 it should change /home to /
How would you be able to distinguish between an exported / and /home ? -- Per Jessen, Zürich (6.4°C) -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 01/03/2012 05:08 PM, Per Jessen wrote:
lynn wrote:
Hi Yast NFS Client gives me the option to choose a share and select nfsv4. If I select the share I want from the drop down list it will not mount the share. I think the dialogue is wrong. e.g. if /home is exported and I select /home from the drop down list it will not mount. For nfs4 it should change /home to / How would you be able to distinguish between an exported / and /home ?
After the share is mounted, look at /somewhere on the client. It should look like /home on the server. nfsv3 mount -t nfs myserver:/home /somewhere nfsv4 mount -t nfs4 myserver:/ /somewhere L x -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
lynn wrote:
On 01/03/2012 05:08 PM, Per Jessen wrote:
lynn wrote:
Hi Yast NFS Client gives me the option to choose a share and select nfsv4. If I select the share I want from the drop down list it will not mount the share. I think the dialogue is wrong. e.g. if /home is exported and I select /home from the drop down list it will not mount. For nfs4 it should change /home to / How would you be able to distinguish between an exported / and /home ?
After the share is mounted, look at /somewhere on the client. It should look like /home on the server.
nfsv3 mount -t nfs myserver:/home /somewhere
nfsv4 mount -t nfs4 myserver:/ /somewhere L x
I can't really follow you - in your nfsv3 example, presumably you have exported /home on the nfs server, but in your nfsv4 example, I guess you have exported / ? (what they're mounted on on the client is not important). -- Per Jessen, Zürich (7.0°C) -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 01/03/2012 06:22 PM, Per Jessen wrote:
lynn wrote:
On 01/03/2012 05:08 PM, Per Jessen wrote:
lynn wrote:
Hi Yast NFS Client gives me the option to choose a share and select nfsv4. If I select the share I want from the drop down list it will not mount the share. I think the dialogue is wrong. e.g. if /home is exported and I select /home from the drop down list it will not mount. For nfs4 it should change /home to / How would you be able to distinguish between an exported / and /home ?
After the share is mounted, look at /somewhere on the client. It should look like /home on the server.
nfsv3 mount -t nfs myserver:/home /somewhere
nfsv4 mount -t nfs4 myserver:/ /somewhere L x I can't really follow you - in your nfsv3 example, presumably you have exported /home on the nfs server, but in your nfsv4 example, I guess you have exported / ? (what they're mounted on on the client is not important).
In both examples, /home has been exported. L x -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 01/04/2012 01:45 AM, lynn wrote:
On 01/03/2012 06:22 PM, Per Jessen wrote:
lynn wrote:
On 01/03/2012 05:08 PM, Per Jessen wrote:
lynn wrote:
Hi Yast NFS Client gives me the option to choose a share and select nfsv4. If I select the share I want from the drop down list it will not mount the share. I think the dialogue is wrong. e.g. if /home is exported and I select /home from the drop down list it will not mount. For nfs4 it should change /home to / How would you be able to distinguish between an exported / and /home ?
After the share is mounted, look at /somewhere on the client. It should look like /home on the server.
nfsv3 mount -t nfs myserver:/home /somewhere
nfsv4 mount -t nfs4 myserver:/ /somewhere L x I can't really follow you - in your nfsv3 example, presumably you have exported /home on the nfs server, but in your nfsv4 example, I guess you have exported / ? (what they're mounted on on the client is not important).
In both examples, /home has been exported. L x
What is the output of "exportfs" on the server? nfs4 is very different from nfs3 in how exports are defined and handled. You can reference http://www.crazysquirrel.com/computing/debian/servers/setting-up-nfs4.jspx to see how things should look under the hood. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On Tuesday 03 January 2012 17:08:36 Per Jessen wrote:
lynn wrote:
Hi Yast NFS Client gives me the option to choose a share and select nfsv4. If I select the share I want from the drop down list it will not mount the share. I think the dialogue is wrong. e.g. if /home is exported and I select /home from the drop down list it will not mount. For nfs4 it should change /home to /
How would you be able to distinguish between an exported / and /home ?
You can't, in nfs4 you define an export with fsid=0 and that is all you can ever export. Everything else you want to export from that server has to be bind-mounted into that export. The nfsv3 concept of different exports doesn't exist in nfsv4. You have one directory exported with fsid=0 and that is mounted as server:/ from the client - this doesn't mean the root of the server file system, it means the root of the nfsv4 export Anders -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On Tuesday 03 January 2012 16:49:29 lynn wrote:
Hi Yast NFS Client gives me the option to choose a share and select nfsv4. If I select the share I want from the drop down list it will not mount the share. I think the dialogue is wrong. e.g. if /home is exported and I select /home from the drop down list it will not mount. For nfs4 it should change /home to /
As I see it, yast is trying to do this:
mount -t nfs4 myserver:/home /somewhere
but it should be doing this
mount -t nfs4 myserver:/ /somewhere
Is this a bug in Yast?
Yes, it looks like a bug.
I can mount it manually, but what should I put in fstab to make it mount?
myserver:/ /somewhere nfs4 defaults 0 0 for example Anders -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
Anders Johansson wrote:
On Tuesday 03 January 2012 17:08:36 Per Jessen wrote:
lynn wrote:
Hi Yast NFS Client gives me the option to choose a share and select nfsv4. If I select the share I want from the drop down list it will not mount the share. I think the dialogue is wrong. e.g. if /home is exported and I select /home from the drop down list it will not mount. For nfs4 it should change /home to /
How would you be able to distinguish between an exported / and /home ?
You can't, in nfs4 you define an export with fsid=0 and that is all you can ever export. Everything else you want to export from that server has to be bind-mounted into that export.
The nfsv3 concept of different exports doesn't exist in nfsv4. You have one directory exported with fsid=0 and that is mounted as server:/ from the client - this doesn't mean the root of the server file system, it means the root of the nfsv4 export
Ah, thanks - I knew there was some kind of misunderstanding her. Mea culpa. -- Per Jessen, Zürich (7.7°C) -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On Tue, Jan 03, 2012 at 09:43:10PM +0100, Anders Johansson wrote:
On Tuesday 03 January 2012 16:49:29 lynn wrote:
Yast NFS Client gives me the option to choose a share and select nfsv4. If I select the share I want from the drop down list it will not mount the share. I think the dialogue is wrong. e.g. if /home is exported and I select /home from the drop down list it will not mount. For nfs4 it should change /home to /
As I see it, yast is trying to do this:
mount -t nfs4 myserver:/home /somewhere
but it should be doing this
mount -t nfs4 myserver:/ /somewhere
Is this a bug in Yast?
Yes, it looks like a bug.
No, a bug it only would be if there was a reference to a bug ID. ;) I'm sure Lynn only missed to quote it. Lars -- Lars Müller [ˈlaː(r)z ˈmʏlɐ] Samba Team SUSE Linux, Maxfeldstraße 5, 90409 Nürnberg, Germany
On 01/03/2012 09:43 PM, Anders Johansson wrote:
On Tuesday 03 January 2012 16:49:29 lynn wrote:
Hi Yast NFS Client gives me the option to choose a share and select nfsv4. If I select the share I want from the drop down list it will not mount the share. I think the dialogue is wrong. e.g. if /home is exported and I select /home from the drop down list it will not mount. For nfs4 it should change /home to /
As I see it, yast is trying to do this:
mount -t nfs4 myserver:/home /somewhere
but it should be doing this
mount -t nfs4 myserver:/ /somewhere
Is this a bug in Yast? Yes, it looks like a bug. Is it important enough to bugzilla it?
I can mount it manually, but what should I put in fstab to make it mount? myserver:/ /somewhere nfs4 defaults 0 0 Thanks.
Whilst we're here, does the Kerberos stuff look after itself? I've kerberized nfs but in particular, should the nfs4 domainname relate to the Kerberos realm? (It doesn't seem to matter what you call it so long as it's set the same on server and clients.) Also, is it intended that the Yast NFS Client set the Domain=domainname in /etc/idmapd.conf ? (Yast NFS Server does.) I'm not sure if this is another bug, but I had to change this manually on the client: [General] Verbosity=0 Pipefs-Directory=/var/lib/nfs/rpc_pipefs #Domain=domainname Domain=SOMETHING.ELSE [Mapping] Nobody-User=nobody Nobody-Group=nobody Sorry to be a pain. L x -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On Tuesday 03 January 2012 23:02:41 lynn wrote:
Is this a bug in Yast?
Yes, it looks like a bug.
Is it important enough to bugzilla it?
I think it's worth an entry, yes. YaST should be able to handle nfs4
Whilst we're here, does the Kerberos stuff look after itself? I've kerberized nfs but in particular, should the nfs4 domainname relate to the Kerberos realm? (It doesn't seem to matter what you call it so long as it's set the same on server and clients.)
kerberos is something I haven't played with at all, so I have to defer to others here. I *think* it should be the kerberos domain, but I'm not sure
Also, is it intended that the Yast NFS Client set the Domain=domainname in /etc/idmapd.conf ? (Yast NFS Server does.) I'm not sure if this is another bug, but I had to change this manually on the client:
[General] Verbosity=0 Pipefs-Directory=/var/lib/nfs/rpc_pipefs #Domain=domainname Domain=SOMETHING.ELSE [Mapping] Nobody-User=nobody Nobody-Group=nobody
It should match what is set on the server, otherwise idmapd won't know how to translate users. This is a problem even without kerberos, but I'm not sure where YaST should get the domain name from. It is definitely a problem, but I'm not sure if it's a bug or a feature request
Sorry to be a pain.
I'd say these are valid issues. Not a pain Anders -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 01/03/2012 10:22 PM, Per Jessen wrote:
Anders Johansson wrote:
On Tuesday 03 January 2012 17:08:36 Per Jessen wrote:
lynn wrote:
Hi Yast NFS Client gives me the option to choose a share and select nfsv4. If I select the share I want from the drop down list it will not mount the share. I think the dialogue is wrong. e.g. if /home is exported and I select /home from the drop down list it will not mount. For nfs4 it should change /home to / How would you be able to distinguish between an exported / and /home ? You can't, in nfs4 you define an export with fsid=0 and that is all you can ever export. Everything else you want to export from that server has to be bind-mounted into that export.
The nfsv3 concept of different exports doesn't exist in nfsv4. You have one directory exported with fsid=0 and that is mounted as server:/ from the client - this doesn't mean the root of the server file system, it means the root of the nfsv4 export
Good answer. K & R would have approved of it:) L x -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On Tuesday 03 January 2012 23:02:41 lynn wrote:
Is this a bug in Yast? Yes, it looks like a bug. Is it important enough to bugzilla it? I think it's worth an entry, yes. YaST should be able to handle nfs4
Whilst we're here, does the Kerberos stuff look after itself? I've kerberized nfs but in particular, should the nfs4 domainname relate to the Kerberos realm? (It doesn't seem to matter what you call it so long as it's set the same on server and clients.) kerberos is something I haven't played with at all, so I have to defer to others here. I *think* it should be the kerberos domain, but I'm not sure
Also, is it intended that the Yast NFS Client set the Domain=domainname in /etc/idmapd.conf ? (Yast NFS Server does.) I'm not sure if this is another bug, but I had to change this manually on the client:
[General] Verbosity=0 Pipefs-Directory=/var/lib/nfs/rpc_pipefs #Domain=domainname Domain=SOMETHING.ELSE [Mapping] Nobody-User=nobody Nobody-Group=nobody It should match what is set on the server, otherwise idmapd won't know how to translate users. This is a problem even without kerberos, but I'm not sure where YaST should get the domain name from. If you are using the Yast NFS Client then I think it should get the Kerberos realm from the NFSv4 settings option. Except in my case it didn't and uid:gid was mapped to nobody:nobody. It would be better if Yast took the domainname from what was already set on the server. Yast NFS Client should also check to see if there was an NFS server before it gave the error 'cannot mount nfs shares from fstab'. The Domain setting is only relevant if rpc.idmapd NFSv4 is used I think. I don't what you need for NFSv3. There could be other ways e.g. if you had joined a M$ AD domain or used Yast Kerberos Client to be able to authenticate. Just
On 01/03/2012 11:11 PM, Anders Johansson wrote: thinking out loud.
It is definitely a problem, but I'm not sure if it's a bug or a feature request
I suppose it's a request, that is also a suggestion, which would make Yast even greater than it already is;)
Sorry to be a pain. I'd say these are valid issues. Not a pain
Anders L x -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
Hi Yast NFS Client gives me the option to choose a share and select nfsv4. If I select the share I want from the drop down list it will not mount the share. I think the dialogue is wrong. e.g. if /home is exported and I select /home from the drop down list it will not mount. For nfs4 it should change /home to / How would you be able to distinguish between an exported / and /home ? You can't, in nfs4 you define an export with fsid=0 and that is all you can ever export. Everything else you want to export from that server has to be bind-mounted into that export.
The nfsv3 concept of different exports doesn't exist in nfsv4. You have one directory exported with fsid=0 and that is mounted as server:/ from the client - this doesn't mean the root of the server file system, it means the root of the nfsv4 export
Anders Hi You don't need to use the fsid=0 stuff if you don't want. In fact the nfs gurus suggest you don't. In this respect, nfs4 is the same as all
the other nfs's. Binding real directories to the pseudoroot seems to have been thrown away. So soon after being the best thing since sliced bread. See the last 2 lines of: http://wiki.linux-nfs.org/wiki/index.php/Nfsv4_configuration Saludos, L x -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
participants (5)
-
Anders Johansson -
Ed Greshko -
Lars Müller -
lynn -
Per Jessen