Quote:
Originally Posted by
hicksd8
I'll try it again now you've said that. It seemed that the "share" showed some files to the client but not all. However, it might have confused me at the time. I'll try it again.
That would be a bug, unless perhaps with removed files that a process has still open. Make sure you are up to date with patches.
Quote:
However, I've read several places that if you share files in a local zone from the global zone that it could affect the local zone booting (getting stuck) and shutting down (getting stuck). Have you actually done this?
I'm not sure to understand your setup.
- Sharing a non global zone file system is unsupported.
- "Remotely" mounting a global zone NFS file system on a non global zone is unsupported.
- Using lofs to have global zone directories visible in a non global zone is, as far as I know, supported without restrictions. Having these directories shared by the global zone with NFS shouldn't affect the non global zone. However, when you shutdown a zone, its file systems are unmounted and perhaps can there be file busy situations here.
Quote:
I also wondered about physically moving the files to be shared up to the global and creating a symbolic link back to the local zone so that local zone users could see them too. Comments on that one?
Symbolic links do not cross filesystem name space. I'm not sure to get "moving the files up to the global", they are already in the global zone (too), aren't they ?
Quote:
Or vice versa, leave the files to be shared in the local, create a link at the global zone and share that.
Symbolic would be resolved by the NFS client so won't see the non global zone files.