[prev in list] [next in list] [prev in thread] [next in thread] 

List:       toasters
Subject:    Re: cDOT 8.2.x, grow aggregates or new ones?
From:       Vervloesem Wouter <wouter.vervloesem () neoria ! be>
Date:       2016-09-08 8:22:46
Message-ID: F3CDC0B1-4FD6-4782-8D9E-E652E42E22FE () neoria ! be
[Download RAW message or body]

Recently I don't recommend to create aggregates 'as big as possible' any mo=
re.
I would create aggregates between 50-100TB and than move volumes online bet=
ween them if needed.

This way you could relocate / phase out some aggregates more easy than if y=
ou have few 'extra large' aggregates.


Met vriendelijke groeten,

Wouter Vervloesem<https://be.linkedin.com/pub/wouter-vervloesem/5/a63/a41>
Storage Consultant

Neoria NV<http://www.neoria.be/>
Prins Boudewijnlaan 41 - 2650 Edegem
T +32 3 451 23 82 | M +32 496 52 93 61

Op 8 sep. 2016, om 05:25 heeft Francis Kim <fkim@BERKCOM.com<mailto:fkim@be=
rkcom.com>> het volgende geschreven:

John,

I generally favor fewer larger aggregates, to keep capacity fragmentation d=
own.  One exception to this personal rule is if I have a bunch of DS4243s t=
hat I will look to retire in the near(er) future with hot-shelf remove than=
 the newer shelves with IOM6 or IOM12, in which case I will try not to mix =
DS4243s and the newer shelves in the same aggregate.

Noticed you have several, smallish sized, aggregates of the same disk type =
in each of your nodes.  I suppose they are different size/rpm disks?  Or wa=
nted to segregate applications to different aggregates?

On Sep 7, 2016, at 5:52 PM, John Stoffel <john@stoffel.org<mailto:john@stof=
fel.org>> wrote:


Guys,

I've got a four node, 8060 cluster running cDOT 8.2.x which we just
added in a bunch of disks, spread evenly across our two HA pairs.  2 x
DS4246 x 2Tb SATA, and 4 x DS2246 x 600g SAS shelves/disks.

I suspect the smart thing to do is to just grow my existing
aggregates, which lets me grow existing volumes, etc without too much
trouble.  And of course I would add in disks in complete Raid Groups.

Or do people think I should just create brand new aggregates and move
as needed?  Do I really need to worry about reallocation issues when I
do these adds?

My current setup is:

n1sas1     20.67TB    7.37TB   64% online      28 n1               raid_dp,
n1sata1    56.75TB   12.15TB   79% online      79 n1               raid_dp,
n1sata2    56.75TB    7.30TB   87% online      99 n1               raid_dp,
n2sas1     26.92TB    6.19TB   77% online      20 n2               raid_dp,
n2sas2     26.92TB    9.51TB   65% online      29 n2               raid_dp,
n2sas3     20.19TB    9.54TB   53% online       6 n2               raid_dp,
n2ssd1     13.09TB   10.84TB   17% online       7 n2               raid_dp,
n3sas1     26.92TB    7.24TB   73% online      31 n3               raid_dp,
n3sas2     26.92TB    8.13TB   70% online      37 n3               raid_dp,
n3sas3     20.19TB    2.97TB   85% online      50 n3               raid_dp,
n4sata1    56.75TB    9.73TB   83% online      69 n4               raid_dp,
n4sata2    53.84TB    9.46TB   82% online      33 n4               raid_dp,

As you can see, we did screw up in n1/n2 by having both SAS and SATA
aggregates on the same head.  Ooops.  We fixed that for the second
pair when we grew the cluster.

Just looking for a confirmation of my thinking.

Thanks,
John
_______________________________________________
Toasters mailing list
Toasters@teaparty.net<mailto:Toasters@teaparty.net>
http://www.teaparty.net/mailman/listinfo/toasters


_______________________________________________
Toasters mailing list
Toasters@teaparty.net<mailto:Toasters@teaparty.net>
http://www.teaparty.net/mailman/listinfo/toasters


