<div dir="ltr"><div class="gmail_extra"><div class="gmail_quote">On Thu, Mar 19, 2015 at 9:11 PM, Rumen Telbizov <span dir="ltr"><<a href="mailto:telbizov@gmail.com" target="_blank">telbizov@gmail.com</a>></span> wrote:<br><br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr"><div style="font-family:tahoma,sans-serif">Thank you for your answer Melkor.<br></div></div></blockquote><div><br></div><div>You're welcome!<br></div><div> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr"><div style="font-family:tahoma,sans-serif"></div><div style="font-family:tahoma,sans-serif">This is the kind of experience I was looking for actually. I am happy that it has worked fine for you.<br><br></div><div style="font-family:tahoma,sans-serif">Anybody coming across any issues while reading directly from the underlying disk?<br></div></div></blockquote><div><br></div><div>I don't think you'll find any issues, at least on the replica scenario since the copied data is exactly the same for every brick in the cluster. After all, Gluster only exports a directory content accross the network. I don't really see how it could mess things up, especially if all you do is reading the files on the exported directory.<br><br></div><div>I see the workflow basically as NFS or Samba. You can acces the exported root and remove/add files from it without creating havock for the clients except the usual "can't access xxx" if you remove/rename a file before the client refreshes the directory listing.<br></div><div></div><br></div><div class="gmail_quote">I won't try such things though (not outside a test environment only) on a distributed scenario since in that particular case, the files are splitted in bits. Still, I think read only is always safe :-)<br></div><br>-- <br><div class="gmail_signature">Unix _IS_ user friendly, it's just selective about who its friends are.</div>
</div></div>