On Wed, Jul 27, 2016 at 11:40:38PM +0100, Sean Brisbane wrote:
> There is a slight performance related reason for exporting disk partitions
> individually, the performance boost is server-side as Paul says. The
> advantage is that the no_subtree_check can be used without any additional
> security
On the server side, the export is defined for /export/base, not for
/export/base/x. But I see the points. It seems, that we should
probably revisit our export/mount setup :-)
frank
On 07/28/2016 12:40 AM, Sean Brisbane wrote:
There is a slight performance related reason for exporting
On 07/28/2016 12:21 AM, Paul Heinlein wrote:
On Wed, 27 Jul 2016, Frank Thommen wrote:
Hello,
does it in any respect (throughput/performance, cpu load, I/O load,
resilience, ...) matter, if one mounts subdirectories of an NFS (v3)
export into separate directories or if one just mounts the
There is a slight performance related reason for exporting disk partitions
individually, the performance boost is server-side as Paul says. The
advantage is that the no_subtree_check can be used without any additional
security risk.
It is probably the case that the /export/base/a is a partition,
On Wed, 27 Jul 2016, Frank Thommen wrote:
Hello,
does it in any respect (throughput/performance, cpu load, I/O load,
resilience, ...) matter, if one mounts subdirectories of an NFS (v3) export
into separate directories or if one just mounts the parent directory?
I.e. like this:
server:
Hello,
does it in any respect (throughput/performance, cpu load, I/O load,
resilience, ...) matter, if one mounts subdirectories of an NFS (v3)
export into separate directories or if one just mounts the parent directory?
I.e. like this:
server:/export/base/a -> /mnt/a
6 matches
Mail list logo
