On Mon, Jan 26, 2015 at 9:58 AM, <sf...@users.sourceforge.net> wrote: > > > Daniel Smedegaard Buus: > > > - /Archive is exported by smbd. > > > > Yup :) It's actually also exported as NFS, but at the moment it's only > > accessed via CIFS (from my sister's Mac). > > While I am unsure, I'd like to make sure one thing. > Did you specify NFS `fsid' option when exporting /Archive? > > (from aufs manual) > ---------------------------------------------------------------------- > Since aufs has no actual block device, you need to add NFS `fsid' option at > exporting. Refer to the manual of NFS about the detail of this option. > ----------------------------------------------------------------------
Yes, I was already using fsids, as ZFS has the same limitation. /titanic 192.168.10.20/255.255.255.0(async,rw,no_subtree_check,crossmnt,mountpoint=/titanic,all_squash,anonuid=1000,anongid=1000,insecure,fsid=1) /titanic/Volumes/Daniel 192.168.10.20/255.255.255.0(async,rw,no_subtree_check,crossmnt,mountpoint=/titanic,all_squash,anonuid=1000,anongid=1000,insecure,fsid=3) /Archive 192.168.10.20/255.255.255.0(async,rw,no_subtree_check,no_root_squash,mountpoint=/Archive,insecure,fsid=2) > > All of them are accessible under the single /titanic mountpoint. But, > > when the aufs /Archive mountpoint is mounted *on the server*, the > > "Processed" folder becomes off-limits to my NFS client. When /Archive > > isn't mounted on the server (or when it's mounted with the hack I > > mentioned), I can access "Processed" just fine on the client. > > Hmm... > If you can, try other branches other than zfs. If it succeeds, we can > focus on zfs. > Thing is, "succeeds" here is whether or not NFS allows access to the folder that is the first branch in the otherwise unrelated aufs mount... Hmmm... I have an idea on how to test that, let me give it a go and report back... :) > > And, as a next step in the future, I MAY ask these things. > - Build with CONFIG_AUFS_DEBUG=y and specify the module patameter > debug=1, in order to see the behaviour of nfsd. But this may not so > effective since you are not accessing /Archive. > - Using wireshark, tcpdump or something, capture the NFS packets between > NFS client and server. It will tell us which NFS operation returned > the error. > These investigations are rather troublesome and doubtful if we get good > information. So I don't ask you right now. > > > J. R. Okajima ------------------------------------------------------------------------------ Dive into the World of Parallel Programming. The Go Parallel Website, sponsored by Intel and developed in partnership with Slashdot Media, is your hub for all things parallel software development, from weekly thought leadership blogs to news, videos, case studies, tutorials and more. Take a look and join the conversation now. http://goparallel.sourceforge.net/
