Very Computer

> 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?

>> 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.

>>> 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)

>>>> 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.

>>>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)

>>   # 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)