Package: nfs-kernel-server
Version: 1:1.0.7-1
Severity: important

I have a debian sid which exports some directories via nfs to other 
hosts. There's a line that causes nfs mount to work

/backup 192.168.0.8/255.255.255.255(no_root_squash,rw,async)
/archive 192.168.0.0/255.255.255.255(no_root_squash,rw,async)

The line is the first one and 
that line has worked for months. some days ago my sarge client 
with ip 192.168.0.8 stopped to mount successfully *every* nfs share 
from the sid server.

>From the client an

rpcinfo -u nfsserver nfs

ended in a TIMEOUT. Other clients in 192.168.0.0 network could 
do a rpcinfo for nfs service and mount their share.
After a long investigation it turned out that if I specify the 
line as follows

/backup 192.168.0.8(no_root_squash,rw,async)

without netmask, it works well and the client whith ip 192.168.0.8 
can do rpcinfo for nfs service and mount all the shares.

Since the client with 192.168.0.8 is a Debian sarge, I tried to reproduce 
the bug with a sid client. The bug is still reproducibile, so I 
thought is related to the server part.


-- System Information:
Debian Release: 3.1
  APT prefers unstable
  APT policy: (500, 'unstable'), (1, 'experimental')
Architecture: i386 (i686)
Kernel: Linux 2.6.9-1-686
Locale: LANG=en_US.ISO-8859-15, LC_CTYPE=en_US.ISO-8859-15 (charmap=ISO-8859-15)

Versions of packages nfs-kernel-server depends on:
ii  debconf                     1.4.42       Debian configuration management sy
ii  libc6                       2.3.2.ds1-20 GNU C Library: Shared libraries an
ii  libcomerr2                  1.36rc4-1    common error description library
ii  libkrb53                    1.3.6-1      MIT Kerberos runtime libraries
ii  libnfsidmap1                0.8-1        An nfs idmapping library
ii  libwrap0                    7.6.dbs-6    Wietse Venema's TCP wrappers libra
ii  nfs-common                  1:1.0.7-1    NFS support files common to client
ii  sysvinit                    2.86.ds1-1   System-V like init

-- no debconf information


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Reply via email to