I don't think brick splitting implemented by LVM would affect directory browsing any more than adding an additional brick would, ----- Original Message ----- From: "Justin Clift" <justin@xxxxxxxxxxx> To: "Dan Lambright" <dlambrig@xxxxxxxxxx> Cc: "Shyamsundar Ranganathan" <srangana@xxxxxxxxxx>, "Gluster Devel" <gluster-devel@xxxxxxxxxxx> Sent: Thursday, June 26, 2014 12:01:16 PM Subject: Re: Data classification proposal On 26/06/2014, at 4:54 PM, Dan Lambright wrote: > Implementing brick splitting using LVM would allow you to treat each logical volume (split) as an independent brick. Each split would have its own .glusterfs subdirectory. I think this would help with taking snapshots as well. Would brick splitting make directory browsing latency even scarier? + Justin -- GlusterFS - http://www.gluster.org An open source, distributed file system scaling to several petabytes, and handling thousands of clients. My personal twitter: twitter.com/realjustinclift _______________________________________________ Gluster-devel mailing list Gluster-devel@xxxxxxxxxxx http://supercolony.gluster.org/mailman/listinfo/gluster-devel
