Yes, this is fixed in burt 113819, which can be gotten as patch 6.5P5.
The new logic also appears to be somewhat broken, not sure if this is covered in that burt --
Given (pre-6.5):
/vol/vol0/foo -ro=192.168.0.0/16,rw=192.168.1.1:10.1.1.1
The export would work as expected (192.168.1.1 and 10.1.1.1 have write access, 192.168.30.30 has ro access). However, under 6.5 this results in only having 10.1.1.1 having write access. Presumably this is due to na_exports(5):
11) -ro= trumps -rw=..which is perfectly reasonable, IFF a specific host was referenced in both cases. In the event that a host is referred to indirectly (ie. via network or netgroup), the specific reference should always win. Hence, example from man page would be extended (perhaps further still to illustrate priority of netgroup vs. network):
12) -ro=DIRECT trumps -rw=INDIRECT 13) -rw=DIRECT trumps -ro=INDIRECT 14) -ro=DIRECT trumps -ro=DIRECTOn Sun, 22 Feb 2004, Haynes, Tom wrote:
This can be tracked as burt 115086.
I'm just about to make the public report available.
The fix will come out in 6.5.1.
Hello,
If you plan to upgrade to 6.5 make sure you check your /etc/exports file after rebooting with 6.5 for the first time. I just upgraded an 840 and an 880 and on both machines the exports file has been rewritten giving everyone read-only access.
Running 6.4.2: /vol/vol10 -access=donald.zdv.uni-mainz.de:unixadm.zdv.uni-mainz.de:dschinny.zdv.uni-mainz.de,root=donald.zdv.uni-mainz.de:unixadm.zdv.uni-mainz.de /vol/vol11 -access=donald.zdv.uni-mainz.de:unixadm.zdv.uni-mainz.de:dschinny.zdv.uni-mainz.de,root=donald.zdv.uni-mainz.de:unixadm.zdv.uni-mainz.de ...
Running 6.5P5: /vol/vol10 -ro,rw=donald.zdv.uni-mainz.de:unixadm.zdv.uni-mainz.de:dschinny.zdv.uni-mainz.de,root=donald.zdv.uni-mainz.de:unixadm.zdv.uni-mainz.de /vol/vol11 -ro,rw=donald.zdv.uni-mainz.de:unixadm.zdv.uni-mainz.de:dschinny.zdv.uni-mainz.de,root=donald.zdv.uni-mainz.de:unixadm.zdv.uni-mainz.de ...
Carsten
-- Tom Haynes, ex-cfb thomas@netapp.com