<div dir="ltr">I have tried this and unfortunately NFS doesn't support extended attributes in the way that gluster needs them, which prevents brick creation.<br></div><div class="gmail_extra"><br><div class="gmail_quote">On Mon, Oct 13, 2014 at 2:49 AM, technocrat 9000 <span dir="ltr"><<a href="mailto:technocrat9000@gmail.com" target="_blank">technocrat9000@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr"><div><div><div><div><div><div><div><div>Hi, I'm interested in using GlusterFS for my simple home NAS system.<br><br></div>I'm primarily interested in being able to virtualise a bunch of different sized harddrives into one large filesystem (whilst retaining the ability to read data off any individual harddrive.)<br><br></div>At the moment, the hardware I have is:<br><br></div>- PC with several harddrives.<br></div>- Synology NAS box with several hardrives.<br><br></div>I'd like to (1) run the PC as a storage server, and have its own harddrives as one brick, and (2) the Synology NAS as a second brick. (3) I'd like to mirror the two bricks for redundancy.<br><br></div>(1) is the normal setup for GlusterFS, but is (2) actually possible?<br><br></div>If I mount the Synology NAS as "/export/NAS/", for example, can I use it as a brick? Is the fact that it's an NFS share transparent to Gluster? Or does Gluster care about the underlying hardware/filesystem used?<br><br></div>Any advice would be much appreciated, thanks!<br></div>
<br>_______________________________________________<br>
Gluster-users mailing list<br>
<a href="mailto:Gluster-users@gluster.org">Gluster-users@gluster.org</a><br>
<a href="http://supercolony.gluster.org/mailman/listinfo/gluster-users" target="_blank">http://supercolony.gluster.org/mailman/listinfo/gluster-users</a><br></blockquote></div><br></div>