Date: Sat, 23 May 2009 06:38:02 -0700 From: Randy Bush <randy@psg.com> To: Adam McDougall <mcdouga9@egr.msu.edu> Cc: freebsd-fs <freebsd-fs@freebsd.org>, Artis Caune <artis.caune@gmail.com> Subject: Re: raidz2 a bit big Message-ID: <m21vqgkkhx.wl%randy@psg.com> In-Reply-To: <20090523132644.GN35763@egr.msu.edu> References: <m28wkon90c.wl%randy@psg.com> <9e20d71e0905230537ibcaf852g1dc32b6ffc3a681d@mail.gmail.com> <m27i08km2j.wl%randy@psg.com> <20090523132644.GN35763@egr.msu.edu>
next in thread | previous in thread | raw e-mail | index | archive | help
> For an example: (btw the read speed is fantastic in a mirror and the write > is notably faster than raidz, but if your I/O is all going to go through a > gig nic, then it may not matter such as if you are just using it for a > low concurrent user stash of large files) it is attached, via gige, to a device which generates data that it stores. a nfs-attached compute box is used to crunch the data. so not a big win to reorganize, yes? > zpool create tank mirror aacd0s1d aacd1s1d mirror aacd2s1d aacd3s1d mirror aacd4s1d aacd5s1d mirror aacd6s1d aacd7s1d ahhhhhhhhhhh! lose a bunch of space, and gain a lot of speed. next time. randy
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?m21vqgkkhx.wl%randy>