Wilhelm Meier:
> gs ~ # ls -l /mnt/test/A/
> ls: /mnt/test/A/boot: Operation not permitted
> ls: /mnt/test/A/etc: Operation not permitted
:::
I see.
Probably this scenario is your problem.
- AP access the file 'unionfs/dirA/fileB'
- usually filesystem parses and lookups all the path components.
- additionally, unionfs lookups the whiteout '.wh.fileB' before 'fileB'.
If AP access the file 'unionfs/dirA/.wh.fileB' directly, unionfs
returns EPERM.
- your AP on nfs client accesses a file 'x'.
- unionfs on nfs clinet lookups '.wh.x'.
- unionfs on nfs server rejected looking up whiteout directly
and returns EPERM.
I think currect unionfs doesn't support nested unionfs.
Junjiro Okajima
_______________________________________________
unionfs mailing list
[email protected]
http://www.fsl.cs.sunysb.edu/mailman/listinfo/unionfs
