Thank you once again for your input. It's highly appreciated.
On Sat, Mar 21, 2015 at 9:53 AM, Melkor Lord <[email protected]> wrote: > On Thu, Mar 19, 2015 at 9:11 PM, Rumen Telbizov <[email protected]> > wrote: > > Thank you for your answer Melkor. >> > > You're welcome! > > >> This is the kind of experience I was looking for actually. I am happy >> that it has worked fine for you. >> >> Anybody coming across any issues while reading directly from the >> underlying disk? >> > > 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. > > 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. > > 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 :-) > > -- > Unix _IS_ user friendly, it's just selective about who its friends are. > -- Rumen Telbizov Unix Systems Administrator <http://telbizov.com>
_______________________________________________ Gluster-users mailing list [email protected] http://www.gluster.org/mailman/listinfo/gluster-users
