Re: autofs NFS mounts and Mandriva 2006.0

In the original post I wrote:
> From my server I export /home to my clients. On old "good"
> clients when I list /net/server I get /home. On the "bad"
> (Mandriva 2006.0 release ) clients when I list /net/server I
> get the contents of /home and not /home itself.

Since this is looking especially networking related, I'm adding
comp.os.linux.networking to the newsgroups.

kermit <cku192@yahoo.com> wrote:
> could you please show output of "showmount -e server" where
> server is your NFS server from both good and bad clients?

On a good client 'showmount -e server' produces:

Export list for server:
/home bad.mydom.com,good.mydom.com,server.mydom.com

On the bad client 'showmount -e server' produces:

Export list for server:
/home bad.mydom.com,good.mydom.com,server.mydom.com

Those look identical to me.


> Could you please also show "rpcinfo -p server"?

On a good client 'rpcinfo -p server' produces:

program vers proto port
100000 2 tcp 111 portmapper
100000 2 udp 111 portmapper
100024 1 udp 1024 status
100024 1 tcp 1024 status
391002 2 tcp 1025 sgi_fam
100011 1 udp 798 rquotad
100011 2 udp 798 rquotad
100011 1 tcp 801 rquotad
100011 2 tcp 801 rquotad
100003 2 udp 2049 nfs
100003 3 udp 2049 nfs
100021 1 udp 1026 nlockmgr
100021 3 udp 1026 nlockmgr
100021 4 udp 1026 nlockmgr
100005 1 udp 4002 mountd
100005 1 tcp 4002 mountd
100005 2 udp 4002 mountd
100005 2 tcp 4002 mountd
100005 3 udp 4002 mountd
100005 3 tcp 4002 mountd


On the bad client 'rpcinfo -p server' produces:

program vers proto port
100000 2 tcp 111 portmapper
100000 2 udp 111 portmapper
100024 1 udp 1024 status
100024 1 tcp 1024 status
391002 2 tcp 1025 sgi_fam
100011 1 udp 798 rquotad
100011 2 udp 798 rquotad
100011 1 tcp 801 rquotad
100011 2 tcp 801 rquotad
100003 2 udp 2049 nfs
100003 3 udp 2049 nfs
100021 1 udp 1026 nlockmgr
100021 3 udp 1026 nlockmgr
100021 4 udp 1026 nlockmgr
100005 1 udp 4002 mountd
100005 1 tcp 4002 mountd
100005 2 udp 4002 mountd
100005 2 tcp 4002 mountd
100005 3 udp 4002 mountd
100005 3 tcp 4002 mountd

Those look identical to me.


> Any chance that your server supports both NFS v3 and v4 and
> new mdk is getting v4 information? It presents mount points
> differently from v3, so it _may_ have described effect.

The server is running nfs-utils-1.0.1. The good client is
running nfs-utils-1.0.6. There is no mention of NFS v4 in
the documentation for 1.0.1 nor 1.0.6, although there is a
bit of discussion of v2 vs. v3. The bad client is running
nfs-utils-1.0.7. On the bad client 'rpm -qi nfs-utils' reports,
in part:

You can also rebuild nfs-utils with NFS protocol v4 and
tcp_wrappers support. Currently both these options are disabled
per default.

I think that says that the bad client is not running v4. Your
point here brings up the question as to whether there's a v2 vs.
v3 issue. I'm not sure how to tell which protocol version is
being run by the server or client. I would think (danger!) that
a client/server that was either all v2 or all v3 should behave
nicely. Would you have any other hints or debugging ideas?
Anyone?

Thanks....

--
PLEASE post a SUMMARY of the answer(s) to your question(s)!
Show Windows & Gates to the exit door.
Unless otherwise noted, the statements herein reflect my personal
opinions and not those of any organization with which I may be affiliated.

Kevin the Drummer <nobody@tek.com> wrote:
> In the original post I wrote:
> > From my server I export /home to my clients. On old "good"
> > clients when I list /net/server I get /home. On the "bad"
> > (Mandriva 2006.0 release ) clients when I list /net/server I
> > get the contents of /home and not /home itself.

Originally I thought this was a problem with autofs. I've bypassed
autofs completely, using fstab to define the mount, and the symptom is
still there. FWIW, my fstab entry is:

server:/home /mnt/server nfs \
nfsvers=2,rsize=8192,wsize=8192,hard,intr,nodev,no suid 0 0

Any ideas why this mounts differently now (with my new
distribution, Mandriva 2006.0) than it used to mount (with all
prior Mandrake distributions)?

Thanks....

--
PLEASE post a SUMMARY of the answer(s) to your question(s)!
Show Windows & Gates to the exit door.
Unless otherwise noted, the statements herein reflect my personal
opinions and not those of any organization with which I may be affiliated.

