<HTML >
<HEAD>
<META http-equiv="Content-Type" content="text/html; charset=us-ascii">
<meta name=Generator content="Microsoft Word 11 (filtered medium)">
<!--[if !mso]>
<style>
v\:* {behavior:url(#default#VML);}
o\:* {behavior:url(#default#VML);}
w\:* {behavior:url(#default#VML);}
.shape {behavior:url(#default#VML);}
</style>
<![endif]--><o:SmartTagType
namespaceuri="urn:schemas-microsoft-com:office:smarttags" name="City"/>
<o:SmartTagType namespaceuri="urn:schemas-microsoft-com:office:smarttags"
name="place"/>
<o:SmartTagType namespaceuri="urn:schemas-microsoft-com:office:smarttags"
name="PersonName"/>
<!--[if !mso]>
<style>
st1\:*{behavior:url(#default#ieooui) }
</style>
<![endif]-->
<style>
<!--
/* Font Definitions */
@font-face
        {font-family:Tahoma;
        panose-1:2 11 6 4 3 5 4 4 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
        {margin:0in;
        margin-bottom:.0001pt;
        font-size:12.0pt;
        font-family:"Times New Roman";}
a:link, span.MsoHyperlink
        {color:blue;
        text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
        {color:blue;
        text-decoration:underline;}
span.EmailStyle17
        {mso-style-type:personal-reply;
        font-family:Arial;
        color:navy;}
@page Section1
        {size:8.5in 11.0in;
        margin:1.0in 1.25in 1.0in 1.25in;}
div.Section1
        {page:Section1;}
-->
</style>
</HEAD>
<BODY lang=EN-US link=blue vlink=blue>
<DIV>
<div class=Section1>
<p class=MsoNormal><font size=2 color=navy face=Arial><span style='font-size:
10.0pt;font-family:Arial;color:navy'>Most of the array vendors out there allow
for SSDs these days. They generally propose something like SSDs for the most
performance sensitive data, fibre drives for somewhat performance sensitive
data and ATA drives for the rest all in the same array.<o:p></o:p></span></font></p>
<p class=MsoNormal><font size=2 color=navy face=Arial><span style='font-size:
10.0pt;font-family:Arial;color:navy'><o:p> </o:p></span></font></p>
<p class=MsoNormal><font size=2 color=navy face=Arial><span style='font-size:
10.0pt;font-family:Arial;color:navy'>Also there’s companies selling PCI
boards that are SSDs so you can just add one to an existing server that doesn’t
support SSDs otherwise. Check out a company called RamSan for those and some
fairly good whitepapers.<o:p></o:p></span></font></p>
<p class=MsoNormal><font size=2 color=navy face=Arial><span style='font-size:
10.0pt;font-family:Arial;color:navy'><o:p> </o:p></span></font></p>
<p class=MsoNormal><font size=2 color=navy face=Arial><span style='font-size:
10.0pt;font-family:Arial;color:navy'>One problem with SSDs is they use flash
which degrades over time. RamSan says they have an algorithm that directs
which bits are written where so balances this to extend the life of the SSD.
I saw similar discussion (maybe even the same one) at a presentation at AUUG
last year but have since lost the literature for that.<o:p></o:p></span></font></p>
<p class=MsoNormal><font size=2 color=navy face=Arial><span style='font-size:
10.0pt;font-family:Arial;color:navy'><o:p> </o:p></span></font></p>
<p class=MsoNormal><font size=2 color=navy face=Arial><span style='font-size:
10.0pt;font-family:Arial;color:navy'>RamSan says they also make RAM based
systems that don’t have that problem.<o:p></o:p></span></font></p>
<p class=MsoNormal><font size=2 color=navy face=Arial><span style='font-size:
10.0pt;font-family:Arial;color:navy'><o:p> </o:p></span></font></p>
<div>
<div class=MsoNormal align=center style='text-align:center'><font size=3
face="Times New Roman"><span style='font-size:12.0pt'>
<hr size=2 width="100%" align=center tabindex=-1>
</span></font></div>
<p class=MsoNormal><b><font size=2 face=Tahoma><span style='font-size:10.0pt;
font-family:Tahoma;font-weight:bold'>From:</span></font></b><font size=2
face=Tahoma><span style='font-size:10.0pt;font-family:Tahoma'>
ale-bounces@ale.org [mailto:ale-bounces@ale.org] <b><span style='font-weight:
bold'>On Behalf Of </span></b>Greg Clifton<br>
<b><span style='font-weight:bold'>Sent:</span></b> Thursday, April 22, 2010
3:00 PM<br>
<b><span style='font-weight:bold'>To:</span></b> <st1:PersonName w:st="on">Atlanta
Linux Enthusiasts - Yes! We run Linux!</st1:PersonName><br>
<b><span style='font-weight:bold'>Subject:</span></b> Re: [ale] XFS on Linux -
Is it ready for prime time?</span></font><o:p></o:p></p>
</div>
<p class=MsoNormal><font size=3 face="Times New Roman"><span style='font-size:
12.0pt'><o:p> </o:p></span></font></p>
<p class=MsoNormal style='margin-bottom:12.0pt'><font size=3
face="Times New Roman"><span style='font-size:12.0pt'>Any feedback on the SSD
question? They are inherently more reliable (by at least an order of
magnitude), no? Read and Write Performance is going up as well as capacities,
and prices are coming down. A multi TB SSD array is probably not something that
most of us could afford to park at home just yet, but maybe in another 2-5 yrs?<br>
<br>
GC<o:p></o:p></span></font></p>
<div>
<p class=MsoNormal><font size=3 face="Times New Roman"><span style='font-size:
12.0pt'>On Thu, Apr 22, 2010 at 2:44 PM, Greg Freemyer <<a
href="mailto:greg.freemyer@gmail.com">greg.freemyer@gmail.com</a>> wrote:<o:p></o:p></span></font></p>
<p class=MsoNormal><font size=3 face="Times New Roman"><span style='font-size:
12.0pt'>Jim,<br>
<br>
Linux mdraid supports 3 drive mirrors. You should have similar write<br>
performance to a 2 drive mirror and improved read-performance.<br>
<br>
So if your using mdraid, you might want to consider raid 10 with 3<br>
drive mirrors, and maybe one hot spare for the whole array.<br>
<br>
Greg<o:p></o:p></span></font></p>
<div>
<p class=MsoNormal><font size=3 face="Times New Roman"><span style='font-size:
12.0pt'><br>
On Thu, Apr 22, 2010 at 2:26 PM, Jim Kinney <<a
href="mailto:jim.kinney@gmail.com">jim.kinney@gmail.com</a>> wrote:<o:p></o:p></span></font></p>
</div>
<div>
<div>
<p class=MsoNormal style='margin-bottom:12.0pt'><font size=3
face="Times New Roman"><span style='font-size:12.0pt'>> RAID 5 was an
invention for a time when hard drives were total crap tons of<br>
> money. The pain of losing a drive in a RAID 5 array is just no longer<br>
> balanced by the cost of the drives. If a 1TB drive is only $100, it's<br>
> bluntly dirt cheap now to have a hot spare in a 4 active drive RAID 10<br>
> system. The recovery is much easier and faster when checksums don't have
to<br>
> be calculated for every stinking block on the drive(s).<br>
><br>
> My ideal rig: Striped array for speed composed of mirrored triplets - 2<br>
> active, one hot spare per active pair.<br>
><br>
> On Thu, Apr 22, 2010 at 1:05 PM, Greg Clifton <<a
href="mailto:gccfof5@gmail.com">gccfof5@gmail.com</a>> wrote:<br>
>><br>
>> Shift in focus to the hardware side of the equation. This thread<br>
>> concentrates on software generated corruption issues, but I have some<br>
>> hardware related questions. First, with RAIDed hard drives, are any
file<br>
>> systems more or less likely to cause (or minimize) the likelihood of<br>
>> corruption of the array and if so, why? Second Greg F (and others)
have<br>
>> commented on NOT using RAID 5 (and RAID 6) esp. with large hard
drives.<br>
>> Looks like 1 or 2 TB hard drives will soon be "standard
issue" for<br>
>> everything but notebook computers. So does that mean that RAID should
be<br>
>> considered 'dead,' except for 0, 1, 10? Third, would SSDs solve the
failure<br>
>> from bad sector issues with HDDs and thus be safe for RAID 5/6<br>
>> implementations?<br>
>><br>
>><br>
>> On Thu, Apr 22, 2010 at 9:41 AM, Ed Cashin <<a
href="mailto:ecashin@noserose.net">ecashin@noserose.net</a>> wrote:<br>
>>><br>
>>> On Wed, Apr 21, 2010 at 9:34 PM, Doug McNash <<a
href="mailto:dmcnash@charter.net">dmcnash@charter.net</a>> wrote:<br>
>>> ...<br>
>>> > Does anyone out there use xfs? How about a suggestion for a
stable<br>
>>> > replacement.<br>
>>><br>
>>> If you use the xfs in the mainline kernel, it's a crap shoot
because<br>
>>> of the amount of churn in the code, but<br>
>>> if you use a long-term kernel like 2.6.16.y, 2.6.27.y, or the
kernels<br>
>>> maintained by distros, then it ought to be stable (as long as the<br>
>>> distro has enough of a user base for other people to find the xfs<br>
>>> bugs first).<br>
>>><br>
>>> --<br>
>>> Ed Cashin <<a href="mailto:ecashin@noserose.net">ecashin@noserose.net</a>><br>
>>> <a href="http://noserose.net/e/" target="_blank">http://noserose.net/e/</a><br>
>>> <a href="http://www.coraid.com/" target="_blank">http://www.coraid.com/</a><br>
>>> _______________________________________________<br>
>>> Ale mailing list<br>
>>> <a href="mailto:Ale@ale.org">Ale@ale.org</a><br>
>>> <a href="http://mail.ale.org/mailman/listinfo/ale" target="_blank">http://mail.ale.org/mailman/listinfo/ale</a><br>
>>> See JOBS, ANNOUNCE and SCHOOLS lists at<br>
>>> <a href="http://mail.ale.org/mailman/listinfo" target="_blank">http://mail.ale.org/mailman/listinfo</a><br>
>><br>
>><br>
>> _______________________________________________<br>
>> Ale mailing list<br>
>> <a href="mailto:Ale@ale.org">Ale@ale.org</a><br>
>> <a href="http://mail.ale.org/mailman/listinfo/ale" target="_blank">http://mail.ale.org/mailman/listinfo/ale</a><br>
>> See JOBS, ANNOUNCE and SCHOOLS lists at<br>
>> <a href="http://mail.ale.org/mailman/listinfo" target="_blank">http://mail.ale.org/mailman/listinfo</a><br>
>><br>
><br>
><br>
><br>
> --<br>
> --<br>
> James P. Kinney III<br>
> Actively in pursuit of Life, <st1:City w:st="on"><st1:place w:st="on">Liberty</st1:place></st1:City>
and Happiness<br>
><br>
><br>
> _______________________________________________<br>
> Ale mailing list<br>
> <a href="mailto:Ale@ale.org">Ale@ale.org</a><br>
> <a href="http://mail.ale.org/mailman/listinfo/ale" target="_blank">http://mail.ale.org/mailman/listinfo/ale</a><br>
> See JOBS, ANNOUNCE and SCHOOLS lists at<br>
> <a href="http://mail.ale.org/mailman/listinfo" target="_blank">http://mail.ale.org/mailman/listinfo</a><br>
><br>
><br>
<br>
<br>
<o:p></o:p></span></font></p>
</div>
</div>
<p class=MsoNormal><font size=3 face="Times New Roman"><span style='font-size:
12.0pt'>--<o:p></o:p></span></font></p>
<div>
<p class=MsoNormal><font size=3 face="Times New Roman"><span style='font-size:
12.0pt'>Greg Freemyer<br>
Head of EDD Tape Extraction and Processing team<br>
Litigation Triage Solutions Specialist<br>
<a href="http://www.linkedin.com/in/gregfreemyer" target="_blank">http://www.linkedin.com/in/gregfreemyer</a><br>
CNN/TruTV Aired Forensic Imaging Demo -<br>
<a
href="http://insession.blogs.cnn.com/2010/03/23/how-computer-evidence-gets-retrieved/"
target="_blank">http://insession.blogs.cnn.com/2010/03/23/how-computer-evidence-gets-retrieved/</a><br>
<br>
The Norcross Group<br>
The Intersection of Evidence & Technology<o:p></o:p></span></font></p>
</div>
<p class=MsoNormal><font size=3 face="Times New Roman"><span style='font-size:
12.0pt'><a href="http://www.norcrossgroup.com" target="_blank">http://www.norcrossgroup.com</a><o:p></o:p></span></font></p>
<div>
<div>
<p class=MsoNormal><font size=3 face="Times New Roman"><span style='font-size:
12.0pt'><br>
_______________________________________________<br>
Ale mailing list<br>
<a href="mailto:Ale@ale.org">Ale@ale.org</a><br>
<a href="http://mail.ale.org/mailman/listinfo/ale" target="_blank">http://mail.ale.org/mailman/listinfo/ale</a><br>
See JOBS, ANNOUNCE and SCHOOLS lists at<br>
<a href="http://mail.ale.org/mailman/listinfo" target="_blank">http://mail.ale.org/mailman/listinfo</a><o:p></o:p></span></font></p>
</div>
</div>
</div>
<p class=MsoNormal><font size=3 face="Times New Roman"><span style='font-size:
12.0pt'><br>
<br>
<o:p></o:p></span></font></p>
<input id=gwProxy type=hidden>
<input id=jsProxy type=hidden onclick="jsCall();">
</div>
</DIV>
<DIV> </DIV>
<DIV>
<FONT FACE="Arial" SIZE="2">Proud partner. Susan G. Komen for the Cure.</FONT>
</DIV>
<DIV> </DIV>
<DIV>
<FONT FACE="Arial" COLOR="green" SIZE="1"><EM>Please consider our environment before printing this e-mail or attachments.</EM></FONT>
</DIV>
<DIV STYLE="FONT-SIZE: 9pt; FONT-FAMILY: Courier New">
<FONT FACE="Arial" SIZE="2">----------------------------------<BR>CONFIDENTIALITY NOTICE: This e-mail may contain privileged or confidential information and is for the sole use of the intended recipient(s). If you are not the intended recipient, any disclosure, copying, distribution, or use of the contents of this information is prohibited and may be unlawful. If you have received this electronic transmission in error, please reply immediately to the sender that you have received the message in error, and delete it. Thank you.<BR>----------------------------------<BR></FONT>
</DIV></BODY></HTML>