Package: nfs-kernel-server
Version: 1:1.0.10-6+etch.1
Severity: normal

I have these NFSv4 exports on my Debian Etch server

  /drbd/nfs_exports        192.168.4.0/24(ro,sync,no_subtree_check,fsid=0)
  /drbd/nfs_exports/usr    192.168.4.0/24(rw,sync,no_subtree_check) 

/drbd/nfs_exports/usr is on the same filesystem as /drbd/nfs_exports. On a 
client I mount /usr using this command:

mount -t nfs4 local.nfs:/usr /mnt

The problem is that /usr is now mounted read only. Apparently the NFS server is 
using only the first line of my exports, where it should be using the second 
line. Everything works fine when I change my exports to

  /drbd/nfs_exports        192.168.4.0/24(rw,sync,no_subtree_check,fsid=0)
  /drbd/nfs_exports/usr    192.168.4.0/24(rw,sync,no_subtree_check) 

(the first line now reads rw instead of ro)

But of course, this is no solution. The export with fsid=0 should never be 
exported as rw.

-- System Information:
Debian Release: 4.0
  APT prefers stable
  APT policy: (500, 'stable')
Architecture: amd64 (x86_64)
Shell:  /bin/sh linked to /bin/bash
Kernel: Linux 2.6.18-5-amd64
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)

Versions of packages nfs-kernel-server depends on:
ii  lib 2.3.6.ds1-13etch2                    GNU C Library: Shared libraries
ii  lib 1.39+1.40-WIP-2006.11.14+dfsg-2etch1 common error description library
ii  lib 0.10-4                               A mechanism-switch gssapi library
ii  lib 1.4.4-7etch4                         MIT Kerberos runtime libraries
ii  lib 0.18-0                               An nfs idmapping library
ii  lib 0.14-2etch3                          allows secure rpc communication us
ii  lib 7.6.dbs-13                           Wietse Venema's TCP wrappers libra
ii  lsb 3.1-23.2etch1                        Linux Standard Base 3.1 init scrip
ii  nfs 1:1.0.10-6+etch.1                    NFS support files common to client
ii  ucf 2.0020                               Update Configuration File: preserv

nfs-kernel-server recommends no packages.

-- no debconf information



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

Reply via email to