On Mon, Oct 14, 2013 at 02:16:58AM +0000, Wangminlan wrote: > Hi, > I’ve got a problem on the nfs exportfs command. I’m not sure if this is the right place to ask this, if not, can you please tell me where? > > Here’s what I need: > 1. I have a folder named /mnt/fs1 to be exported. > 2. All the host in subnetwork 192.168.0.0/16 should be able access this folder, but their root should be squashed. > 3. Some specified host in the same subnetwork can gain the root permission on the folder, for example: 192.168.0.21, 192.168.0.22. > > I’ve got a SLES11SP1 box as the nfs server, the nfs clients are SLES11SP1, too, and the protocol used between clients and server are NFSv3. > Here are the commands I used to do the export: > #exportfs –o rw,root_squash 192.168.0.0/16:/mnt/fs1 > #exportfs –o rw,no_root_squash 192.168.0.21:/mnt/fs1 > #exportfs –o rw,no_root_squash 192.168.0.22:/mnt/fs1 > After this, everything works as expected. > > But, after the following operations: > #exportfs –u 192.168.0.0/16:/mnt/fs1 /* Delete this export */ > # exportfs –o rw,root_squash 192.168.0.0/16:/mnt/fs1 /* And add it again */ > Hosts on 192.168.0.21 and 192.168.0.22 doesn’t get root permission any more. when I tried to write a file, it complains about “Permission denied”. > > So, does the order of exportfs command has something to do the final result? Or am I doing something wrong? That sounds like a bug. The contents of /proc/net/rpc/auth.unix.ip/content and /proc/net/rpc/nfsd.export/content after getting the above "permission denied" might be interesting. -- To unsubscribe from this list: send the line "unsubscribe linux-nfs" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
