Additional nfs mounts on diskless machine lock nfs server

Additional nfs mounts on diskless machine lock nfs server

Post by Ray » Wed, 20 Nov 2002 06:19:18



I have several diskless workstations that mostly work just fine (I have one
other issue that I'll get to later) except that if I try to mount an
additional directory from the server the nfs server stops responding to all
clients.  For example I have:

1.  Client boots and mounts it's root directory from server://tftpboot/client1
and continues to boot and work fine.

2.  Client now mounts server://data in /data and the nfs server stops
responding.

I'm running Debian Woody on the server with kernel 2.4.19 and the user space
nfs daemon.  The clients are a mixture of Debian Potato and Woody with a
variety of 2.2 and 2.4. kernels.

Any ideas?

--
Ray

 
 
 

Additional nfs mounts on diskless machine lock nfs server

Post by Paul Lutu » Wed, 20 Nov 2002 07:14:03



> I have several diskless workstations that mostly work just fine (I have one
> other issue that I'll get to later) except that if I try to mount an
> additional directory from the server the nfs server stops responding to all
> clients.  For example I have:

> 1.  Client boots and mounts it's root directory from server://tftpboot/client1
> and continues to boot and work fine.

> 2.  Client now mounts server://data in /data and the nfs server stops
> responding.

> I'm running Debian Woody on the server with kernel 2.4.19 and the user space
> nfs daemon.  The clients are a mixture of Debian Potato and Woody with a
> variety of 2.2 and 2.4. kernels.

> Any ideas?

Show us how these shares are offered -- list the server's /etc/exports
file. And show us specifically how you mount the additional share at the
client.

And what is with the double slashes? That is not normal NFS syntax.

Right: "mount machine-name:/share-name /local/mount/point"

Wrong: "mount machine-name://share-name /local/mount/point"

--
Paul Lutus
www.arachnoid.com

 
 
 

Additional nfs mounts on diskless machine lock nfs server

Post by Ray » Wed, 20 Nov 2002 12:27:08




>> I have several diskless workstations that mostly work just fine (I have one
>> other issue that I'll get to later) except that if I try to mount an
>> additional directory from the server the nfs server stops responding to all
>> clients.  For example I have:

>> 1.  Client boots and mounts it's root directory from server://tftpboot/client1
>> and continues to boot and work fine.

>> 2.  Client now mounts server://data in /data and the nfs server stops
>> responding.

>> I'm running Debian Woody on the server with kernel 2.4.19 and the user space
>> nfs daemon.  The clients are a mixture of Debian Potato and Woody with a
>> variety of 2.2 and 2.4. kernels.

>> Any ideas?

> Show us how these shares are offered -- list the server's /etc/exports
> file. And show us specifically how you mount the additional share at the
> client.

Here is the /etc/exports file on the server (homer):

  # Give Bart access to home & sources
  /home bart(rw,no_root_squash,map_daemon)
  /usr/src bart(rw,no_root_squash,map_daemon)
  #nfs boot machines
  /tftpboot 192.168.0.0/255.255.255.0(rw,no_root_squash)
  # Other data
  # /data  192.168.0.0/255.255.0.0(rw,no_root_squash,map_daemon)
  /  192.168.0.0/255.255.0.0(rw,no_root_squash,map_daemon)

My fstab file from one of the diskless boxes:

  192.168.0.1:/tftpboot/192.168.0.31      /       nfs
  proc            /proc         proc   defaults                   0      0

And mounting an additonal directory like this:

  mount homer:/data /data

Imediately the nfs server stops responding to any of the machines here that
have mounts and only recovers when I restart nfsd.  Mounting that same
directory from any of the normal (not diskless) machines works fine and the
diskless machines can mount directories from other machines with no
problems.

Quote:

> And what is with the double slashes? That is not normal NFS syntax.

> Right: "mount machine-name:/share-name /local/mount/point"

> Wrong: "mount machine-name://share-name /local/mount/point"

Yes, I know, guess I've just been to too many web pages today:)

--
Ray

 
 
 

Additional nfs mounts on diskless machine lock nfs server

Post by Paul Lutu » Wed, 20 Nov 2002 14:28:35






>>> I have several diskless workstations that mostly work just fine (I
>>> have one other issue that I'll get to later) except that if I try to
>>> mount an additional directory from the server the nfs server stops
>>> responding to all clients.  For example I have:

>>> 1.  Client boots and mounts it's root directory from
>>> server://tftpboot/client1 and continues to boot and work fine.

>>> 2.  Client now mounts server://data in /data and the nfs server stops
>>> responding.

>>> I'm running Debian Woody on the server with kernel 2.4.19 and the user
>>> space nfs daemon.  The clients are a mixture of Debian Potato and
>>> Woody with a variety of 2.2 and 2.4. kernels.

>>> Any ideas?

>> Show us how these shares are offered -- list the server's /etc/exports
>> file. And show us specifically how you mount the additional share at
>> the client.

> Here is the /etc/exports file on the server (homer):

>   # Give Bart access to home & sources
>   /home bart(rw,no_root_squash,map_daemon) /usr/src
>   bart(rw,no_root_squash,map_daemon) #nfs boot machines
>   /tftpboot 192.168.0.0/255.255.255.0(rw,no_root_squash)
>   # Other data
>   # /data  192.168.0.0/255.255.0.0(rw,no_root_squash,map_daemon)
>   / 192.168.0.0/255.255.0.0(rw,no_root_squash,map_daemon)

1. Have you tried not using the map_daemon? Make the information on "bart"
the same on both machines instead? I have never used map_daemon, and it
might be the source of the problem, especially because you've allowed two
accesses to the same resources with two different access methods.

2. The "/" share is likely to be a problem -- most NFS versions will not
allow this access to coexist with any other access to the same resource.

To say it another way, you can have the "/" share, or you can have a
collection of more specific shares, but you cannot have both.

--
Paul Lutus
www.arachnoid.com

 
 
 

Additional nfs mounts on diskless machine lock nfs server

Post by Ray » Thu, 21 Nov 2002 05:43:44







>>>> I have several diskless workstations that mostly work just fine (I
>>>> have one other issue that I'll get to later) except that if I try to
>>>> mount an additional directory from the server the nfs server stops
>>>> responding to all clients.  For example I have:

>>>> 1.  Client boots and mounts it's root directory from
>>>> server://tftpboot/client1 and continues to boot and work fine.

>>>> 2.  Client now mounts server://data in /data and the nfs server stops
>>>> responding.

>>>> I'm running Debian Woody on the server with kernel 2.4.19 and the user
>>>> space nfs daemon.  The clients are a mixture of Debian Potato and
>>>> Woody with a variety of 2.2 and 2.4. kernels.

>>>> Any ideas?

>>> Show us how these shares are offered -- list the server's /etc/exports
>>> file. And show us specifically how you mount the additional share at
>>> the client.

>> Here is the /etc/exports file on the server (homer):

>>   # Give Bart access to home & sources
>>   /home bart(rw,no_root_squash,map_daemon) /usr/src
>>   bart(rw,no_root_squash,map_daemon) #nfs boot machines
>>   /tftpboot 192.168.0.0/255.255.255.0(rw,no_root_squash)
>>   # Other data
>>   # /data  192.168.0.0/255.255.0.0(rw,no_root_squash,map_daemon)
>>   / 192.168.0.0/255.255.0.0(rw,no_root_squash,map_daemon)

> 1. Have you tried not using the map_daemon? Make the information on "bart"
> the same on both machines instead? I have never used map_daemon, and it
> might be the source of the problem, especially because you've allowed two
> accesses to the same resources with two different access methods.

This was the problem.  Apparently since the diskless machines were mounting
their root (/tftpboot/clientX) without map_daemon and mounting /data on top
of that with map_daemon it was causing problems.  Other machines here have
no trouble mixing mapping modes but these diskless machines are the only
ones where I'm actually mounting 1 share on top of another.

Thanks for the tip.

--
Ray

 
 
 

Additional nfs mounts on diskless machine lock nfs server

Post by Greg DeFreita » Thu, 21 Nov 2002 05:06:41





>>>I have several diskless workstations that mostly work just fine (I have one
>>>other issue that I'll get to later) except that if I try to mount an
>>>additional directory from the server the nfs server stops responding to all
>>>clients.  For example I have:

>>>1.  Client boots and mounts it's root directory from server://tftpboot/client1
>>>and continues to boot and work fine.

>>>2.  Client now mounts server://data in /data and the nfs server stops
>>>responding.

>>>I'm running Debian Woody on the server with kernel 2.4.19 and the user space
>>>nfs daemon.  The clients are a mixture of Debian Potato and Woody with a
>>>variety of 2.2 and 2.4. kernels.

>>>Any ideas?

>>Show us how these shares are offered -- list the server's /etc/exports
>>file. And show us specifically how you mount the additional share at the
>>client.

> Here is the /etc/exports file on the server (homer):

>   # Give Bart access to home & sources
>   /home bart(rw,no_root_squash,map_daemon)
>   /usr/src bart(rw,no_root_squash,map_daemon)
>   #nfs boot machines
>   /tftpboot 192.168.0.0/255.255.255.0(rw,no_root_squash)
>   # Other data
>   # /data  192.168.0.0/255.255.0.0(rw,no_root_squash,map_daemon)

^^^^^^^^^ = NOT "shared" (# = commented_out)

BTW: Why do the netmasks differ, /16 vs. /24 ?
:-)

- Show quoted text -

Quote:>   /  192.168.0.0/255.255.0.0(rw,no_root_squash,map_daemon)

> My fstab file from one of the diskless boxes:

>   192.168.0.1:/tftpboot/192.168.0.31      /       nfs
>   proc            /proc         proc   defaults                   0      0

> And mounting an additonal directory like this:

>   mount homer:/data /data

> Imediately the nfs server stops responding to any of the machines here that
> have mounts and only recovers when I restart nfsd.  Mounting that same
> directory from any of the normal (not diskless) machines works fine and the
> diskless machines can mount directories from other machines with no
> problems.

>>And what is with the double slashes? That is not normal NFS syntax.

>>Right: "mount machine-name:/share-name /local/mount/point"

>>Wrong: "mount machine-name://share-name /local/mount/point"

> Yes, I know, guess I've just been to too many web pages today:)

 
 
 

Additional nfs mounts on diskless machine lock nfs server

Post by Ray » Fri, 22 Nov 2002 01:33:04




>>   # Give Bart access to home & sources
>>   /home bart(rw,no_root_squash,map_daemon)
>>   /usr/src bart(rw,no_root_squash,map_daemon)
>>   #nfs boot machines
>>   /tftpboot 192.168.0.0/255.255.255.0(rw,no_root_squash)
>>   # Other data
>>   # /data  192.168.0.0/255.255.0.0(rw,no_root_squash,map_daemon)
> ^^^^^^^^^ = NOT "shared" (# = commented_out)

Right, I commented it out and replaced it with the one (/) below for testing
purposes. I don't normally give access to the whole filesystem.

Quote:> BTW: Why do the netmasks differ, /16 vs. /24 ?
>:-)

I have a small network of wireless routers out on 192.168.3.x and their
(wired) clients have 192.168.5.0/24, 192.168.6.0/24 etc.  I'm not running
any diskless boxes on the wireless net so I don't give them access to
/tftpboot.

Quote:

>>   /  192.168.0.0/255.255.0.0(rw,no_root_squash,map_daemon)

----^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
This was for testing only.  I was curious if it mattered what dir I was
mounting.

--
Ray