Hi,
I've the following trouble:
after some hard traffic or a nfs restart my exports sometimes switches to
"ro". I don't have that problem if I boot the server first and all clients
connect afterwards. But that gets a little messy because I've got 110
clients....
If I use "exportfs -rv" this usually solves the problem, but not always.
kernelversion 2.4.18
nfs Version 1.0
distribution: debian/woody
cat /var/lib/nfs/xtab | grep myotherhost
/data01
myotherhost.foo.bar(ro,async,wdelay,hide,secure,root_squash,no_all_squash,subtree_check,
secure_locks,mapping=identity,anonuid=-2,anongid=-2)
# /etc/exports: the access control list for filesystems which may be exported
# to NFS clients. See exports(5).
#
/data01 myhost.foo.bar(rw,no_root_squash)
/data01 my*.foo.bar(rw)
/data01 www-linux.foo.bar(rw)
/data01 *.foo.bar(ro)
--
Oliver Korff, credativ GmbH
Karl-Heinz-Beckurts-Str. 13
52428 J?lich, Germany
Tel.: +49 (2461) 69071-0
Fax: +49 (2461) 69071-1
-------------------------------------------------------
This sf.net email is sponsored by:ThinkGeek
Welcome to geek heaven.
http://thinkgeek.com/sf
_______________________________________________
NFS maillist - [email protected]
https://lists.sourceforge.net/lists/listinfo/nfs
On Friday August 2, [email protected] wrote:
> Hi,
>
> I've the following trouble:
> after some hard traffic or a nfs restart my exports sometimes switches to
> "ro". I don't have that problem if I boot the server first and all clients
> connect afterwards. But that gets a little messy because I've got 110
> clients....
> If I use "exportfs -rv" this usually solves the problem, but not always.
>
>
> kernelversion 2.4.18
> nfs Version 1.0
> distribution: debian/woody
>
> cat /var/lib/nfs/xtab | grep myotherhost
> /data01
> myotherhost.foo.bar(ro,async,wdelay,hide,secure,root_squash,no_all_squash,subtree_check,
> secure_locks,mapping=identity,anonuid=-2,anongid=-2)
>
> # /etc/exports: the access control list for filesystems which may be exported
> # to NFS clients. See exports(5).
> #
> /data01 myhost.foo.bar(rw,no_root_squash)
> /data01 my*.foo.bar(rw)
> /data01 www-linux.foo.bar(rw)
> /data01 *.foo.bar(ro)
You have an ambiguity here. You have three different rules that apply
to myhost.for.bar. One is clearly more explicit and so is used.
But myotherhost.foo.bar could clearly match two rules, and it is not
obvious (to a computer) that one match is more explicit than another.
So I guess you get pot-luck.
You need to find a way to be more explicit.
Maybe:
> /data01 myhost.foo.bar(rw,no_root_squash)
> /data01 my*.foo.bar(rw)
> /data01 www-linux.foo.bar(rw)
> /data01 [^m]*.foo.bar(ro)
> /data01 ?[^y]*.foo.bar(ro)
NeilBrown
-------------------------------------------------------
This sf.net email is sponsored by:ThinkGeek
Welcome to geek heaven.
http://thinkgeek.com/sf
_______________________________________________
NFS maillist - [email protected]
https://lists.sourceforge.net/lists/listinfo/nfs