[Attachment #3 (text/html)]

<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=us-ascii">
</head>
<body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: \
after-white-space;" class=""> Recently I don't recommend to create aggregates 'as big \
as possible' any more. <div class="">I would create aggregates between 50-100TB and \
than move volumes online between them if needed.</div> <div class=""><br class="">
</div>
<div class="">This way you could relocate / phase out some aggregates more easy than \
if you have few 'extra large' aggregates.</div> <div class="">
<div class=""><span style="font-size: 9pt; font-style: normal; font-variant: normal; \
font-weight: normal; letter-spacing: normal; orphans: auto; text-align: start; \
text-indent: 0px; text-transform: none; white-space: normal; widows: auto; \
word-spacing: 0px; -webkit-text-stroke-width: 0px; font-family: 'Century Gothic'; \
color: rgb(91, 91, 89);" class=""><br class="Apple-interchange-newline"> <br \
class="Apple-interchange-newline"> Met vriendelijke groeten,<br class="">
<br class="">
</span><a href="https://be.linkedin.com/pub/wouter-vervloesem/5/a63/a41" \
style="font-family: Helvetica; font-size: 12px; font-style: normal; font-variant: \
normal; font-weight: normal; letter-spacing: normal; orphans: auto; text-align: \
start; text-indent: 0px; text-transform: none; white-space: normal; widows: auto; \
word-spacing: 0px; -webkit-text-stroke-width: 0px;" class=""><b class=""><span \
style="font-size: 11pt; font-family: 'Century Gothic'; color: rgb(214, 212, 39); \
text-decoration: none;" class="">Wouter  Vervloesem</span></b></a><b style="color: \
rgb(0, 0, 0); font-family: Helvetica; font-size: 12px; font-style: normal; \
font-variant: normal; letter-spacing: normal; orphans: auto; text-align: start; \
text-indent: 0px; text-transform: none; white-space: normal; widows: auto; \
word-spacing: 0px; -webkit-text-stroke-width: 0px;" class=""><span style="font-size: \
9pt; font-family: 'Century Gothic'; color: rgb(214, 212, 39);" class=""><br class=""> \
</span></b><span style="font-size: 9pt; font-style: normal; font-variant: normal; \
font-weight: normal; letter-spacing: normal; orphans: auto; text-align: start; \
text-indent: 0px; text-transform: none; white-space: normal; widows: auto; \
word-spacing: 0px; -webkit-text-stroke-width: 0px; font-family: 'Century Gothic'; \
color: rgb(91, 91, 89);" class="">Storage  Consultant</span><b style="color: rgb(0, \
0, 0); font-family: Helvetica; font-size: 12px; font-style: normal; font-variant: \
normal; letter-spacing: normal; orphans: auto; text-align: start; text-indent: 0px; \
text-transform: none; white-space: normal; widows: auto; word-spacing: 0px; \
-webkit-text-stroke-width: 0px;" class=""><span style="font-size: 9pt; font-family: \
'Century Gothic'; color: rgb(214, 212, 39);" class=""><br class=""> <br class="">
</span></b><a href="http://www.neoria.be/" style="font-family: Helvetica; font-size: \
12px; font-style: normal; font-variant: normal; font-weight: normal; letter-spacing: \
normal; orphans: auto; text-align: start; text-indent: 0px; text-transform: none; \
white-space: normal; widows: auto; word-spacing: 0px; -webkit-text-stroke-width: \
0px;" class=""><b class=""><span style="font-size: 9pt; font-family: 'Century \
Gothic'; color: rgb(91, 91, 89); text-decoration: none;" class="">Neoria  \
NV</span></b></a><b style="color: rgb(0, 0, 0); font-family: Helvetica; font-size: \
12px; font-style: normal; font-variant: normal; letter-spacing: normal; orphans: \
auto; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; \
widows: auto; word-spacing: 0px; -webkit-text-stroke-width: 0px;" class=""><span \
style="font-size: 9pt; font-family: 'Century Gothic'; color: rgb(214, 212, 39);" \
class=""><br class=""> </span></b><span style="font-size: 9pt; font-style: normal; \
font-variant: normal; font-weight: normal; letter-spacing: normal; orphans: auto; \
text-align: start; text-indent: 0px; text-transform: none; white-space: normal; \
widows: auto; word-spacing: 0px; -webkit-text-stroke-width: 0px; font-family: \
'Century Gothic'; color: rgb(91, 91, 89);" class="">Prins  Boudewijnlaan 41 - 2650 \
Edegem</span><b style="color: rgb(0, 0, 0); font-family: Helvetica; font-size: 12px; \
font-style: normal; font-variant: normal; letter-spacing: normal; orphans: auto; \
text-align: start; text-indent: 0px; text-transform: none; white-space: normal; \
widows: auto; word-spacing: 0px; -webkit-text-stroke-width: 0px;" class=""><span \
style="font-size: 9pt; font-family: 'Century Gothic'; color: rgb(214, 212, 39);" \
class=""><br class=""> </span></b><b style="color: rgb(0, 0, 0); font-family: \
Helvetica; font-size: 12px; font-style: normal; font-variant: normal; letter-spacing: \
normal; orphans: auto; text-align: start; text-indent: 0px; text-transform: none; \
white-space: normal; widows: auto; word-spacing: 0px; -webkit-text-stroke-width: \
0px;" class=""><span style="font-size: 9pt; font-family: 'Century Gothic'; color: \
rgb(91, 91, 89);" class="">T</span></b><span style="font-size: 9pt; font-style: \
normal; font-variant: normal; font-weight: normal; letter-spacing: normal; orphans: \
auto; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; \
widows: auto; word-spacing: 0px; -webkit-text-stroke-width: 0px; font-family: \
'Century Gothic'; color: rgb(91, 91, 89);" class=""><span \
class="Apple-converted-space">&nbsp;</span>&#43;32  3 451 23 82 |&nbsp;<b \
class="">M</b><span class="Apple-converted-space">&nbsp;</span>&#43;32 496 52 93 \
61</span><b style="color: rgb(0, 0, 0); font-family: Helvetica; font-size: 12px; \
font-style: normal; font-variant: normal; letter-spacing: normal; orphans: auto; \
text-align: start; text-indent: 0px; text-transform: none; white-space: normal; \
widows: auto; word-spacing: 0px; -webkit-text-stroke-width: 0px;" class=""><span \
style="font-size: 9pt; font-family: 'Century Gothic'; color: rgb(214, 212, 39);" \
class=""><o:p class=""></o:p></span></b> </div>
<br class="">
<div>
<blockquote type="cite" class="">
<div class="">Op 8 sep. 2016, om 05:25 heeft Francis Kim &lt;<a \
href="mailto:fkim@berkcom.com" class="">fkim@BERKCOM.com</a>&gt; het volgende \
geschreven:</div> <br class="Apple-interchange-newline">
<div class="">
<div class="">John,<br class="">
<br class="">
I generally favor fewer larger aggregates, to keep capacity fragmentation down. \
&nbsp;One exception to this personal rule is if I have a bunch of DS4243s that I will \
look to retire in the near(er) future with hot-shelf remove than the newer shelves \
with IOM6 or  IOM12, in which case I will try not to mix DS4243s and the newer \
shelves in the same aggregate.<br class=""> <br class="">
Noticed you have several, smallish sized, aggregates of the same disk type in each of \
your nodes. &nbsp;I suppose they are different size/rpm disks? &nbsp;Or wanted to \
segregate applications to different aggregates?<br class=""> <br class="">
<blockquote type="cite" class="">On Sep 7, 2016, at 5:52 PM, John Stoffel &lt;<a \
href="mailto:john@stoffel.org" class="">john@stoffel.org</a>&gt; wrote:<br class=""> \
<br class=""> <br class="">
Guys,<br class="">
<br class="">
I've got a four node, 8060 cluster running cDOT 8.2.x which we just<br class="">
added in a bunch of disks, spread evenly across our two HA pairs. &nbsp;2 x<br \
class=""> DS4246 x 2Tb SATA, and 4 x DS2246 x 600g SAS shelves/disks.<br class="">
<br class="">
I suspect the smart thing to do is to just grow my existing<br class="">
aggregates, which lets me grow existing volumes, etc without too much<br class="">
trouble. &nbsp;And of course I would add in disks in complete Raid Groups.<br \
class=""> <br class="">
Or do people think I should just create brand new aggregates and move<br class="">
as needed? &nbsp;Do I really need to worry about reallocation issues when I<br \
class=""> do these adds?<br class="">
<br class="">
My current setup is:<br class="">
<br class="">
n1sas1 &nbsp;&nbsp;&nbsp;&nbsp;20.67TB &nbsp;&nbsp;&nbsp;7.37TB &nbsp;&nbsp;64% \
online &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;28 n1 \
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;raid_dp,<br \
class=""> n1sata1 &nbsp;&nbsp;&nbsp;56.75TB &nbsp;&nbsp;12.15TB &nbsp;&nbsp;79% \
online &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;79 n1 \
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;raid_dp,<br \
class=""> n1sata2 &nbsp;&nbsp;&nbsp;56.75TB &nbsp;&nbsp;&nbsp;7.30TB &nbsp;&nbsp;87% \
online &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;99 n1 \
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;raid_dp,<br \
class=""> n2sas1 &nbsp;&nbsp;&nbsp;&nbsp;26.92TB &nbsp;&nbsp;&nbsp;6.19TB \
&nbsp;&nbsp;77% online &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;20 n2 \
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;raid_dp,<br \
class=""> n2sas2 &nbsp;&nbsp;&nbsp;&nbsp;26.92TB &nbsp;&nbsp;&nbsp;9.51TB \
&nbsp;&nbsp;65% online &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;29 n2 \
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;raid_dp,<br \
class=""> n2sas3 &nbsp;&nbsp;&nbsp;&nbsp;20.19TB &nbsp;&nbsp;&nbsp;9.54TB \
&nbsp;&nbsp;53% online &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;6 n2 \
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;raid_dp,<br \
class=""> n2ssd1 &nbsp;&nbsp;&nbsp;&nbsp;13.09TB &nbsp;&nbsp;10.84TB &nbsp;&nbsp;17% \
online &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;7 n2 \
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;raid_dp,<br \
class=""> n3sas1 &nbsp;&nbsp;&nbsp;&nbsp;26.92TB &nbsp;&nbsp;&nbsp;7.24TB \
&nbsp;&nbsp;73% online &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;31 n3 \
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;raid_dp,<br \
class=""> n3sas2 &nbsp;&nbsp;&nbsp;&nbsp;26.92TB &nbsp;&nbsp;&nbsp;8.13TB \
&nbsp;&nbsp;70% online &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;37 n3 \
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;raid_dp,<br \
class=""> n3sas3 &nbsp;&nbsp;&nbsp;&nbsp;20.19TB &nbsp;&nbsp;&nbsp;2.97TB \
&nbsp;&nbsp;85% online &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;50 n3 \
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;raid_dp,<br \
class=""> n4sata1 &nbsp;&nbsp;&nbsp;56.75TB &nbsp;&nbsp;&nbsp;9.73TB &nbsp;&nbsp;83% \
online &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;69 n4 \
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;raid_dp,<br \
class=""> n4sata2 &nbsp;&nbsp;&nbsp;53.84TB &nbsp;&nbsp;&nbsp;9.46TB &nbsp;&nbsp;82% \
online &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;33 n4 \
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;raid_dp,<br \
class=""> <br class="">
As you can see, we did screw up in n1/n2 by having both SAS and SATA<br class="">
aggregates on the same head. &nbsp;Ooops. &nbsp;We fixed that for the second<br \
class=""> pair when we grew the cluster.<br class="">
<br class="">
Just looking for a confirmation of my thinking.<br class="">
<br class="">
Thanks,<br class="">
John<br class="">
_______________________________________________<br class="">
Toasters mailing list<br class="">
<a href="mailto:Toasters@teaparty.net" class="">Toasters@teaparty.net</a><br \
class=""> http://www.teaparty.net/mailman/listinfo/toasters<br class="">
</blockquote>
<br class="">
<br class="">
_______________________________________________<br class="">
Toasters mailing list<br class="">
<a href="mailto:Toasters@teaparty.net" class="">Toasters@teaparty.net</a><br \
class=""> http://www.teaparty.net/mailman/listinfo/toasters<br class="">
</div>
</div>
</blockquote>
</div>
<br class="">
</div>
</body>
</html>



_______________________________________________
Toasters mailing list
Toasters@teaparty.net
http://www.teaparty.net/mailman/listinfo/toasters

--===============6953643823250173496==--

[prev in list] [next in list] [prev in thread] [next in thread] 

Configure | About | News | Add a list | Sponsored by KoreLogic