Shain, If you are planning on taking snapshots of the underlying filesystems then #2 would be better. If you are not planning on taking snapshots then #1 and #2 are equal really and so I would say that #1 is fine because there are less filesystems to manage. I hope this clarifies things. Since ZFS snapshots are done at the filesystem level, if you wanted to take a snapshot of just music then you could not do that unless music was on its own ZFS filesystem. -Jacob -----Original Message----- From: gluster-users-bounces at gluster.org [mailto:gluster-users-bounces at gluster.org] On Behalf Of Shain Miley Sent: Thursday, January 06, 2011 1:47 PM To: Gluster General Discussion List Subject: ZFS setup question Hello, I am in the process of setting up my Gluster shares and I am looking at the following two setup options and I am wondering if anyone can speak to the pros/cons of either: 1) Create one large zfs filesystem for gluster. eg: zfs create pool1/glusterfs and then create several folders with 'mkdir' inside '/pool1/glusterfs' (music,videos,documents). 2) Create 1 zfs filesystem per share. eg: zfs create pool1/glusterfs zfs create pool1/glusterfs/music zfs create pool1/glusterfs/videos zfs create pool1/glusterfs/documents I would then share /pool1/glusterfs out with gluster (I do not want to have to have an overly complicated .vol file with each share having it's own gluster volume). Any thoughts would be great. Thanks, Shain _______________________________________________ Gluster-users mailing list Gluster-users at gluster.org http://gluster.org/cgi-bin/mailman/listinfo/gluster-users
