Quote:
Originally Posted by
blicki
However, using LOFS to share one dataset into two local zones can be risky as hell, if both zones work on same data (read-write)
This doesn't make sense. Having multiple processes accessing the same file in r/w mode might be risky regardless of whether the file system is local or not and regardless of the accessing processes running on the same kernel or not. You can lofs mount in read-only mode should you want to avoid that specific issue. On the other hand, it is extremely common to have NFS, cifs or lofs shares in r/w mode and this definitely serves a purpose. File locking is the usual way to avoid multiple processes concurrently accessing the same file.
Quote:
Therefore I would use second opinion only.
You really shouldn't. This is not supported (see NOTES in the mount_nfs manual page). It is well know to create kernel deadlocks, which are much "riskier as hell" than the previous solution you discarded.
Bug ID: 6811806 automounter should prevent zone-to-global-zone mounts