On Fri, Mar 13, 2009 at 12:03 PM, Pepito Perez <span dir="ltr"><<a href="mailto:jvoorhees1@gmail.com">jvoorhees1@gmail.com</a>></span> wrote:<br><div class="gmail_quote"><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
<div class="im">On Fri, Mar 13, 2009 at 10:20 AM, Richard Ray <<a href="mailto:rray@mstc.state.ms.us">rray@mstc.state.ms.us</a>> wrote:<br>
> With fs mounted on HN what problems might I run into if I mount --bind the<br>
> fs to multiple VE<br>
> Should this situation be handled differently<br>
> Maybe mount --bind on one VE and nfs export to second VE<br>
> Suggestion appreciated<br>
><br>
</div>I made a similar question related to sharing a mount point between a<br>
VE and HN exported via NFS, but nobody answered my question.<br>
<br>
However right know I'm bind mounting a unique path between three VEs<br>
without problems. Is it possible to occur a file locking maybe? I<br>
don't know ... yet<br>
<div><div></div><div class="h5"></div></div></blockquote><div><br>On many machines I mount a directory via NFS on the hardware node and then "mount --bind" it to many (8) VEs on that hardware node and it works great. I also bind mount /usr between identical VEs to reduce footprint. As long as the directory is effectively read only, or it's treated as a shared directory.<br>
<br></div></div>Bill<br><br>-- <br>Bill Comisky<br><a href="mailto:bcomisky@pobox.com">bcomisky@pobox.com</a><br>