Another good reason to keep your LUN's small is the possibility of having to fsck the filesystem. Even on really fast disk it can take days to fsck a 16TB LUN. Gluster hides the multiple LUNs in a volume so you never have to deal with them, other than a bit more SAN management and more typing to setup a volume the first time there is no downside. Thanks, Craig --> Craig Carl Senior Systems Engineer Gluster From: "Daniel Mons" <daemons at kanuka.com.au> To: gluster-users at gluster.org Sent: Saturday, October 23, 2010 5:38:12 AM Subject: Re: Question about Volume Type when bricks are on SAN On Sat, Oct 23, 2010 at 5:22 AM, Mike Hanby <mhanby at uab.edu> wrote: > Each Gluster server has been allocated a single 9TB LUN (if it makes any sense to do so, I could have the SAN admin provide many smaller LUNs per server and use LVM to combine into single brick) Generally speaking you should LVM over many smaller LUNs. With multiport FC HBAs being the standard, you will get better performance as separate requests hit separate LUNs. Multiple LUNs mean multiple SCSI queues, which can reduce I/O latency substantially. We try to cap our LUNs at around 100GB. It does make for a lot of LUNs per server, but it's worth if for the performance gain. Talk to your storage admin and ask them what their recommendation is based on your vendor and their best practices. -Dan _______________________________________________ Gluster-users mailing list Gluster-users at gluster.org http://gluster.org/cgi-bin/mailman/listinfo/gluster-users
