From: Werner Fischer <devlists@wefi.net>
To: Tom De Mulder <tdm27@cam.ac.uk>
Cc: linux-raid@vger.kernel.org
Subject: Re: Software RAID and TRIM
Date: Mon, 04 Jul 2011 18:26:52 +0200 [thread overview]
Message-ID: <1309796812.2046.13.camel@werner-t410> (raw)
In-Reply-To: <alpine.OSX.2.00.1107041011110.4557@trogdor.csi.cam.ac.uk>
Hi Tom,
1) regarding Software RAID and TRIM:
there is a script raid1ext4trim.sh-1.4 from Chris Caputo that does a
TRIM for Ext4 file systems on a software RAID 1. According to the
comments in the script it only supports RAID volumes which reside on
complete disks (e.g. /dev/sdb and /dev/sdc), not on RAID partitions
(e.g. /dev/sdb1 and /dev/sdc1)
The script is shipped with hdparm, get hdparm 9.37 at
http://sourceforge.net/projects/hdparm/ and you'll find the script in
the subfolder hdparm-9.37/wiper/contrib/
I have not tested the script yet, maybe I could do some tests tomorrow
2) regarding choosing the right SSD:
I would strongly recommend a SSD with integrated power-outage
protection, Intel's 320 series has this inside:
http://newsroom.intel.com/servlet/JiveServlet/download/38-4324/Intel_SSD_320_Series_Enhance_Power_Loss_Technology_Brief.pdf
I have done some power-outage tests today, including a Vertex-3 and an
Intel 320 series. I used diskchecker.pl from
http://brad.livejournal.com/2116715.html
result:
-> for the Vertex 3 diskchecker.pl reported lost data:
[root@f15-ocz-vertex3 ~]# ./diskchecker.pl -s 10.10.30.199 verify testfile2
verifying: 0.00%
verifying: 1.42%
Error at page 52141, 0 seconds before end.
verifying: 6.31%
Error at page 83344, 0 seconds before end.
verifying: 11.12%
Error at page 163555, 0 seconds before end.
[...]
Total errors: 12
Histogram of seconds before end:
0 12
[root@f15-ocz-vertex3 ~]#
-> for the Intel 320 Series diskchecker.pl did not report data loss:
[root@f15-intel-320 ~]# ./diskchecker.pl -s 10.10.30.199 verify
testfile2
verifying: 0.00%
verifying: 0.12%
[...]
verifying: 99.82%
verifying: 100.00%
Total errors: 0
[root@f15-intel-320 ~]#
I did the tests multiple times, I had also some runs on the Vertex 3
without errors, but with the Intel 320 Series no single test reported an
error.
I did the tests with fedora 15 on the SSDs, here are the details of
hdparm -I
OCZ Vertex 3:
Model Number: OCZ-VERTEX3
Serial Number: OCZ-OQZF2I45DYZ47T3C
Firmware Revision: 2.06
Transport: Serial, ATA8-AST, SATA 1.0a, SATA II Extensions, SATA Rev 2.5, SATA Rev 2.6, SATA Rev 3.0
[...]
device size with M = 1000*1000: 120034 MBytes (120 GB)
Intel 320 Series:
Model Number: INTEL SSDSA2CW160G3
Serial Number: CVPR112601AL160DGN
Firmware Revision: 4PC10302
Transport: Serial, ATA8-AST, SATA 1.0a, SATA II Extensions, SATA Rev 2.5, SATA Rev 2.6
[...]
device size with M = 1000*1000: 160041 MBytes (160 GB)
Regards,
Werner
On Mon, 2011-07-04 at 10:13 +0100, Tom De Mulder wrote:
> On Thu, 30 Jun 2011, Mikael Abrahamsson wrote:
>
> > From the tests I have read, the Intel 510 are actually worse than the Intel
> > X-25 G1/G2/320 models, with exactly the symptoms you're describing. It's fast
> > for linear reads and writes, but not so good for random writes, especially not
> > when it's getting full.
>
> Yes; that's why I'm looking forward to also getting some SandForce 22xx
> based drives (probably OCZ Vertex 3) to test.
>
> > Include the Intel 320 as well, I think it should be viable for your usage
> > pattern.
>
> I wasn't too impressed by the Anandtech review of the 320, and (as
> everywhere) my funds are limited. :-)
>
>
> --
> Tom De Mulder <tdm27@cam.ac.uk> - Cambridge University Computing Service
> +44 1223 3 31843 - New Museums Site, Pembroke Street, Cambridge CB2 3QH
> -> 04/07/2011 : The Moon is Waxing Crescent (17% of Full)
> --
> To unsubscribe from this list: send the line "unsubscribe linux-raid" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2011-07-04 16:26 UTC|newest]
Thread overview: 45+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-06-28 15:31 Software RAID and TRIM Tom De Mulder
2011-06-28 16:11 ` Mathias Burén
2011-06-29 10:32 ` Tom De Mulder
2011-06-29 10:45 ` NeilBrown
2011-06-29 11:10 ` Tom De Mulder
2011-06-29 11:48 ` Scott E. Armitage
2011-06-29 12:46 ` Roberto Spadim
2011-06-29 12:46 ` David Brown
2011-06-30 0:28 ` NeilBrown
2011-06-30 7:50 ` David Brown
2011-06-29 13:39 ` Namhyung Kim
2011-06-30 0:27 ` NeilBrown
2011-07-17 22:11 ` Lutz Vieweg
2011-07-17 21:57 ` Lutz Vieweg
2011-06-29 10:33 ` Tom De Mulder
2011-06-29 12:42 ` David Brown
2011-06-29 12:55 ` Tom De Mulder
2011-06-29 13:02 ` Roberto Spadim
2011-06-29 13:10 ` David Brown
2011-06-30 5:51 ` Mikael Abrahamsson
2011-07-04 9:13 ` Tom De Mulder
2011-07-04 16:26 ` Werner Fischer [this message]
2011-07-17 22:31 ` Lutz Vieweg
2011-07-17 22:16 ` Lutz Vieweg
2011-07-17 22:00 ` Lutz Vieweg
2011-06-28 16:17 ` Johannes Truschnigg
2011-06-28 16:40 ` David Brown
2011-07-17 21:52 ` Lutz Vieweg
2011-07-18 5:14 ` Mikael Abrahamsson
2011-07-18 10:35 ` David Brown
2011-07-18 10:48 ` Tom De Mulder
2011-07-18 18:09 ` Lutz Vieweg
2011-07-18 20:18 ` David Brown
2011-07-19 9:29 ` Lutz Vieweg
2011-07-19 10:22 ` David Brown
2011-07-19 13:41 ` Lutz Vieweg
2011-07-19 15:06 ` David Brown
2011-07-20 10:39 ` Lutz Vieweg
2011-07-19 14:19 ` Tom De Mulder
2011-07-20 7:42 ` David Brown
2011-07-20 12:20 ` Lutz Vieweg
2011-07-20 12:13 ` Werner Fischer
2011-07-20 12:25 ` Lutz Vieweg
2011-07-18 10:53 ` Tom De Mulder
2011-07-18 12:13 ` Werner Fischer
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1309796812.2046.13.camel@werner-t410 \
--to=devlists@wefi.net \
--cc=linux-raid@vger.kernel.org \
--cc=tdm27@cam.ac.uk \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).