Kevin the Drummer wrote:

> In the original post I wrote:
>> From my server I export /home to my clients. On old "good"
>> clients when I list /net/server I get /home. On the "bad"
>> (Mandriva 2006.0 release ) clients when I list /net/server I
>> get the contents of /home and not /home itself.
>


well I just can assume that either kernel or user part of autofs has
changed; I would guess at user (automount) part.

Currently as far as I can tell for /net to work as expected you need every
intermediate directory starting from toplevel exported. So for your case as
a workaround export / (read-only suffice). Consider (ignore bind mount, it
is a shortcut taken by automunter for local exports):

{pts/0}% ls /net/cooker
bin/ etc/ lib/ media/ nsr@ root/ swap/ test/ usr/
boot/ home/ lvm/ mnt/ opt/ sbin/ sys/ tmp/ var/
dev/ initrd/ man/ net/ proc/ share/ T/ udev/
{pts/0}% mount
/dev/hda2 on / type reiserfs (rw)
none on /proc type proc (rw)
none on /proc/bus/usb type usbfs (rw)
none on /sys type sysfs (rw)
none on /tmp type tmpfs (rw)
nfsd on /proc/fs/nfsd type nfsd (rw)
automount(pid16567) on /net type autofs
(rw,fd=5,pgrp=16567,minproto=2,maxproto=4)
/ on /net/cooker type none (rw,bind)
/home on /net/cooker/home type none (rw,bind)
{pts/0}% showmount -e
Export list for cooker.home.net:
/ (everyone)
/home 10.0.0.0/255.0.0.0

I advice to make a bug report on Mandriva bugzilla (post bug number here so
I could follow it). It looks like clear bug to me, at least Solaris does
work differently here.


=arvi=

Kevin the Drummer wrote:

> Kevin the Drummer <nobody@tek.com> wrote:
>> In the original post I wrote:
>> > From my server I export /home to my clients. On old "good"
>> > clients when I list /net/server I get /home. On the "bad"
>> > (Mandriva 2006.0 release ) clients when I list /net/server I
>> > get the contents of /home and not /home itself.
>
> Originally I thought this was a problem with autofs. I've bypassed
> autofs completely, using fstab to define the mount, and the symptom is
> still there. FWIW, my fstab entry is:
>
> server:/home /mnt/server nfs \
> nfsvers=2,rsize=8192,wsize=8192,hard,intr,nodev,no suid 0 0
>

What exactly do you expect? You told it to mount server:/home on /mnt/server
so when you list /mnt/server you get contents of server:/home.

> Any ideas why this mounts differently now (with my new
> distribution, Mandriva 2006.0) than it used to mount (with all
> prior Mandrake distributions)?
>

Do you mean that you EVER got to see /mnt/server/home with above mount line?
This must be the most broken thing ever existed.

Anyway to original problem - I looked as autofs code and I believe I know
where the problem is. There is a bug that makes automount interpret output
with single and multiple mount points differently. It is easy to see if you
export any other directory:

{pts/0}% pwd
/net/cooker
{pts/0}% ls
home/ opt/

So if you are truly interested in fixing it, make a bug report and I send a
patch for it so it can be tested. Until that workaround is to have more
than one directory exported (second can be dummy with no access).

=arvi=

kermit <cku192@yahoo.com> wrote:
> > server:/home /mnt/server nfs \
> > nfsvers=2,rsize=8192,wsize=8192,hard,intr,nodev,no suid 0 0
>
> What exactly do you expect? You told it to mount server:/home on /mnt/server
> so when you list /mnt/server you get contents of server:/home.
[snip]
> Do you mean that you EVER got to see /mnt/server/home with above mount line?
> This must be the most broken thing ever existed.

I haven't tried mounting outside of autofs in a long time. So, I wasn't
sure what to expect. I just now tried the older client, the one with
autofs working the way I expect, and it has the same NFS behavior
outside of autofs. I concur that NFS itself it working just fine.
[posting to this article to comp.os.linux.networking to clear up any
confusion I might have caused. Followups set.]

> Anyway to original problem - I looked as autofs code and I
> believe I know where the problem is. There is a bug that makes
> automount interpret output with single and multiple mount
> points differently. It is easy to see if you export any other
> directory:
>
> {pts/0}% pwd
> /net/cooker
> {pts/0}% ls
> home/ opt/
>
> So if you are truly interested in fixing it, make a bug report
> and I'd send a patch for it so it can be tested. Until that
> workaround is to have more than one directory exported (second
> can be dummy with no access).

I will explore what you found, and I'll work on a patch.

Thanks for your help....

--
PLEASE post a SUMMARY of the answer(s) to your question(s)!
Show Windows & Gates to the exit door.
Unless otherwise noted, the statements herein reflect my personal
opinions and not those of any organization with which I may be affiliated.