standard performance (write speed 20Mb/s)

Hi folks :-)

after assembled a new hw (xeon, ich10 controller with 5 disks of 2Tb wd -
radi5) I have slow write performance:

20Mb/s :-(((

dd if=/dev/zero of=/share/raid/1Gb bs=1024M count=1
1+0 records in
1+0 records out
1073741824 bytes (1.1 GB) copied, 48.7203 s, 22.0 MB/s

I repeated same test also creating a 10Gb file.. same results..

write speed is better:

dd if=/share/raid/1Gb of=/dev/null
2097152+0 records in
2097152+0 records out
1073741824 bytes (1.1 GB) copied, 1.82054 s, 590 MB/s

20Mb/s is a disk/controller problem or controller can't do better?

hw is new, I already check all disks..

thanks!

Pol
--
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

Re: standard performance (write speed 20Mb/s)

On 7/16/2011 2:40 PM, Pol Hallen wrote:
> Hi folks :-)
>
> after assembled a new hw (xeon, ich10 controller with 5 disks of 2Tb wd -
> radi5) I have slow write performance:
>
> 20Mb/s :-(((
>
> dd if=/dev/zero of=/share/raid/1Gb bs=1024M count=1
> 1+0 records in
> 1+0 records out
> 1073741824 bytes (1.1 GB) copied, 48.7203 s, 22.0 MB/s

Using a write block size of 1GB with dd causes the entire file to be
buffered to RAM before being flushed to disk. To prove the point, I
just ran your test against a single SATA disk with an XFS filesystem.
XFS is is optimized for large files.

$ dd if=/dev/zero of=./test bs=1024M count=1
1+0 records in
1+0 records out
1073741824 bytes (1.1 GB) copied, 139.895 s, 7.7 MB/s

The same test using a *sane* block size of 4KB:

$ dd if=/dev/zero of=./test bs=4096 count=262144
262144+0 records in
262144+0 records out
1073741824 bytes (1.1 GB) copied, 15.0732 s, 71.2 MB/s

10x decrease in performance due to the insane 1GB block size.

The machine I ran this test on is old, having only 384MB RAM and a
Sil3512 PCI SATA-I controller. The disk is a WD Blue 500GB 7.2K. Using
the 1GB block size ate over 800MB of swap out of 1GB before the buffer
was flushed. This massive buffering is what murders performance here.
Repeat your test using a 4KB block size and post the results.

Know your tools Pol.

--
Stan
--
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

Re: standard performance (write speed 20Mb/s)

hello and thanks for the reply :-)

dd if=/dev/zero of=test bs=4096 count=262144
262144+0 records in
262144+0 records out
1073741824 bytes (1.1 GB) copied, 31.3475 s, 34.3 MB/s

I've 8Gb ddr3 of ram

Pol

--
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

Re: standard performance (write speed 20Mb/s)

On 17/07/2011 09:12, Pol Hallen wrote:
> hello and thanks for the reply :-)
>
> dd if=/dev/zero of=test bs=4096 count=262144
> 262144+0 records in
> 262144+0 records out
> 1073741824 bytes (1.1 GB) copied, 31.3475 s, 34.3 MB/s

Pretty poor. CentOS 5, Intel ICH10, md RAID 6 over 5 7200rpm 1TB drives,
then LVM, then ext3:
# dd if=/dev/zero of=test bs=4096 count=262144
262144+0 records in
262144+0 records out
1073741824 bytes (1.1 GB) copied, 2.5253 seconds, 425 MB/s

And there's a badblocks running on another drive also on the ICH10.

Having said that, I think mine's wrong too, I don't think my array can
really manage that much throughput. We should both be using more
realistic benchmarking tools like bonnie++:

Version 1.03 ------Sequential Output------ --Sequential Input-
--Random-
-Per Chr- --Block-- -Rewrite- -Per Chr- --Block--
--Seeks--
Machine Size K/sec %CP K/sec %CP K/sec %CP K/sec %CP K/sec %CP
/sec %CP
beast.private.yu 7G 80890 91 67527 13 41608 4 74028 69 205104 9
378.7 0
------Sequential Create------ --------Random
Create--------
-Create-- --Read--- -Delete-- -Create-- --Read---
-Delete--
files /sec %CP /sec %CP /sec %CP /sec %CP /sec %CP
/sec %CP
16 +++++ +++ +++++ +++ +++++ +++ +++++ +++ +++++ +++
+++++ +++
beast.private.yuiop.co.uk,7G,80890,91,67527,13,41608,4,74028 ,69,205104,9,378.7,0,16,+++++,+++,+++++,+++,+++++,+++,+++++, +++,+++++,+++,+++++,+++

And I should think of a command line options so I don't get all those +
signs. Never mind, the above shows 40-80MB/s for writes, 70-200MB/s for
reads, which is not too bad even if it's not great.

Hang on. You aren't trying to benchmark your array just after creating
it, while it's still doing its initial sync, are you?

Cheers,

John.

--
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

Re: standard performance (write speed 20Mb/s)

On Sun, Jul 17, 2011 at 01:11:19PM +0100, John Robinson wrote:
> On 17/07/2011 09:12, Pol Hallen wrote:
> >hello and thanks for the reply :-)
> >
> >dd if=3D/dev/zero of=3Dtest bs=3D4096 count=3D262144
> >262144+0 records in
> >262144+0 records out
> >1073741824 bytes (1.1 GB) copied, 31.3475 s, 34.3 MB/s
>=20
> Pretty poor. CentOS 5, Intel ICH10, md RAID 6 over 5 7200rpm 1TB
> drives, then LVM, then ext3:
> # dd if=3D/dev/zero of=3Dtest bs=3D4096 count=3D262144
> 262144+0 records in
> 262144+0 records out
> 1073741824 bytes (1.1 GB) copied, 2.5253 seconds, 425 MB/s
>=20
> And there's a badblocks running on another drive also on the ICH10.
>=20
> Having said that, I think mine's wrong too, I don't think my array
> can really manage that much throughput. We should both be using more
> realistic benchmarking tools like bonnie++:

Or simply pass the correct flags to dd â€=94 like oflag=3Ddirect, w=
hich will
make it do non-buffered writes.

regards,
iustin
--
To unsubscribe from this list: send the line "unsubscribe linux-raid" i=
n
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html

Re: standard performance (write speed 20Mb/s)

On 17/07/2011 13:22, Iustin Pop wrote:
> On Sun, Jul 17, 2011 at 01:11:19PM +0100, John Robinson wrote:
[...]
>> # dd if=3D/dev/zero of=3Dtest bs=3D4096 count=3D262144
>> 262144+0 records in
>> 262144+0 records out
>> 1073741824 bytes (1.1 GB) copied, 2.5253 seconds, 425 MB/s
>>
>> And there's a badblocks running on another drive also on the ICH10.
>>
>> Having said that, I think mine's wrong too, I don't think my array
>> can really manage that much throughput. We should both be using more
>> realistic benchmarking tools like bonnie++:
>
> Or simply pass the correct flags to dd â€=94 like oflag=3Ddirect,=
which will
> make it do non-buffered writes.

That's still not realistic:

# dd if=3D/dev/zero of=3Dtest oflag=3Ddirect bs=3D4096 count=3D262144
262144+0 records in
262144+0 records out
1073741824 bytes (1.1 GB) copied, 117.434 seconds, 9.1 MB/s

Because this time we're doing a read-modify-write for every 4K block, o=
r=20
at least a write for every 4K block. I can fix it up again to work in=20
stripe size amounts:

# dd if=3D/dev/zero of=3Dtest oflag=3Ddirect bs=3D1572864 count=3D683
683+0 records in
683+0 records out
1074266112 bytes (1.1 GB) copied, 18.3198 seconds, 58.6 MB/s

But it's still not realistic because real I/O does use buffers and=20
doesn't work in magic sizes, so we should be using a more realistic=20
benchmarking tool like bonnie++.

Cheers,

John.

--
To unsubscribe from this list: send the line "unsubscribe linux-raid" i=
n
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html

Re: standard performance (write speed 20Mb/s)

On Sun, Jul 17, 2011 at 01:51:11PM +0100, John Robinson wrote:
> On 17/07/2011 13:22, Iustin Pop wrote:
> >On Sun, Jul 17, 2011 at 01:11:19PM +0100, John Robinson wrote:
> [...]
> >># dd if=3D/dev/zero of=3Dtest bs=3D4096 count=3D262144
> >>262144+0 records in
> >>262144+0 records out
> >>1073741824 bytes (1.1 GB) copied, 2.5253 seconds, 425 MB/s
> >>
> >>And there's a badblocks running on another drive also on the ICH10.
> >>
> >>Having said that, I think mine's wrong too, I don't think my array
> >>can really manage that much throughput. We should both be using mor=
e
> >>realistic benchmarking tools like bonnie++:
> >
> >Or simply pass the correct flags to dd â€=94 like oflag=3Ddirect=
, which will
> >make it do non-buffered writes.
>=20
> That's still not realistic:
>=20
> # dd if=3D/dev/zero of=3Dtest oflag=3Ddirect bs=3D4096 count=3D262144
> 262144+0 records in
> 262144+0 records out
> 1073741824 bytes (1.1 GB) copied, 117.434 seconds, 9.1 MB/s
>=20
> Because this time we're doing a read-modify-write for every 4K
> block, or at least a write for every 4K block.

Of course :)

But at 4K speed, this is actually the speed of your array.

> I can fix it up again
> to work in stripe size amounts:
>=20
> # dd if=3D/dev/zero of=3Dtest oflag=3Ddirect bs=3D1572864 count=3D683
> 683+0 records in
> 683+0 records out
> 1074266112 bytes (1.1 GB) copied, 18.3198 seconds, 58.6 MB/s
>=20
> But it's still not realistic because real I/O does use buffers and

Buffers is one thing; flushing to disk after a certain block size
another, and that happens quite often, depending on workload.

> doesn't work in magic sizes, so we should be using a more realistic
> benchmarking tool like bonnie++.

Honestly, I don't find bonnie++ a realistic tool. fio is a much better
one; bonnie is quite old and inflexible.

regards,
iustin
--
To unsubscribe from this list: send the line "unsubscribe linux-raid" i=
n
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html

Re: standard performance (write speed 20Mb/s)

On Sat, 16 Jul 2011, Pol Hallen wrote:

> Hi folks :-)
>
> after assembled a new hw (xeon, ich10 controller with 5 disks of 2Tb wd -
> radi5) I have slow write performance:
>
> 20Mb/s :-(((

In addition to the other comments so-far, are these drives WDC EARS
drives?

What's the output of

hdparm -i /dev/sda

If it's something like

Model=WDC WD20EARS-00MVWB0, FwRev=50.0AB50, SerialNo=WD-WMAZ20098633
^^^^

then it has 4KB sectors.

If so, then you'll have to make absolutely sure the partitions are aligned
on a 4KB boundary.

What does the output of

sfdisk -d /dev/sda

look like? (where /dev/sda is one of the disks on your array)

The start of each partition ought to be divisible by 64 evenly for optimal
results.

Gordon
--
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

Re: standard performance (write speed 20Mb/s)

On 7/17/2011 7:22 AM, Iustin Pop wrote:
> On Sun, Jul 17, 2011 at 01:11:19PM +0100, John Robinson wrote:
>> On 17/07/2011 09:12, Pol Hallen wrote:
>>> hello and thanks for the reply :-)
>>>
>>> dd if=3D/dev/zero of=3Dtest bs=3D4096 count=3D262144
>>> 262144+0 records in
>>> 262144+0 records out
>>> 1073741824 bytes (1.1 GB) copied, 31.3475 s, 34.3 MB/s
>>
>> Pretty poor. CentOS 5, Intel ICH10, md RAID 6 over 5 7200rpm 1TB
>> drives, then LVM, then ext3:
>> # dd if=3D/dev/zero of=3Dtest bs=3D4096 count=3D262144
>> 262144+0 records in
>> 262144+0 records out
>> 1073741824 bytes (1.1 GB) copied, 2.5253 seconds, 425 MB/s
>>
>> And there's a badblocks running on another drive also on the ICH10.
>>
>> Having said that, I think mine's wrong too, I don't think my array
>> can really manage that much throughput. We should both be using more
>> realistic benchmarking tools like bonnie++:
>=20
> Or simply pass the correct flags to dd â€=94 like oflag=3Ddirect,=
which will
> make it do non-buffered writes.

I'm not sure of the reasons, but O_DIRECT doesn't work with dd quite th=
e
way one would think, at least not from a performance perspective. On m=
y
test rig it yields an almost 10x decrease, much like using insane block
size. It may have something to do with write barriers being enabled in
XFS on my test rig, or something similar. This system is running
vanilla 2.6.38.6 with Debian Squeeze atop. Using O_DIRECT with dd with
2.6.26 and 2.6.34 yielded the same dd O_DIRECT behavior in the past.

$ dd if=3D/dev/zero of=3D./test bs=3D4096 count=3D262144
262144+0 records in
262144+0 records out
1073741824 bytes (1.1 GB) copied, 15.0542 s, 71.3 MB/s

$ dd oflag=3Ddirect if=3D/dev/zero of=3D./test bs=3D4096 count=3D262144
262144+0 records in
262144+0 records out
1073741824 bytes (1.1 GB) copied, 133.888 s, 8.0 MB/s

--=20
Stan
--
To unsubscribe from this list: send the line "unsubscribe linux-raid" i=
n
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html

Re: standard performance (write speed 20Mb/s)

On 7/17/2011 3:12 AM, Pol Hallen wrote:
> hello and thanks for the reply :-)
>
> dd if=/dev/zero of=test bs=4096 count=262144
> 262144+0 records in
> 262144+0 records out
> 1073741824 bytes (1.1 GB) copied, 31.3475 s, 34.3 MB/s
>
> I've 8Gb ddr3 of ram

Then you have multiple problems causing poor performance. Now is the
time for you to post your hardware configuration, drive model
number(s), mdadm config, and filesystem. You should have done all of
this in your initial post.

You've been on this list long enough to have known of the WD Green
sector alignment issue and avoided it, and to know better than to run
performance tests while an array is still in its initial sync. Thus I
initially assumed your problem was merely the insane dd block size.

--
Stan
--
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

Re: standard performance (write speed 20Mb/s)

On 17/07/2011 14:28, Iustin Pop wrote:
> On Sun, Jul 17, 2011 at 01:51:11PM +0100, John Robinson wrote:
[...]
>> doesn't work in magic sizes, so we should be using a more realistic
>> benchmarking tool like bonnie++.
>
> Honestly, I don't find bonnie++ a realistic tool. fio is a much better
> one; bonnie is quite old and inflexible.

Ah OK, yes I agree with you there, but my general point remains: dd
might be OK for producing one very specific metric in some cases, but
that will not give a realistic impression of real use performance, so we
should be using a more realistic benchmarking tool.

Cheers,

John.
--
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

Re: standard performance (write speed 20Mb/s)

--Boundary-00=_b6BJOwgYP3vEmKe
Content-Type: Text/Plain;
charset="iso-8859-1"
Content-Transfer-Encoding: 7bit

> Then you have multiple problems causing poor performance. Now is the
> time for you to post your hardware configuration, drive model
> number(s), mdadm config, and filesystem. You should have done all of
> this in your initial post.

hello and sorry for the late :-(

now is a resync in progress, I can't stop it. Try /usr/share/mdadm/checkarray
-x md0 but nothing..

fs is ext3 (done less 10 days ago)

> You've been on this list long enough to have known of the WD Green
> sector alignment issue and avoided it, and to know better than to run
> performance tests while an array is still in its initial sync. Thus I
> initially assumed your problem was merely the insane dd block size.

when I wrote a post there was not resync in progress..

tell me if you need known other things, thanks

Pol

--Boundary-00=_b6BJOwgYP3vEmKe
Content-Type: text/plain;
charset="UTF-8";
name="mdadm.conf"
Content-Transfer-Encoding: 7bit
Content-Disposition: attachment;
filename="mdadm.conf"

# mdadm.conf
#
# Please refer to mdadm.conf(5) for information about this file.
#

# by default, scan all partitions (/proc/partitions) for MD superblocks.
# alternatively, specify devices to scan, using wildcards if desired.
DEVICE partitions

# auto-create devices with Debian standard permissions
CREATE owner=root group=disk mode=0660 auto=yes

# automatically tag new arrays as belonging to the local system
HOMEHOST

# instruct the monitoring daemon where to send mail alerts
MAILADDR pol@yahoo.it

# definitions of existing MD arrays

# This file was auto-generated on Fri, 08 Jul 2011 14:37:51 -0700
# by mkconf 3.1.4-1+8efb9d1


--Boundary-00=_b6BJOwgYP3vEmKe
Content-Type: text/plain;
charset="UTF-8";
name="sdb"
Content-Transfer-Encoding: 7bit
Content-Disposition: attachment;
filename="sdb"

smartctl 5.40 2010-07-12 r3124 [i686-pc-linux-gnu] (local build)
Copyright (C) 2002-10 by Bruce Allen, http://smartmontools.sourceforge.net

=== START OF INFORMATION SECTION ===
Model Family: Seagate Barracuda 7200.11 family
Device Model: ST31500341AS
Serial Number: 9VS4PSG9
Firmware Version: CC1H
User Capacity: 1,500,301,910,016 bytes
Device is: In smartctl database [for details use: -P show]
ATA Version is: 8
ATA Standard is: ATA-8-ACS revision 4
Local Time is: Mon Jul 18 13:44:52 2011 CEST
SMART support is: Available - device has SMART capability.
SMART support is: Enabled


--Boundary-00=_b6BJOwgYP3vEmKe
Content-Type: text/plain;
charset="UTF-8";
name="mdadm-d"
Content-Transfer-Encoding: 7bit
Content-Disposition: attachment;
filename="mdadm-d"

/dev/md0:
Version : 1.2
Creation Time : Fri Jul 8 23:52:13 2011
Raid Level : raid5
Array Size : 5860538368 (5589.05 GiB 6001.19 GB)
Used Dev Size : 1465134592 (1397.26 GiB 1500.30 GB)
Raid Devices : 5
Total Devices : 5
Persistence : Superblock is persistent

Update Time : Mon Jul 18 13:14:04 2011
State : active, resyncing
Active Devices : 5
Working Devices : 5
Failed Devices : 0
Spare Devices : 0

Layout : left-symmetric
Chunk Size : 512K

Rebuild Status : 33% complete

Name : smooth:0 (local to host smooth)
UUID : bfca3ad6:a7df5fa5:20ba4933:55fd4181
Events : 6212

Number Major Minor RaidDevice State
0 8 64 0 active sync /dev/sde
1 8 97 1 active sync /dev/sdg1
2 8 113 2 active sync /dev/sdh1
3 8 129 3 active sync /dev/sdi1
5 8 81 4 active sync /dev/sdf1

--Boundary-00=_b6BJOwgYP3vEmKe
Content-Type: text/plain;
charset="UTF-8";
name="sdc"
Content-Transfer-Encoding: 7bit
Content-Disposition: attachment;
filename="sdc"

smartctl 5.40 2010-07-12 r3124 [i686-pc-linux-gnu] (local build)
Copyright (C) 2002-10 by Bruce Allen, http://smartmontools.sourceforge.net

=== START OF INFORMATION SECTION ===
Model Family: Seagate Barracuda 7200.11 family
Device Model: ST31500341AS
Serial Number: 9VS3KL49
Firmware Version: CC1H
User Capacity: 1,500,301,910,016 bytes
Device is: In smartctl database [for details use: -P show]
ATA Version is: 8
ATA Standard is: ATA-8-ACS revision 4
Local Time is: Mon Jul 18 13:45:00 2011 CEST
SMART support is: Available - device has SMART capability.
SMART support is: Enabled


--Boundary-00=_b6BJOwgYP3vEmKe
Content-Type: text/plain;
charset="UTF-8";
name="lspci"
Content-Transfer-Encoding: 7bit
Content-Disposition: attachment;
filename="lspci"

00:00.0 Host bridge: Intel Corporation 5520 I/O Hub to ESI Port (rev 22)
Subsystem: Super Micro Computer Inc Device a880
Flags: fast devsel
Capabilities: [60] MSI: Enable- Count=1/2 Maskable+ 64bit-
Capabilities: [90] Express Root Port (Slot-), MSI 00
Capabilities: [e0] Power Management version 3
Capabilities: [100] Advanced Error Reporting
Capabilities: [150] Access Control Services
Capabilities: [160] Vendor Specific Information: ID=0002 Rev=0 Len=00c

00:01.0 PCI bridge: Intel Corporation 5520/5500/X58 I/O Hub PCI Express Root Port 1 (rev 22) (prog-if 00 [Normal decode])
Flags: bus master, fast devsel, latency 0
Bus: primary=00, secondary=07, subordinate=07, sec-latency=0
Capabilities: [40] Subsystem: Super Micro Computer Inc Device a880
Capabilities: [60] MSI: Enable+ Count=1/2 Maskable+ 64bit-
Capabilities: [90] Express Root Port (Slot+), MSI 00
Capabilities: [e0] Power Management version 3
Capabilities: [100] Advanced Error Reporting
Capabilities: [150] Access Control Services
Capabilities: [160] Vendor Specific Information: ID=0002 Rev=0 Len=00c
Kernel driver in use: pcieport

00:03.0 PCI bridge: Intel Corporation 5520/5500/X58 I/O Hub PCI Express Root Port 3 (rev 22) (prog-if 00 [Normal decode])
Flags: bus master, fast devsel, latency 0
Bus: primary=00, secondary=06, subordinate=06, sec-latency=0
I/O behind bridge: 0000e000-0000efff
Memory behind bridge: faf00000-faffffff
Prefetchable memory behind bridge: 00000000d8000000-00000000dfffffff
Capabilities: [40] Subsystem: Super Micro Computer Inc Device a880
Capabilities: [60] MSI: Enable+ Count=1/2 Maskable+ 64bit-
Capabilities: [90] Express Root Port (Slot+), MSI 00
Capabilities: [e0] Power Management version 3
Capabilities: [100] Advanced Error Reporting
Capabilities: [150] Access Control Services
Capabilities: [160] Vendor Specific Information: ID=0002 Rev=0 Len=00c
Kernel driver in use: pcieport

00:07.0 PCI bridge: Intel Corporation 5520/5500/X58 I/O Hub PCI Express Root Port 7 (rev 22) (prog-if 00 [Normal decode])
Flags: bus master, fast devsel, latency 0
Bus: primary=00, secondary=05, subordinate=05, sec-latency=0
Capabilities: [40] Subsystem: Super Micro Computer Inc Device a880
Capabilities: [60] MSI: Enable+ Count=1/2 Maskable+ 64bit-
Capabilities: [90] Express Root Port (Slot+), MSI 00
Capabilities: [e0] Power Management version 3
Capabilities: [100] Advanced Error Reporting
Capabilities: [150] Access Control Services
Capabilities: [160] Vendor Specific Information: ID=0002 Rev=0 Len=00c
Kernel driver in use: pcieport

00:0e.0 Host bridge: Intel Corporation Device 341c (rev 22)
Flags: fast devsel
Capabilities: [40] Express Root Complex Integrated Endpoint, MSI 00
Capabilities: [60] #00 [0000]
Capabilities: [100] Vendor Specific Information: ID=0001 Rev=0 Len=0b8

00:0e.1 Host bridge: Intel Corporation Device 341d (rev 22)
Flags: fast devsel
Capabilities: [40] Express Root Complex Integrated Endpoint, MSI 00
Capabilities: [60] #00 [0000]

00:0e.2 Host bridge: Intel Corporation Device 341e (rev 22)
Flags: fast devsel
Capabilities: [40] Express Root Complex Integrated Endpoint, MSI 00
Capabilities: [60] #00 [0000]

00:13.0 PIC: Intel Corporation 5520/5500/X58 I/O Hub I/OxAPIC Interrupt Controller (rev 22) (prog-if 20 [IO(X)-APIC])
Flags: bus master, fast devsel, latency 0
Memory at fec8a000 (32-bit, non-prefetchable) [size=4K]
Capabilities: [6c] Power Management version 3

00:14.0 PIC: Intel Corporation 5520/5500/X58 I/O Hub System Management Registers (rev 22) (prog-if 00 [8259])
Flags: fast devsel
Capabilities: [40] Express Root Complex Integrated Endpoint, MSI 00

00:14.1 PIC: Intel Corporation 5520/5500/X58 I/O Hub GPIO and Scratch Pad Registers (rev 22) (prog-if 00 [8259])
Flags: fast devsel
Capabilities: [40] Express Root Complex Integrated Endpoint, MSI 00

00:14.2 PIC: Intel Corporation 5520/5500/X58 I/O Hub Control Status and RAS Registers (rev 22) (prog-if 00 [8259])
Flags: fast devsel
Capabilities: [40] Express Root Complex Integrated Endpoint, MSI 00

00:14.3 PIC: Intel Corporation 5520/5500/X58 I/O Hub Throttle Registers (rev 22) (prog-if 00 [8259])
Flags: fast devsel

00:16.0 System peripheral: Intel Corporation 5520/5500/X58 Chipset QuickData Technology Device (rev 22)
Subsystem: Super Micro Computer Inc Device a880
Flags: bus master, fast devsel, latency 0, IRQ 43
Memory at faaec000 (64-bit, non-prefetchable) [size=16K]
Capabilities: [80] MSI-X: Enable+ Count=1 Masked-
Capabilities: [90] Express Root Complex Integrated Endpoint, MSI 00
Capabilities: [e0] Power Management version 3
Kernel driver in use: ioatdma

00:16.1 System peripheral: Intel Corporation 5520/5500/X58 Chipset QuickData Technology Device (rev 22)
Subsystem: Super Micro Computer Inc Device a880
Flags: bus master, fast devsel, latency 0, IRQ 44
Memory at faae8000 (64-bit, non-prefetchable) [size=16K]
Capabilities: [80] MSI-X: Enable+ Count=1 Masked-
Capabilities: [90] Express Root Complex Integrated Endpoint, MSI 00
Capabilities: [e0] Power Management version 3
Kernel driver in use: ioatdma

00:16.2 System peripheral: Intel Corporation 5520/5500/X58 Chipset QuickData Technology Device (rev 22)
Subsystem: Super Micro Computer Inc Device a880
Flags: bus master, fast devsel, latency 0, IRQ 45
Memory at faae4000 (64-bit, non-prefetchable) [size=16K]
Capabilities: [80] MSI-X: Enable+ Count=1 Masked-
Capabilities: [90] Express Root Complex Integrated Endpoint, MSI 00
Capabilities: [e0] Power Management version 3
Kernel driver in use: ioatdma

00:16.3 System peripheral: Intel Corporation 5520/5500/X58 Chipset QuickData Technology Device (rev 22)
Subsystem: Super Micro Computer Inc Device a880
Flags: bus master, fast devsel, latency 0, IRQ 46
Memory at faae0000 (64-bit, non-prefetchable) [size=16K]
Capabilities: [80] MSI-X: Enable+ Count=1 Masked-
Capabilities: [90] Express Root Complex Integrated Endpoint, MSI 00
Capabilities: [e0] Power Management version 3
Kernel driver in use: ioatdma

00:16.4 System peripheral: Intel Corporation 5520/5500/X58 Chipset QuickData Technology Device (rev 22)
Subsystem: Super Micro Computer Inc Device a880
Flags: bus master, fast devsel, latency 0, IRQ 43
Memory at faadc000 (64-bit, non-prefetchable) [size=16K]
Capabilities: [80] MSI-X: Enable+ Count=1 Masked-
Capabilities: [90] Express Root Complex Integrated Endpoint, MSI 00
Capabilities: [e0] Power Management version 3
Kernel driver in use: ioatdma

00:16.5 System peripheral: Intel Corporation 5520/5500/X58 Chipset QuickData Technology Device (rev 22)
Subsystem: Super Micro Computer Inc Device a880
Flags: bus master, fast devsel, latency 0, IRQ 44
Memory at faad8000 (64-bit, non-prefetchable) [size=16K]
Capabilities: [80] MSI-X: Enable+ Count=1 Masked-
Capabilities: [90] Express Root Complex Integrated Endpoint, MSI 00
Capabilities: [e0] Power Management version 3
Kernel driver in use: ioatdma

00:16.6 System peripheral: Intel Corporation 5520/5500/X58 Chipset QuickData Technology Device (rev 22)
Subsystem: Super Micro Computer Inc Device a880
Flags: bus master, fast devsel, latency 0, IRQ 45
Memory at faad4000 (64-bit, non-prefetchable) [size=16K]
Capabilities: [80] MSI-X: Enable+ Count=1 Masked-
Capabilities: [90] Express Root Complex Integrated Endpoint, MSI 00
Capabilities: [e0] Power Management version 3
Kernel driver in use: ioatdma

00:16.7 System peripheral: Intel Corporation 5520/5500/X58 Chipset QuickData Technology Device (rev 22)
Subsystem: Super Micro Computer Inc Device a880
Flags: bus master, fast devsel, latency 0, IRQ 46
Memory at faad0000 (64-bit, non-prefetchable) [size=16K]
Capabilities: [80] MSI-X: Enable+ Count=1 Masked-
Capabilities: [90] Express Root Complex Integrated Endpoint, MSI 00
Capabilities: [e0] Power Management version 3
Kernel driver in use: ioatdma

00:1a.0 USB Controller: Intel Corporation 82801JI (ICH10 Family) USB UHCI Controller #4 (prog-if 00 [UHCI])
Subsystem: Super Micro Computer Inc Device a880
Flags: bus master, medium devsel, latency 0, IRQ 16
I/O ports at aea0 [size=32]
Capabilities: [50] PCI Advanced Features
Kernel driver in use: uhci_hcd

00:1a.1 USB Controller: Intel Corporation 82801JI (ICH10 Family) USB UHCI Controller #5 (prog-if 00 [UHCI])
Subsystem: Super Micro Computer Inc Device a880
Flags: bus master, medium devsel, latency 0, IRQ 21
I/O ports at ae80 [size=32]
Capabilities: [50] PCI Advanced Features
Kernel driver in use: uhci_hcd

00:1a.2 USB Controller: Intel Corporation 82801JI (ICH10 Family) USB UHCI Controller #6 (prog-if 00 [UHCI])
Subsystem: Super Micro Computer Inc Device a880
Flags: bus master, medium devsel, latency 0, IRQ 19
I/O ports at ae20 [size=32]
Capabilities: [50] PCI Advanced Features
Kernel driver in use: uhci_hcd

00:1a.7 USB Controller: Intel Corporation 82801JI (ICH10 Family) USB2 EHCI Controller #2 (prog-if 20 [EHCI])
Subsystem: Super Micro Computer Inc Device a880
Flags: bus master, medium devsel, latency 0, IRQ 18
Memory at faaf4000 (32-bit, non-prefetchable) [size=1K]
Capabilities: [50] Power Management version 2
Capabilities: [58] Debug port: BAR=1 offset=00a0
Capabilities: [98] PCI Advanced Features
Kernel driver in use: ehci_hcd

00:1b.0 Audio device: Intel Corporation 82801JI (ICH10 Family) HD Audio Controller
Subsystem: Super Micro Computer Inc Device a880
Flags: bus master, fast devsel, latency 0, IRQ 81
Memory at faaf0000 (64-bit, non-prefetchable) [size=16K]
Capabilities: [50] Power Management version 2
Capabilities: [60] MSI: Enable+ Count=1/1 Maskable- 64bit+
Capabilities: [70] Express Root Complex Integrated Endpoint, MSI 00
Capabilities: [100] Virtual Channel
Capabilities: [130] Root Complex Link
Kernel driver in use: HDA Intel

00:1c.0 PCI bridge: Intel Corporation 82801JI (ICH10 Family) PCI Express Root Port 1 (prog-if 00 [Normal decode])
Flags: bus master, fast devsel, latency 0
Bus: primary=00, secondary=02, subordinate=02, sec-latency=0
I/O behind bridge: 00001000-00001fff
Memory behind bridge: c0400000-c05fffff
Prefetchable memory behind bridge: 00000000c0600000-00000000c07fffff
Capabilities: [40] Express Root Port (Slot+), MSI 00
Capabilities: [80] MSI: Enable+ Count=1/1 Maskable- 64bit-
Capabilities: [90] Subsystem: Super Micro Computer Inc Device a880
Capabilities: [a0] Power Management version 2
Capabilities: [100] Virtual Channel
Capabilities: [180] Root Complex Link
Kernel driver in use: pcieport

00:1c.4 PCI bridge: Intel Corporation 82801JI (ICH10 Family) PCI Express Root Port 5 (prog-if 00 [Normal decode])
Flags: bus master, fast devsel, latency 0
Bus: primary=00, secondary=03, subordinate=03, sec-latency=0
I/O behind bridge: 0000c000-0000cfff
Memory behind bridge: fad00000-fadfffff
Prefetchable memory behind bridge: 00000000c0200000-00000000c03fffff
Capabilities: [40] Express Root Port (Slot+), MSI 00
Capabilities: [80] MSI: Enable+ Count=1/1 Maskable- 64bit-
Capabilities: [90] Subsystem: Super Micro Computer Inc Device a880
Capabilities: [a0] Power Management version 2
Capabilities: [100] Virtual Channel
Capabilities: [180] Root Complex Link
Kernel driver in use: pcieport

00:1c.5 PCI bridge: Intel Corporation 82801JI (ICH10 Family) PCI Express Root Port 6 (prog-if 00 [Normal decode])
Flags: bus master, fast devsel, latency 0
Bus: primary=00, secondary=04, subordinate=04, sec-latency=0
I/O behind bridge: 0000d000-0000dfff
Memory behind bridge: fae00000-faefffff
Prefetchable memory behind bridge: 00000000c0000000-00000000c01fffff
Capabilities: [40] Express Root Port (Slot+), MSI 00
Capabilities: [80] MSI: Enable+ Count=1/1 Maskable- 64bit-
Capabilities: [90] Subsystem: Super Micro Computer Inc Device a880
Capabilities: [a0] Power Management version 2
Capabilities: [100] Virtual Channel
Capabilities: [180] Root Complex Link
Kernel driver in use: pcieport

00:1d.0 USB Controller: Intel Corporation 82801JI (ICH10 Family) USB UHCI Controller #1 (prog-if 00 [UHCI])
Subsystem: Super Micro Computer Inc Device a880
Flags: bus master, medium devsel, latency 0, IRQ 23
I/O ports at af20 [size=32]
Capabilities: [50] PCI Advanced Features
Kernel driver in use: uhci_hcd

00:1d.1 USB Controller: Intel Corporation 82801JI (ICH10 Family) USB UHCI Controller #2 (prog-if 00 [UHCI])
Subsystem: Super Micro Computer Inc Device a880
Flags: bus master, medium devsel, latency 0, IRQ 19
I/O ports at af00 [size=32]
Capabilities: [50] PCI Advanced Features
Kernel driver in use: uhci_hcd

00:1d.2 USB Controller: Intel Corporation 82801JI (ICH10 Family) USB UHCI Controller #3 (prog-if 00 [UHCI])
Subsystem: Super Micro Computer Inc Device a880
Flags: bus master, medium devsel, latency 0, IRQ 18
I/O ports at aec0 [size=32]
Capabilities: [50] PCI Advanced Features
Kernel driver in use: uhci_hcd

00:1d.7 USB Controller: Intel Corporation 82801JI (ICH10 Family) USB2 EHCI Controller #1 (prog-if 20 [EHCI])
Subsystem: Super Micro Computer Inc Device a880
Flags: bus master, medium devsel, latency 0, IRQ 23
Memory at faaf6000 (32-bit, non-prefetchable) [size=1K]
Capabilities: [50] Power Management version 2
Capabilities: [58] Debug port: BAR=1 offset=00a0
Capabilities: [98] PCI Advanced Features
Kernel driver in use: ehci_hcd

00:1e.0 PCI bridge: Intel Corporation 82801 PCI Bridge (rev 90) (prog-if 01 [Subtractive decode])
Flags: bus master, fast devsel, latency 0
Bus: primary=00, secondary=01, subordinate=01, sec-latency=32
I/O behind bridge: 0000b000-0000bfff
Memory behind bridge: fab00000-facfffff
Capabilities: [50] Subsystem: Super Micro Computer Inc Device a880

00:1f.0 ISA bridge: Intel Corporation 82801JIR (ICH10R) LPC Interface Controller
Subsystem: Super Micro Computer Inc Device a880
Flags: bus master, medium devsel, latency 0
Capabilities: [e0] Vendor Specific Information: Len=0c

00:1f.2 SATA controller: Intel Corporation 82801JI (ICH10 Family) SATA AHCI Controller (prog-if 01 [AHCI 1.0])
Subsystem: Super Micro Computer Inc Device a880
Flags: bus master, 66MHz, medium devsel, latency 0, IRQ 71
I/O ports at aff0 [size=8]
I/O ports at afac [size=4]
I/O ports at afe0 [size=8]
I/O ports at afa8 [size=4]
I/O ports at af80 [size=32]
Memory at faafe000 (32-bit, non-prefetchable) [size=2K]
Capabilities: [80] MSI: Enable+ Count=1/16 Maskable- 64bit-
Capabilities: [70] Power Management version 3
Capabilities: [a8] SATA HBA v1.0
Capabilities: [b0] PCI Advanced Features
Kernel driver in use: ahci

00:1f.3 SMBus: Intel Corporation 82801JI (ICH10 Family) SMBus Controller
Subsystem: Super Micro Computer Inc Device a880
Flags: medium devsel, IRQ 18
Memory at faafc000 (64-bit, non-prefetchable) [size=256]
I/O ports at 0400 [size=32]
Kernel driver in use: i801_smbus

01:02.0 FireWire (IEEE 1394): Texas Instruments TSB43AB22/A IEEE-1394a-2000 Controller (PHY/Link) (prog-if 10 [OHCI])
Subsystem: Super Micro Computer Inc Device 1411
Flags: bus master, medium devsel, latency 64, IRQ 18
Memory at fabf7800 (32-bit, non-prefetchable) [size=2K]
Memory at fabf8000 (32-bit, non-prefetchable) [size=16K]
Capabilities: [44] Power Management version 2
Kernel driver in use: firewire_ohci

01:05.0 RAID bus controller: Silicon Image, Inc. SiI 3114 [SATALink/SATARaid] Serial ATA Controller (rev 02)
Subsystem: Silicon Image, Inc. Device 7114
Flags: bus master, 66MHz, medium devsel, latency 64, IRQ 19
I/O ports at bb90 [size=8]
I/O ports at bb88 [size=4]
I/O ports at bb98 [size=8]
I/O ports at bb8c [size=4]
I/O ports at bba0 [size=16]
Memory at fabffc00 (32-bit, non-prefetchable) [size=1K]
Expansion ROM at fac00000 [disabled] [size=512K]
Capabilities: [60] Power Management version 2
Kernel driver in use: sata_sil

01:06.0 Ethernet controller: 3Com Corporation 3c905C-TX/TX-M [Tornado] (rev 78)
Subsystem: 3Com Corporation 3C905CX-TX/TX-M Fast Etherlink for PC Management NIC
Flags: bus master, medium devsel, latency 64, IRQ 17
I/O ports at bc00 [size=128]
Memory at facdfc00 (32-bit, non-prefetchable) [size=128]
Expansion ROM at face0000 [disabled] [size=128K]
Capabilities: [dc] Power Management version 2
Kernel driver in use: 3c59x

03:00.0 Ethernet controller: Intel Corporation 82573E Gigabit Ethernet Controller (Copper) (rev 03)
Subsystem: Super Micro Computer Inc Device 108c
Flags: bus master, fast devsel, latency 0, IRQ 70
Memory at fade0000 (32-bit, non-prefetchable) [size=128K]
I/O ports at cf80 [size=32]
Capabilities: [c8] Power Management version 2
Capabilities: [d0] MSI: Enable+ Count=1/1 Maskable- 64bit+
Capabilities: [e0] Express Endpoint, MSI 00
Capabilities: [100] Advanced Error Reporting
Capabilities: [140] Device Serial Number 00-25-90-ff-ff-24-d1-e4
Kernel driver in use: e1000e

04:00.0 Ethernet controller: Intel Corporation 82573L Gigabit Ethernet Controller
Subsystem: Super Micro Computer Inc Device 109a
Flags: bus master, fast devsel, latency 0, IRQ 72
Memory at faee0000 (32-bit, non-prefetchable) [size=128K]
I/O ports at df80 [size=32]
Capabilities: [c8] Power Management version 2
Capabilities: [d0] MSI: Enable+ Count=1/1 Maskable- 64bit+
Capabilities: [e0] Express Endpoint, MSI 00
Capabilities: [100] Advanced Error Reporting
Capabilities: [140] Device Serial Number 00-25-90-ff-ff-24-d1-e5
Kernel driver in use: e1000e

06:00.0 VGA compatible controller: ATI Technologies Inc RV370 5B60 [Radeon X300 (PCIE)] (prog-if 00 [VGA controller])
Subsystem: PC Partner Limited Radeon X300 (PCIE)
Flags: bus master, fast devsel, latency 0, IRQ 11
Memory at d8000000 (32-bit, prefetchable) [size=128M]
I/O ports at e000 [size=256]
Memory at fafd0000 (32-bit, non-prefetchable) [size=64K]
Expansion ROM at fafe0000 [disabled] [size=128K]
Capabilities: [50] Power Management version 2
Capabilities: [58] Express Endpoint, MSI 00
Capabilities: [80] MSI: Enable- Count=1/1 Maskable- 64bit+
Capabilities: [100] Advanced Error Reporting

06:00.1 Display controller: ATI Technologies Inc RV370 [Radeon X300SE]
Subsystem: PC Partner Limited Radeon X300SE
Flags: bus master, fast devsel, latency 0
Memory at fafc0000 (32-bit, non-prefetchable) [size=64K]
Capabilities: [50] Power Management version 2
Capabilities: [58] Express Endpoint, MSI 00


--Boundary-00=_b6BJOwgYP3vEmKe
Content-Type: text/plain;
charset="UTF-8";
name="sde"
Content-Transfer-Encoding: 7bit
Content-Disposition: attachment;
filename="sde"

smartctl 5.40 2010-07-12 r3124 [i686-pc-linux-gnu] (local build)
Copyright (C) 2002-10 by Bruce Allen, http://smartmontools.sourceforge.net

=== START OF INFORMATION SECTION ===
Model Family: Western Digital Caviar Green (Adv. Format) family
Device Model: WDC WD20EARS-00MVWB0
Serial Number: WD-WCAZA6281995
Firmware Version: 51.0AB51
User Capacity: 2,000,398,934,016 bytes
Device is: In smartctl database [for details use: -P show]
ATA Version is: 8
ATA Standard is: Exact ATA specification draft version not indicated
Local Time is: Mon Jul 18 13:45:07 2011 CEST
SMART support is: Available - device has SMART capability.
SMART support is: Enabled


--Boundary-00=_b6BJOwgYP3vEmKe
Content-Type: text/plain;
charset="UTF-8";
name="sdd"
Content-Transfer-Encoding: 7bit
Content-Disposition: attachment;
filename="sdd"

smartctl 5.40 2010-07-12 r3124 [i686-pc-linux-gnu] (local build)
Copyright (C) 2002-10 by Bruce Allen, http://smartmontools.sourceforge.net

=== START OF INFORMATION SECTION ===
Model Family: Seagate Barracuda 7200.12 family
Device Model: ST3500418AS
Serial Number: 9VM1WK4N
Firmware Version: CC46
User Capacity: 500,107,862,016 bytes
Device is: In smartctl database [for details use: -P show]
ATA Version is: 8
ATA Standard is: ATA-8-ACS revision 4
Local Time is: Mon Jul 18 13:45:03 2011 CEST
SMART support is: Available - device has SMART capability.
SMART support is: Enabled


--Boundary-00=_b6BJOwgYP3vEmKe
Content-Type: text/plain;
charset="UTF-8";
name="sdf"
Content-Transfer-Encoding: 7bit
Content-Disposition: attachment;
filename="sdf"

smartctl 5.40 2010-07-12 r3124 [i686-pc-linux-gnu] (local build)
Copyright (C) 2002-10 by Bruce Allen, http://smartmontools.sourceforge.net

=== START OF INFORMATION SECTION ===
Model Family: Western Digital Caviar Green (Adv. Format) family
Device Model: WDC WD20EARS-00MVWB0
Serial Number: WD-WCAZA5510079
Firmware Version: 51.0AB51
User Capacity: 2,000,398,934,016 bytes
Device is: In smartctl database [for details use: -P show]
ATA Version is: 8
ATA Standard is: Exact ATA specification draft version not indicated
Local Time is: Mon Jul 18 13:45:12 2011 CEST
SMART support is: Available - device has SMART capability.
SMART support is: Enabled


--Boundary-00=_b6BJOwgYP3vEmKe--
--
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

Re: standard performance (write speed 20Mb/s)

--Boundary-00=_lECJOkJ+W+9lhYH
Content-Type: text/plain;
charset="iso-8859-1"
Content-Transfer-Encoding: 7bit

> Then you have multiple problems causing poor performance. Now is the
> time for you to post your hardware configuration, drive model
> number(s), mdadm config, and filesystem. You should have done all of
> this in your initial post.

hello and sorry for the late :-(

now is a resync in progress, I can't stop it. Try /usr/share/mdadm/checkarray
-x md0 but nothing..

fs is ext3 (done less 10 days ago)

> You've been on this list long enough to have known of the WD Green
> sector alignment issue and avoided it, and to know better than to run
> performance tests while an array is still in its initial sync. Thus I
> initially assumed your problem was merely the insane dd block size.

when I wrote a post there was not resync in progress..

tell me if you need known other things, thanks


00:00.0 Host bridge: Intel Corporation 5520 I/O Hub to ESI Port (rev 22)
Subsystem: Super Micro Computer Inc Device a880
Flags: fast devsel
Capabilities: [60] MSI: Enable- Count=1/2 Maskable+ 64bit-
Capabilities: [90] Express Root Port (Slot-), MSI 00
Capabilities: [e0] Power Management version 3
Capabilities: [100] Advanced Error Reporting
Capabilities: [150] Access Control Services
Capabilities: [160] Vendor Specific Information: ID=0002 Rev=0 Len=00c

00:01.0 PCI bridge: Intel Corporation 5520/5500/X58 I/O Hub PCI Express Root
Port 1 (rev 22) (prog-if 00 [Normal decode])
Flags: bus master, fast devsel, latency 0
Bus: primary=00, secondary=07, subordinate=07, sec-latency=0
Capabilities: [40] Subsystem: Super Micro Computer Inc Device a880
Capabilities: [60] MSI: Enable+ Count=1/2 Maskable+ 64bit-
Capabilities: [90] Express Root Port (Slot+), MSI 00
Capabilities: [e0] Power Management version 3
Capabilities: [100] Advanced Error Reporting
Capabilities: [150] Access Control Services
Capabilities: [160] Vendor Specific Information: ID=0002 Rev=0 Len=00c
Kernel driver in use: pcieport

00:03.0 PCI bridge: Intel Corporation 5520/5500/X58 I/O Hub PCI Express Root
Port 3 (rev 22) (prog-if 00 [Normal decode])
Flags: bus master, fast devsel, latency 0
Bus: primary=00, secondary=06, subordinate=06, sec-latency=0
I/O behind bridge: 0000e000-0000efff
Memory behind bridge: faf00000-faffffff
Prefetchable memory behind bridge: 00000000d8000000-00000000dfffffff
Capabilities: [40] Subsystem: Super Micro Computer Inc Device a880
Capabilities: [60] MSI: Enable+ Count=1/2 Maskable+ 64bit-
Capabilities: [90] Express Root Port (Slot+), MSI 00
Capabilities: [e0] Power Management version 3
Capabilities: [100] Advanced Error Reporting
Capabilities: [150] Access Control Services
Capabilities: [160] Vendor Specific Information: ID=0002 Rev=0 Len=00c
Kernel driver in use: pcieport

00:07.0 PCI bridge: Intel Corporation 5520/5500/X58 I/O Hub PCI Express Root
Port 7 (rev 22) (prog-if 00 [Normal decode])
Flags: bus master, fast devsel, latency 0
Bus: primary=00, secondary=05, subordinate=05, sec-latency=0
Capabilities: [40] Subsystem: Super Micro Computer Inc Device a880
Capabilities: [60] MSI: Enable+ Count=1/2 Maskable+ 64bit-
Capabilities: [90] Express Root Port (Slot+), MSI 00
Capabilities: [e0] Power Management version 3
Capabilities: [100] Advanced Error Reporting
Capabilities: [150] Access Control Services
Capabilities: [160] Vendor Specific Information: ID=0002 Rev=0 Len=00c
Kernel driver in use: pcieport

00:0e.0 Host bridge: Intel Corporation Device 341c (rev 22)
Flags: fast devsel
Capabilities: [40] Express Root Complex Integrated Endpoint, MSI 00
Capabilities: [60] #00 [0000]
Capabilities: [100] Vendor Specific Information: ID=0001 Rev=0 Len=0b8

00:0e.1 Host bridge: Intel Corporation Device 341d (rev 22)
Flags: fast devsel
Capabilities: [40] Express Root Complex Integrated Endpoint, MSI 00
Capabilities: [60] #00 [0000]

00:0e.2 Host bridge: Intel Corporation Device 341e (rev 22)
Flags: fast devsel
Capabilities: [40] Express Root Complex Integrated Endpoint, MSI 00
Capabilities: [60] #00 [0000]

00:13.0 PIC: Intel Corporation 5520/5500/X58 I/O Hub I/OxAPIC Interrupt
Controller (rev 22) (prog-if 20 [IO(X)-APIC])
Flags: bus master, fast devsel, latency 0
Memory at fec8a000 (32-bit, non-prefetchable) [size=4K]
Capabilities: [6c] Power Management version 3

00:14.0 PIC: Intel Corporation 5520/5500/X58 I/O Hub System Management
Registers (rev 22) (prog-if 00 [8259])
Flags: fast devsel
Capabilities: [40] Express Root Complex Integrated Endpoint, MSI 00

00:14.1 PIC: Intel Corporation 5520/5500/X58 I/O Hub GPIO and Scratch Pad
Registers (rev 22) (prog-if 00 [8259])
Flags: fast devsel
Capabilities: [40] Express Root Complex Integrated Endpoint, MSI 00

00:14.2 PIC: Intel Corporation 5520/5500/X58 I/O Hub Control Status and RAS
Registers (rev 22) (prog-if 00 [8259])
Flags: fast devsel
Capabilities: [40] Express Root Complex Integrated Endpoint, MSI 00

00:14.3 PIC: Intel Corporation 5520/5500/X58 I/O Hub Throttle Registers (rev
22) (prog-if 00 [8259])
Flags: fast devsel

00:16.0 System peripheral: Intel Corporation 5520/5500/X58 Chipset QuickData
Technology Device (rev 22)
Subsystem: Super Micro Computer Inc Device a880
Flags: bus master, fast devsel, latency 0, IRQ 43
Memory at faaec000 (64-bit, non-prefetchable) [size=16K]
Capabilities: [80] MSI-X: Enable+ Count=1 Masked-
Capabilities: [90] Express Root Complex Integrated Endpoint, MSI 00
Capabilities: [e0] Power Management version 3
Kernel driver in use: ioatdma

00:16.1 System peripheral: Intel Corporation 5520/5500/X58 Chipset QuickData
Technology Device (rev 22)
Subsystem: Super Micro Computer Inc Device a880
Flags: bus master, fast devsel, latency 0, IRQ 44
Memory at faae8000 (64-bit, non-prefetchable) [size=16K]
Capabilities: [80] MSI-X: Enable+ Count=1 Masked-
Capabilities: [90] Express Root Complex Integrated Endpoint, MSI 00
Capabilities: [e0] Power Management version 3
Kernel driver in use: ioatdma

00:16.2 System peripheral: Intel Corporation 5520/5500/X58 Chipset QuickData
Technology Device (rev 22)
Subsystem: Super Micro Computer Inc Device a880
Flags: bus master, fast devsel, latency 0, IRQ 45
Memory at faae4000 (64-bit, non-prefetchable) [size=16K]
Capabilities: [80] MSI-X: Enable+ Count=1 Masked-
Capabilities: [90] Express Root Complex Integrated Endpoint, MSI 00
Capabilities: [e0] Power Management version 3
Kernel driver in use: ioatdma

00:16.3 System peripheral: Intel Corporation 5520/5500/X58 Chipset QuickData
Technology Device (rev 22)
Subsystem: Super Micro Computer Inc Device a880
Flags: bus master, fast devsel, latency 0, IRQ 46
Memory at faae0000 (64-bit, non-prefetchable) [size=16K]
Capabilities: [80] MSI-X: Enable+ Count=1 Masked-
Capabilities: [90] Express Root Complex Integrated Endpoint, MSI 00
Capabilities: [e0] Power Management version 3
Kernel driver in use: ioatdma

00:16.4 System peripheral: Intel Corporation 5520/5500/X58 Chipset QuickData
Technology Device (rev 22)
Subsystem: Super Micro Computer Inc Device a880
Flags: bus master, fast devsel, latency 0, IRQ 43
Memory at faadc000 (64-bit, non-prefetchable) [size=16K]
Capabilities: [80] MSI-X: Enable+ Count=1 Masked-
Capabilities: [90] Express Root Complex Integrated Endpoint, MSI 00
Capabilities: [e0] Power Management version 3
Kernel driver in use: ioatdma

00:16.5 System peripheral: Intel Corporation 5520/5500/X58 Chipset QuickData
Technology Device (rev 22)
Subsystem: Super Micro Computer Inc Device a880
Flags: bus master, fast devsel, latency 0, IRQ 44
Memory at faad8000 (64-bit, non-prefetchable) [size=16K]
Capabilities: [80] MSI-X: Enable+ Count=1 Masked-
Capabilities: [90] Express Root Complex Integrated Endpoint, MSI 00
Capabilities: [e0] Power Management version 3
Kernel driver in use: ioatdma

00:16.6 System peripheral: Intel Corporation 5520/5500/X58 Chipset QuickData
Technology Device (rev 22)
Subsystem: Super Micro Computer Inc Device a880
Flags: bus master, fast devsel, latency 0, IRQ 45
Memory at faad4000 (64-bit, non-prefetchable) [size=16K]
Capabilities: [80] MSI-X: Enable+ Count=1 Masked-
Capabilities: [90] Express Root Complex Integrated Endpoint, MSI 00
Capabilities: [e0] Power Management version 3
Kernel driver in use: ioatdma

00:16.7 System peripheral: Intel Corporation 5520/5500/X58 Chipset QuickData
Technology Device (rev 22)
Subsystem: Super Micro Computer Inc Device a880
Flags: bus master, fast devsel, latency 0, IRQ 46
Memory at faad0000 (64-bit, non-prefetchable) [size=16K]
Capabilities: [80] MSI-X: Enable+ Count=1 Masked-
Capabilities: [90] Express Root Complex Integrated Endpoint, MSI 00
Capabilities: [e0] Power Management version 3
Kernel driver in use: ioatdma

00:1a.0 USB Controller: Intel Corporation 82801JI (ICH10 Family) USB UHCI
Controller #4 (prog-if 00 [UHCI])
Subsystem: Super Micro Computer Inc Device a880
Flags: bus master, medium devsel, latency 0, IRQ 16
I/O ports at aea0 [size=32]
Capabilities: [50] PCI Advanced Features
Kernel driver in use: uhci_hcd

00:1a.1 USB Controller: Intel Corporation 82801JI (ICH10 Family) USB UHCI
Controller #5 (prog-if 00 [UHCI])
Subsystem: Super Micro Computer Inc Device a880
Flags: bus master, medium devsel, latency 0, IRQ 21
I/O ports at ae80 [size=32]
Capabilities: [50] PCI Advanced Features
Kernel driver in use: uhci_hcd

00:1a.2 USB Controller: Intel Corporation 82801JI (ICH10 Family) USB UHCI
Controller #6 (prog-if 00 [UHCI])
Subsystem: Super Micro Computer Inc Device a880
Flags: bus master, medium devsel, latency 0, IRQ 19
I/O ports at ae20 [size=32]
Capabilities: [50] PCI Advanced Features
Kernel driver in use: uhci_hcd

00:1a.7 USB Controller: Intel Corporation 82801JI (ICH10 Family) USB2 EHCI
Controller #2 (prog-if 20 [EHCI])
Subsystem: Super Micro Computer Inc Device a880
Flags: bus master, medium devsel, latency 0, IRQ 18
Memory at faaf4000 (32-bit, non-prefetchable) [size=1K]
Capabilities: [50] Power Management version 2
Capabilities: [58] Debug port: BAR=1 offset=00a0
Capabilities: [98] PCI Advanced Features
Kernel driver in use: ehci_hcd

00:1b.0 Audio device: Intel Corporation 82801JI (ICH10 Family) HD Audio
Controller
Subsystem: Super Micro Computer Inc Device a880
Flags: bus master, fast devsel, latency 0, IRQ 81
Memory at faaf0000 (64-bit, non-prefetchable) [size=16K]
Capabilities: [50] Power Management version 2
Capabilities: [60] MSI: Enable+ Count=1/1 Maskable- 64bit+
Capabilities: [70] Express Root Complex Integrated Endpoint, MSI 00
Capabilities: [100] Virtual Channel
Capabilities: [130] Root Complex Link
Kernel driver in use: HDA Intel

00:1c.0 PCI bridge: Intel Corporation 82801JI (ICH10 Family) PCI Express Root
Port 1 (prog-if 00 [Normal decode])
Flags: bus master, fast devsel, latency 0
Bus: primary=00, secondary=02, subordinate=02, sec-latency=0
I/O behind bridge: 00001000-00001fff
Memory behind bridge: c0400000-c05fffff
Prefetchable memory behind bridge: 00000000c0600000-00000000c07fffff
Capabilities: [40] Express Root Port (Slot+), MSI 00
Capabilities: [80] MSI: Enable+ Count=1/1 Maskable- 64bit-
Capabilities: [90] Subsystem: Super Micro Computer Inc Device a880
Capabilities: [a0] Power Management version 2
Capabilities: [100] Virtual Channel
Capabilities: [180] Root Complex Link
Kernel driver in use: pcieport

00:1c.4 PCI bridge: Intel Corporation 82801JI (ICH10 Family) PCI Express Root
Port 5 (prog-if 00 [Normal decode])
Flags: bus master, fast devsel, latency 0
Bus: primary=00, secondary=03, subordinate=03, sec-latency=0
I/O behind bridge: 0000c000-0000cfff
Memory behind bridge: fad00000-fadfffff
Prefetchable memory behind bridge: 00000000c0200000-00000000c03fffff
Capabilities: [40] Express Root Port (Slot+), MSI 00
Capabilities: [80] MSI: Enable+ Count=1/1 Maskable- 64bit-
Capabilities: [90] Subsystem: Super Micro Computer Inc Device a880
Capabilities: [a0] Power Management version 2
Capabilities: [100] Virtual Channel
Capabilities: [180] Root Complex Link
Kernel driver in use: pcieport

00:1c.5 PCI bridge: Intel Corporation 82801JI (ICH10 Family) PCI Express Root
Port 6 (prog-if 00 [Normal decode])
Flags: bus master, fast devsel, latency 0
Bus: primary=00, secondary=04, subordinate=04, sec-latency=0
I/O behind bridge: 0000d000-0000dfff
Memory behind bridge: fae00000-faefffff
Prefetchable memory behind bridge: 00000000c0000000-00000000c01fffff
Capabilities: [40] Express Root Port (Slot+), MSI 00
Capabilities: [80] MSI: Enable+ Count=1/1 Maskable- 64bit-
Capabilities: [90] Subsystem: Super Micro Computer Inc Device a880
Capabilities: [a0] Power Management version 2
Capabilities: [100] Virtual Channel
Capabilities: [180] Root Complex Link
Kernel driver in use: pcieport

00:1d.0 USB Controller: Intel Corporation 82801JI (ICH10 Family) USB UHCI
Controller #1 (prog-if 00 [UHCI])
Subsystem: Super Micro Computer Inc Device a880
Flags: bus master, medium devsel, latency 0, IRQ 23
I/O ports at af20 [size=32]
Capabilities: [50] PCI Advanced Features
Kernel driver in use: uhci_hcd

00:1d.1 USB Controller: Intel Corporation 82801JI (ICH10 Family) USB UHCI
Controller #2 (prog-if 00 [UHCI])
Subsystem: Super Micro Computer Inc Device a880
Flags: bus master, medium devsel, latency 0, IRQ 19
I/O ports at af00 [size=32]
Capabilities: [50] PCI Advanced Features
Kernel driver in use: uhci_hcd

00:1d.2 USB Controller: Intel Corporation 82801JI (ICH10 Family) USB UHCI
Controller #3 (prog-if 00 [UHCI])
Subsystem: Super Micro Computer Inc Device a880
Flags: bus master, medium devsel, latency 0, IRQ 18
I/O ports at aec0 [size=32]
Capabilities: [50] PCI Advanced Features
Kernel driver in use: uhci_hcd

00:1d.7 USB Controller: Intel Corporation 82801JI (ICH10 Family) USB2 EHCI
Controller #1 (prog-if 20 [EHCI])
Subsystem: Super Micro Computer Inc Device a880
Flags: bus master, medium devsel, latency 0, IRQ 23
Memory at faaf6000 (32-bit, non-prefetchable) [size=1K]
Capabilities: [50] Power Management version 2
Capabilities: [58] Debug port: BAR=1 offset=00a0
Capabilities: [98] PCI Advanced Features
Kernel driver in use: ehci_hcd

00:1e.0 PCI bridge: Intel Corporation 82801 PCI Bridge (rev 90) (prog-if 01
[Subtractive decode])
Flags: bus master, fast devsel, latency 0
Bus: primary=00, secondary=01, subordinate=01, sec-latency=32
I/O behind bridge: 0000b000-0000bfff
Memory behind bridge: fab00000-facfffff
Capabilities: [50] Subsystem: Super Micro Computer Inc Device a880

00:1f.0 ISA bridge: Intel Corporation 82801JIR (ICH10R) LPC Interface
Controller
Subsystem: Super Micro Computer Inc Device a880
Flags: bus master, medium devsel, latency 0
Capabilities: [e0] Vendor Specific Information: Len=0c

00:1f.2 SATA controller: Intel Corporation 82801JI (ICH10 Family) SATA AHCI
Controller (prog-if 01 [AHCI 1.0])
Subsystem: Super Micro Computer Inc Device a880
Flags: bus master, 66MHz, medium devsel, latency 0, IRQ 71
I/O ports at aff0 [size=8]
I/O ports at afac [size=4]
I/O ports at afe0 [size=8]
I/O ports at afa8 [size=4]
I/O ports at af80 [size=32]
Memory at faafe000 (32-bit, non-prefetchable) [size=2K]
Capabilities: [80] MSI: Enable+ Count=1/16 Maskable- 64bit-
Capabilities: [70] Power Management version 3
Capabilities: [a8] SATA HBA v1.0
Capabilities: [b0] PCI Advanced Features
Kernel driver in use: ahci

00:1f.3 SMBus: Intel Corporation 82801JI (ICH10 Family) SMBus Controller
Subsystem: Super Micro Computer Inc Device a880
Flags: medium devsel, IRQ 18
Memory at faafc000 (64-bit, non-prefetchable) [size=256]
I/O ports at 0400 [size=32]
Kernel driver in use: i801_smbus

01:02.0 FireWire (IEEE 1394): Texas Instruments TSB43AB22/A IEEE-1394a-2000
Controller (PHY/Link) (prog-if 10 [OHCI])
Subsystem: Super Micro Computer Inc Device 1411
Flags: bus master, medium devsel, latency 64, IRQ 18
Memory at fabf7800 (32-bit, non-prefetchable) [size=2K]
Memory at fabf8000 (32-bit, non-prefetchable) [size=16K]
Capabilities: [44] Power Management version 2
Kernel driver in use: firewire_ohci

01:05.0 RAID bus controller: Silicon Image, Inc. SiI 3114 [SATALink/SATARaid]
Serial ATA Controller (rev 02)
Subsystem: Silicon Image, Inc. Device 7114
Flags: bus master, 66MHz, medium devsel, latency 64, IRQ 19
I/O ports at bb90 [size=8]
I/O ports at bb88 [size=4]
I/O ports at bb98 [size=8]
I/O ports at bb8c [size=4]
I/O ports at bba0 [size=16]
Memory at fabffc00 (32-bit, non-prefetchable) [size=1K]
Expansion ROM at fac00000 [disabled] [size=512K]
Capabilities: [60] Power Management version 2
Kernel driver in use: sata_sil

01:06.0 Ethernet controller: 3Com Corporation 3c905C-TX/TX-M [Tornado] (rev
78)
Subsystem: 3Com Corporation 3C905CX-TX/TX-M Fast Etherlink for PC
Management NIC
Flags: bus master, medium devsel, latency 64, IRQ 17
I/O ports at bc00 [size=128]
Memory at facdfc00 (32-bit, non-prefetchable) [size=128]
Expansion ROM at face0000 [disabled] [size=128K]
Capabilities: [dc] Power Management version 2
Kernel driver in use: 3c59x

03:00.0 Ethernet controller: Intel Corporation 82573E Gigabit Ethernet
Controller (Copper) (rev 03)
Subsystem: Super Micro Computer Inc Device 108c
Flags: bus master, fast devsel, latency 0, IRQ 70
Memory at fade0000 (32-bit, non-prefetchable) [size=128K]
I/O ports at cf80 [size=32]
Capabilities: [c8] Power Management version 2
Capabilities: [d0] MSI: Enable+ Count=1/1 Maskable- 64bit+
Capabilities: [e0] Express Endpoint, MSI 00
Capabilities: [100] Advanced Error Reporting
Capabilities: [140] Device Serial Number 00-25-90-ff-ff-24-d1-e4
Kernel driver in use: e1000e

04:00.0 Ethernet controller: Intel Corporation 82573L Gigabit Ethernet
Controller
Subsystem: Super Micro Computer Inc Device 109a
Flags: bus master, fast devsel, latency 0, IRQ 72
Memory at faee0000 (32-bit, non-prefetchable) [size=128K]
I/O ports at df80 [size=32]
Capabilities: [c8] Power Management version 2
Capabilities: [d0] MSI: Enable+ Count=1/1 Maskable- 64bit+
Capabilities: [e0] Express Endpoint, MSI 00
Capabilities: [100] Advanced Error Reporting
Capabilities: [140] Device Serial Number 00-25-90-ff-ff-24-d1-e5
Kernel driver in use: e1000e

06:00.0 VGA compatible controller: ATI Technologies Inc RV370 5B60 [Radeon
X300 (PCIE)] (prog-if 00 [VGA controller])
Subsystem: PC Partner Limited Radeon X300 (PCIE)
Flags: bus master, fast devsel, latency 0, IRQ 11
Memory at d8000000 (32-bit, prefetchable) [size=128M]
I/O ports at e000 [size=256]
Memory at fafd0000 (32-bit, non-prefetchable) [size=64K]
Expansion ROM at fafe0000 [disabled] [size=128K]
Capabilities: [50] Power Management version 2
Capabilities: [58] Express Endpoint, MSI 00
Capabilities: [80] MSI: Enable- Count=1/1 Maskable- 64bit+
Capabilities: [100] Advanced Error Reporting

06:00.1 Display controller: ATI Technologies Inc RV370 [Radeon X300SE]
Subsystem: PC Partner Limited Radeon X300SE
Flags: bus master, fast devsel, latency 0
Memory at fafc0000 (32-bit, non-prefetchable) [size=64K]
Capabilities: [50] Power Management version 2
Capabilities: [58] Express Endpoint, MSI 00

# mdadm.conf
#
# Please refer to mdadm.conf(5) for information about this file.
#

# by default, scan all partitions (/proc/partitions) for MD superblocks.
# alternatively, specify devices to scan, using wildcards if desired.
DEVICE partitions

# auto-create devices with Debian standard permissions
CREATE owner=root group=disk mode=0660 auto=yes

# automatically tag new arrays as belonging to the local system
HOMEHOST

# instruct the monitoring daemon where to send mail alerts
MAILADDR pol@yahoo.it

# definitions of existing MD arrays

# This file was auto-generated on Fri, 08 Jul 2011 14:37:51 -0700
# by mkconf 3.1.4-1+8efb9d1

/dev/md0:
Version : 1.2
Creation Time : Fri Jul 8 23:52:13 2011
Raid Level : raid5
Array Size : 5860538368 (5589.05 GiB 6001.19 GB)
Used Dev Size : 1465134592 (1397.26 GiB 1500.30 GB)
Raid Devices : 5
Total Devices : 5
Persistence : Superblock is persistent

Update Time : Mon Jul 18 13:14:04 2011
State : active, resyncing
Active Devices : 5
Working Devices : 5
Failed Devices : 0
Spare Devices : 0

Layout : left-symmetric
Chunk Size : 512K

Rebuild Status : 33% complete

Name : smooth:0 (local to host smooth)
UUID : bfca3ad6:a7df5fa5:20ba4933:55fd4181
Events : 6212

Number Major Minor RaidDevice State
0 8 64 0 active sync /dev/sde
1 8 97 1 active sync /dev/sdg1
2 8 113 2 active sync /dev/sdh1
3 8 129 3 active sync /dev/sdi1
5 8 81 4 active sync /dev/sdf1
smartctl 5.40 2010-07-12 r3124 [i686-pc-linux-gnu] (local build)
Copyright (C) 2002-10 by Bruce Allen, http://smartmontools.sourceforge.net

=== START OF INFORMATION SECTION ===
Model Family: Seagate Barracuda 7200.11 family
Device Model: ST31500341AS
Serial Number: 9VS4PSG9
Firmware Version: CC1H
User Capacity: 1,500,301,910,016 bytes
Device is: In smartctl database [for details use: -P show]
ATA Version is: 8
ATA Standard is: ATA-8-ACS revision 4
Local Time is: Mon Jul 18 13:44:52 2011 CEST
SMART support is: Available - device has SMART capability.
SMART support is: Enabled

smartctl 5.40 2010-07-12 r3124 [i686-pc-linux-gnu] (local build)
Copyright (C) 2002-10 by Bruce Allen, http://smartmontools.sourceforge.net

=== START OF INFORMATION SECTION ===
Model Family: Seagate Barracuda 7200.11 family
Device Model: ST31500341AS
Serial Number: 9VS3KL49
Firmware Version: CC1H
User Capacity: 1,500,301,910,016 bytes
Device is: In smartctl database [for details use: -P show]
ATA Version is: 8
ATA Standard is: ATA-8-ACS revision 4
Local Time is: Mon Jul 18 13:45:00 2011 CEST
SMART support is: Available - device has SMART capability.
SMART support is: Enabled

smartctl 5.40 2010-07-12 r3124 [i686-pc-linux-gnu] (local build)
Copyright (C) 2002-10 by Bruce Allen, http://smartmontools.sourceforge.net

=== START OF INFORMATION SECTION ===
Model Family: Seagate Barracuda 7200.12 family
Device Model: ST3500418AS
Serial Number: 9VM1WK4N
Firmware Version: CC46
User Capacity: 500,107,862,016 bytes
Device is: In smartctl database [for details use: -P show]
ATA Version is: 8
ATA Standard is: ATA-8-ACS revision 4
Local Time is: Mon Jul 18 13:45:03 2011 CEST
SMART support is: Available - device has SMART capability.
SMART support is: Enabled

smartctl 5.40 2010-07-12 r3124 [i686-pc-linux-gnu] (local build)
Copyright (C) 2002-10 by Bruce Allen, http://smartmontools.sourceforge.net

=== START OF INFORMATION SECTION ===
Model Family: Western Digital Caviar Green (Adv. Format) family
Device Model: WDC WD20EARS-00MVWB0
Serial Number: WD-WCAZA6281995
Firmware Version: 51.0AB51
User Capacity: 2,000,398,934,016 bytes
Device is: In smartctl database [for details use: -P show]
ATA Version is: 8
ATA Standard is: Exact ATA specification draft version not indicated
Local Time is: Mon Jul 18 13:45:07 2011 CEST
SMART support is: Available - device has SMART capability.
SMART support is: Enabled

smartctl 5.40 2010-07-12 r3124 [i686-pc-linux-gnu] (local build)
Copyright (C) 2002-10 by Bruce Allen, http://smartmontools.sourceforge.net

=== START OF INFORMATION SECTION ===
Model Family: Western Digital Caviar Green (Adv. Format) family
Device Model: WDC WD20EARS-00MVWB0
Serial Number: WD-WCAZA5510079
Firmware Version: 51.0AB51
User Capacity: 2,000,398,934,016 bytes
Device is: In smartctl database [for details use: -P show]
ATA Version is: 8
ATA Standard is: Exact ATA specification draft version not indicated
Local Time is: Mon Jul 18 13:45:12 2011 CEST
SMART support is: Available - device has SMART capability.
SMART support is: Enabled

--Boundary-00=_lECJOkJ+W+9lhYH
Content-Type: text/plain;
charset="utf-8";
name="mdadm.conf"
Content-Transfer-Encoding: 7bit
Content-Disposition: attachment;
filename="mdadm.conf"

# mdadm.conf
#
# Please refer to mdadm.conf(5) for information about this file.
#

# by default, scan all partitions (/proc/partitions) for MD superblocks.
# alternatively, specify devices to scan, using wildcards if desired.
DEVICE partitions

# auto-create devices with Debian standard permissions
CREATE owner=root group=disk mode=0660 auto=yes

# automatically tag new arrays as belonging to the local system
HOMEHOST

# instruct the monitoring daemon where to send mail alerts
MAILADDR pol@yahoo.it

# definitions of existing MD arrays

# This file was auto-generated on Fri, 08 Jul 2011 14:37:51 -0700
# by mkconf 3.1.4-1+8efb9d1


--Boundary-00=_lECJOkJ+W+9lhYH
Content-Type: text/plain;
charset="utf-8";
name="sdb"
Content-Transfer-Encoding: 7bit
Content-Disposition: attachment;
filename="sdb"

smartctl 5.40 2010-07-12 r3124 [i686-pc-linux-gnu] (local build)
Copyright (C) 2002-10 by Bruce Allen, http://smartmontools.sourceforge.net

=== START OF INFORMATION SECTION ===
Model Family: Seagate Barracuda 7200.11 family
Device Model: ST31500341AS
Serial Number: 9VS4PSG9
Firmware Version: CC1H
User Capacity: 1,500,301,910,016 bytes
Device is: In smartctl database [for details use: -P show]
ATA Version is: 8
ATA Standard is: ATA-8-ACS revision 4
Local Time is: Mon Jul 18 13:44:52 2011 CEST
SMART support is: Available - device has SMART capability.
SMART support is: Enabled


--Boundary-00=_lECJOkJ+W+9lhYH
Content-Type: text/plain;
charset="utf-8";
name="mdadm-d"
Content-Transfer-Encoding: 7bit
Content-Disposition: attachment;
filename="mdadm-d"

/dev/md0:
Version : 1.2
Creation Time : Fri Jul 8 23:52:13 2011
Raid Level : raid5
Array Size : 5860538368 (5589.05 GiB 6001.19 GB)
Used Dev Size : 1465134592 (1397.26 GiB 1500.30 GB)
Raid Devices : 5
Total Devices : 5
Persistence : Superblock is persistent

Update Time : Mon Jul 18 13:14:04 2011
State : active, resyncing
Active Devices : 5
Working Devices : 5
Failed Devices : 0
Spare Devices : 0

Layout : left-symmetric
Chunk Size : 512K

Rebuild Status : 33% complete

Name : smooth:0 (local to host smooth)
UUID : bfca3ad6:a7df5fa5:20ba4933:55fd4181
Events : 6212

Number Major Minor RaidDevice State
0 8 64 0 active sync /dev/sde
1 8 97 1 active sync /dev/sdg1
2 8 113 2 active sync /dev/sdh1
3 8 129 3 active sync /dev/sdi1
5 8 81 4 active sync /dev/sdf1

--Boundary-00=_lECJOkJ+W+9lhYH
Content-Type: text/plain;
charset="utf-8";
name="sdc"
Content-Transfer-Encoding: 7bit
Content-Disposition: attachment;
filename="sdc"

smartctl 5.40 2010-07-12 r3124 [i686-pc-linux-gnu] (local build)
Copyright (C) 2002-10 by Bruce Allen, http://smartmontools.sourceforge.net

=== START OF INFORMATION SECTION ===
Model Family: Seagate Barracuda 7200.11 family
Device Model: ST31500341AS
Serial Number: 9VS3KL49
Firmware Version: CC1H
User Capacity: 1,500,301,910,016 bytes
Device is: In smartctl database [for details use: -P show]
ATA Version is: 8
ATA Standard is: ATA-8-ACS revision 4
Local Time is: Mon Jul 18 13:45:00 2011 CEST
SMART support is: Available - device has SMART capability.
SMART support is: Enabled


--Boundary-00=_lECJOkJ+W+9lhYH
Content-Type: text/plain;
charset="utf-8";
name="lspci"
Content-Transfer-Encoding: 7bit
Content-Disposition: attachment;
filename="lspci"

00:00.0 Host bridge: Intel Corporation 5520 I/O Hub to ESI Port (rev 22)
Subsystem: Super Micro Computer Inc Device a880
Flags: fast devsel
Capabilities: [60] MSI: Enable- Count=1/2 Maskable+ 64bit-
Capabilities: [90] Express Root Port (Slot-), MSI 00
Capabilities: [e0] Power Management version 3
Capabilities: [100] Advanced Error Reporting
Capabilities: [150] Access Control Services
Capabilities: [160] Vendor Specific Information: ID=0002 Rev=0 Len=00c

00:01.0 PCI bridge: Intel Corporation 5520/5500/X58 I/O Hub PCI Express Root Port 1 (rev 22) (prog-if 00 [Normal decode])
Flags: bus master, fast devsel, latency 0
Bus: primary=00, secondary=07, subordinate=07, sec-latency=0
Capabilities: [40] Subsystem: Super Micro Computer Inc Device a880
Capabilities: [60] MSI: Enable+ Count=1/2 Maskable+ 64bit-
Capabilities: [90] Express Root Port (Slot+), MSI 00
Capabilities: [e0] Power Management version 3
Capabilities: [100] Advanced Error Reporting
Capabilities: [150] Access Control Services
Capabilities: [160] Vendor Specific Information: ID=0002 Rev=0 Len=00c
Kernel driver in use: pcieport

00:03.0 PCI bridge: Intel Corporation 5520/5500/X58 I/O Hub PCI Express Root Port 3 (rev 22) (prog-if 00 [Normal decode])
Flags: bus master, fast devsel, latency 0
Bus: primary=00, secondary=06, subordinate=06, sec-latency=0
I/O behind bridge: 0000e000-0000efff
Memory behind bridge: faf00000-faffffff
Prefetchable memory behind bridge: 00000000d8000000-00000000dfffffff
Capabilities: [40] Subsystem: Super Micro Computer Inc Device a880
Capabilities: [60] MSI: Enable+ Count=1/2 Maskable+ 64bit-
Capabilities: [90] Express Root Port (Slot+), MSI 00
Capabilities: [e0] Power Management version 3
Capabilities: [100] Advanced Error Reporting
Capabilities: [150] Access Control Services
Capabilities: [160] Vendor Specific Information: ID=0002 Rev=0 Len=00c
Kernel driver in use: pcieport

00:07.0 PCI bridge: Intel Corporation 5520/5500/X58 I/O Hub PCI Express Root Port 7 (rev 22) (prog-if 00 [Normal decode])
Flags: bus master, fast devsel, latency 0
Bus: primary=00, secondary=05, subordinate=05, sec-latency=0
Capabilities: [40] Subsystem: Super Micro Computer Inc Device a880
Capabilities: [60] MSI: Enable+ Count=1/2 Maskable+ 64bit-
Capabilities: [90] Express Root Port (Slot+), MSI 00
Capabilities: [e0] Power Management version 3
Capabilities: [100] Advanced Error Reporting
Capabilities: [150] Access Control Services
Capabilities: [160] Vendor Specific Information: ID=0002 Rev=0 Len=00c
Kernel driver in use: pcieport

00:0e.0 Host bridge: Intel Corporation Device 341c (rev 22)
Flags: fast devsel
Capabilities: [40] Express Root Complex Integrated Endpoint, MSI 00
Capabilities: [60] #00 [0000]
Capabilities: [100] Vendor Specific Information: ID=0001 Rev=0 Len=0b8

00:0e.1 Host bridge: Intel Corporation Device 341d (rev 22)
Flags: fast devsel
Capabilities: [40] Express Root Complex Integrated Endpoint, MSI 00
Capabilities: [60] #00 [0000]

00:0e.2 Host bridge: Intel Corporation Device 341e (rev 22)
Flags: fast devsel
Capabilities: [40] Express Root Complex Integrated Endpoint, MSI 00
Capabilities: [60] #00 [0000]

00:13.0 PIC: Intel Corporation 5520/5500/X58 I/O Hub I/OxAPIC Interrupt Controller (rev 22) (prog-if 20 [IO(X)-APIC])
Flags: bus master, fast devsel, latency 0
Memory at fec8a000 (32-bit, non-prefetchable) [size=4K]
Capabilities: [6c] Power Management version 3

00:14.0 PIC: Intel Corporation 5520/5500/X58 I/O Hub System Management Registers (rev 22) (prog-if 00 [8259])
Flags: fast devsel
Capabilities: [40] Express Root Complex Integrated Endpoint, MSI 00

00:14.1 PIC: Intel Corporation 5520/5500/X58 I/O Hub GPIO and Scratch Pad Registers (rev 22) (prog-if 00 [8259])
Flags: fast devsel
Capabilities: [40] Express Root Complex Integrated Endpoint, MSI 00

00:14.2 PIC: Intel Corporation 5520/5500/X58 I/O Hub Control Status and RAS Registers (rev 22) (prog-if 00 [8259])
Flags: fast devsel
Capabilities: [40] Express Root Complex Integrated Endpoint, MSI 00

00:14.3 PIC: Intel Corporation 5520/5500/X58 I/O Hub Throttle Registers (rev 22) (prog-if 00 [8259])
Flags: fast devsel

00:16.0 System peripheral: Intel Corporation 5520/5500/X58 Chipset QuickData Technology Device (rev 22)
Subsystem: Super Micro Computer Inc Device a880
Flags: bus master, fast devsel, latency 0, IRQ 43
Memory at faaec000 (64-bit, non-prefetchable) [size=16K]
Capabilities: [80] MSI-X: Enable+ Count=1 Masked-
Capabilities: [90] Express Root Complex Integrated Endpoint, MSI 00
Capabilities: [e0] Power Management version 3
Kernel driver in use: ioatdma

00:16.1 System peripheral: Intel Corporation 5520/5500/X58 Chipset QuickData Technology Device (rev 22)
Subsystem: Super Micro Computer Inc Device a880
Flags: bus master, fast devsel, latency 0, IRQ 44
Memory at faae8000 (64-bit, non-prefetchable) [size=16K]
Capabilities: [80] MSI-X: Enable+ Count=1 Masked-
Capabilities: [90] Express Root Complex Integrated Endpoint, MSI 00
Capabilities: [e0] Power Management version 3
Kernel driver in use: ioatdma

00:16.2 System peripheral: Intel Corporation 5520/5500/X58 Chipset QuickData Technology Device (rev 22)
Subsystem: Super Micro Computer Inc Device a880
Flags: bus master, fast devsel, latency 0, IRQ 45
Memory at faae4000 (64-bit, non-prefetchable) [size=16K]
Capabilities: [80] MSI-X: Enable+ Count=1 Masked-
Capabilities: [90] Express Root Complex Integrated Endpoint, MSI 00
Capabilities: [e0] Power Management version 3
Kernel driver in use: ioatdma

00:16.3 System peripheral: Intel Corporation 5520/5500/X58 Chipset QuickData Technology Device (rev 22)
Subsystem: Super Micro Computer Inc Device a880
Flags: bus master, fast devsel, latency 0, IRQ 46
Memory at faae0000 (64-bit, non-prefetchable) [size=16K]
Capabilities: [80] MSI-X: Enable+ Count=1 Masked-
Capabilities: [90] Express Root Complex Integrated Endpoint, MSI 00
Capabilities: [e0] Power Management version 3
Kernel driver in use: ioatdma

00:16.4 System peripheral: Intel Corporation 5520/5500/X58 Chipset QuickData Technology Device (rev 22)
Subsystem: Super Micro Computer Inc Device a880
Flags: bus master, fast devsel, latency 0, IRQ 43
Memory at faadc000 (64-bit, non-prefetchable) [size=16K]
Capabilities: [80] MSI-X: Enable+ Count=1 Masked-
Capabilities: [90] Express Root Complex Integrated Endpoint, MSI 00
Capabilities: [e0] Power Management version 3
Kernel driver in use: ioatdma

00:16.5 System peripheral: Intel Corporation 5520/5500/X58 Chipset QuickData Technology Device (rev 22)
Subsystem: Super Micro Computer Inc Device a880
Flags: bus master, fast devsel, latency 0, IRQ 44
Memory at faad8000 (64-bit, non-prefetchable) [size=16K]
Capabilities: [80] MSI-X: Enable+ Count=1 Masked-
Capabilities: [90] Express Root Complex Integrated Endpoint, MSI 00
Capabilities: [e0] Power Management version 3
Kernel driver in use: ioatdma

00:16.6 System peripheral: Intel Corporation 5520/5500/X58 Chipset QuickData Technology Device (rev 22)
Subsystem: Super Micro Computer Inc Device a880
Flags: bus master, fast devsel, latency 0, IRQ 45
Memory at faad4000 (64-bit, non-prefetchable) [size=16K]
Capabilities: [80] MSI-X: Enable+ Count=1 Masked-
Capabilities: [90] Express Root Complex Integrated Endpoint, MSI 00
Capabilities: [e0] Power Management version 3
Kernel driver in use: ioatdma

00:16.7 System peripheral: Intel Corporation 5520/5500/X58 Chipset QuickData Technology Device (rev 22)
Subsystem: Super Micro Computer Inc Device a880
Flags: bus master, fast devsel, latency 0, IRQ 46
Memory at faad0000 (64-bit, non-prefetchable) [size=16K]
Capabilities: [80] MSI-X: Enable+ Count=1 Masked-
Capabilities: [90] Express Root Complex Integrated Endpoint, MSI 00
Capabilities: [e0] Power Management version 3
Kernel driver in use: ioatdma

00:1a.0 USB Controller: Intel Corporation 82801JI (ICH10 Family) USB UHCI Controller #4 (prog-if 00 [UHCI])
Subsystem: Super Micro Computer Inc Device a880
Flags: bus master, medium devsel, latency 0, IRQ 16
I/O ports at aea0 [size=32]
Capabilities: [50] PCI Advanced Features
Kernel driver in use: uhci_hcd

00:1a.1 USB Controller: Intel Corporation 82801JI (ICH10 Family) USB UHCI Controller #5 (prog-if 00 [UHCI])
Subsystem: Super Micro Computer Inc Device a880
Flags: bus master, medium devsel, latency 0, IRQ 21
I/O ports at ae80 [size=32]
Capabilities: [50] PCI Advanced Features
Kernel driver in use: uhci_hcd

00:1a.2 USB Controller: Intel Corporation 82801JI (ICH10 Family) USB UHCI Controller #6 (prog-if 00 [UHCI])
Subsystem: Super Micro Computer Inc Device a880
Flags: bus master, medium devsel, latency 0, IRQ 19
I/O ports at ae20 [size=32]
Capabilities: [50] PCI Advanced Features
Kernel driver in use: uhci_hcd

00:1a.7 USB Controller: Intel Corporation 82801JI (ICH10 Family) USB2 EHCI Controller #2 (prog-if 20 [EHCI])
Subsystem: Super Micro Computer Inc Device a880
Flags: bus master, medium devsel, latency 0, IRQ 18
Memory at faaf4000 (32-bit, non-prefetchable) [size=1K]
Capabilities: [50] Power Management version 2
Capabilities: [58] Debug port: BAR=1 offset=00a0
Capabilities: [98] PCI Advanced Features
Kernel driver in use: ehci_hcd

00:1b.0 Audio device: Intel Corporation 82801JI (ICH10 Family) HD Audio Controller
Subsystem: Super Micro Computer Inc Device a880
Flags: bus master, fast devsel, latency 0, IRQ 81
Memory at faaf0000 (64-bit, non-prefetchable) [size=16K]
Capabilities: [50] Power Management version 2
Capabilities: [60] MSI: Enable+ Count=1/1 Maskable- 64bit+
Capabilities: [70] Express Root Complex Integrated Endpoint, MSI 00
Capabilities: [100] Virtual Channel
Capabilities: [130] Root Complex Link
Kernel driver in use: HDA Intel

00:1c.0 PCI bridge: Intel Corporation 82801JI (ICH10 Family) PCI Express Root Port 1 (prog-if 00 [Normal decode])
Flags: bus master, fast devsel, latency 0
Bus: primary=00, secondary=02, subordinate=02, sec-latency=0
I/O behind bridge: 00001000-00001fff
Memory behind bridge: c0400000-c05fffff
Prefetchable memory behind bridge: 00000000c0600000-00000000c07fffff
Capabilities: [40] Express Root Port (Slot+), MSI 00
Capabilities: [80] MSI: Enable+ Count=1/1 Maskable- 64bit-
Capabilities: [90] Subsystem: Super Micro Computer Inc Device a880
Capabilities: [a0] Power Management version 2
Capabilities: [100] Virtual Channel
Capabilities: [180] Root Complex Link
Kernel driver in use: pcieport

00:1c.4 PCI bridge: Intel Corporation 82801JI (ICH10 Family) PCI Express Root Port 5 (prog-if 00 [Normal decode])
Flags: bus master, fast devsel, latency 0
Bus: primary=00, secondary=03, subordinate=03, sec-latency=0
I/O behind bridge: 0000c000-0000cfff
Memory behind bridge: fad00000-fadfffff
Prefetchable memory behind bridge: 00000000c0200000-00000000c03fffff
Capabilities: [40] Express Root Port (Slot+), MSI 00
Capabilities: [80] MSI: Enable+ Count=1/1 Maskable- 64bit-
Capabilities: [90] Subsystem: Super Micro Computer Inc Device a880
Capabilities: [a0] Power Management version 2
Capabilities: [100] Virtual Channel
Capabilities: [180] Root Complex Link
Kernel driver in use: pcieport

00:1c.5 PCI bridge: Intel Corporation 82801JI (ICH10 Family) PCI Express Root Port 6 (prog-if 00 [Normal decode])
Flags: bus master, fast devsel, latency 0
Bus: primary=00, secondary=04, subordinate=04, sec-latency=0
I/O behind bridge: 0000d000-0000dfff
Memory behind bridge: fae00000-faefffff
Prefetchable memory behind bridge: 00000000c0000000-00000000c01fffff
Capabilities: [40] Express Root Port (Slot+), MSI 00
Capabilities: [80] MSI: Enable+ Count=1/1 Maskable- 64bit-
Capabilities: [90] Subsystem: Super Micro Computer Inc Device a880
Capabilities: [a0] Power Management version 2
Capabilities: [100] Virtual Channel
Capabilities: [180] Root Complex Link
Kernel driver in use: pcieport

00:1d.0 USB Controller: Intel Corporation 82801JI (ICH10 Family) USB UHCI Controller #1 (prog-if 00 [UHCI])
Subsystem: Super Micro Computer Inc Device a880
Flags: bus master, medium devsel, latency 0, IRQ 23
I/O ports at af20 [size=32]
Capabilities: [50] PCI Advanced Features
Kernel driver in use: uhci_hcd

00:1d.1 USB Controller: Intel Corporation 82801JI (ICH10 Family) USB UHCI Controller #2 (prog-if 00 [UHCI])
Subsystem: Super Micro Computer Inc Device a880
Flags: bus master, medium devsel, latency 0, IRQ 19
I/O ports at af00 [size=32]
Capabilities: [50] PCI Advanced Features
Kernel driver in use: uhci_hcd

00:1d.2 USB Controller: Intel Corporation 82801JI (ICH10 Family) USB UHCI Controller #3 (prog-if 00 [UHCI])
Subsystem: Super Micro Computer Inc Device a880
Flags: bus master, medium devsel, latency 0, IRQ 18
I/O ports at aec0 [size=32]
Capabilities: [50] PCI Advanced Features
Kernel driver in use: uhci_hcd

00:1d.7 USB Controller: Intel Corporation 82801JI (ICH10 Family) USB2 EHCI Controller #1 (prog-if 20 [EHCI])
Subsystem: Super Micro Computer Inc Device a880
Flags: bus master, medium devsel, latency 0, IRQ 23
Memory at faaf6000 (32-bit, non-prefetchable) [size=1K]
Capabilities: [50] Power Management version 2
Capabilities: [58] Debug port: BAR=1 offset=00a0
Capabilities: [98] PCI Advanced Features
Kernel driver in use: ehci_hcd

00:1e.0 PCI bridge: Intel Corporation 82801 PCI Bridge (rev 90) (prog-if 01 [Subtractive decode])
Flags: bus master, fast devsel, latency 0
Bus: primary=00, secondary=01, subordinate=01, sec-latency=32
I/O behind bridge: 0000b000-0000bfff
Memory behind bridge: fab00000-facfffff
Capabilities: [50] Subsystem: Super Micro Computer Inc Device a880

00:1f.0 ISA bridge: Intel Corporation 82801JIR (ICH10R) LPC Interface Controller
Subsystem: Super Micro Computer Inc Device a880
Flags: bus master, medium devsel, latency 0
Capabilities: [e0] Vendor Specific Information: Len=0c

00:1f.2 SATA controller: Intel Corporation 82801JI (ICH10 Family) SATA AHCI Controller (prog-if 01 [AHCI 1.0])
Subsystem: Super Micro Computer Inc Device a880
Flags: bus master, 66MHz, medium devsel, latency 0, IRQ 71
I/O ports at aff0 [size=8]
I/O ports at afac [size=4]
I/O ports at afe0 [size=8]
I/O ports at afa8 [size=4]
I/O ports at af80 [size=32]
Memory at faafe000 (32-bit, non-prefetchable) [size=2K]
Capabilities: [80] MSI: Enable+ Count=1/16 Maskable- 64bit-
Capabilities: [70] Power Management version 3
Capabilities: [a8] SATA HBA v1.0
Capabilities: [b0] PCI Advanced Features
Kernel driver in use: ahci

00:1f.3 SMBus: Intel Corporation 82801JI (ICH10 Family) SMBus Controller
Subsystem: Super Micro Computer Inc Device a880
Flags: medium devsel, IRQ 18
Memory at faafc000 (64-bit, non-prefetchable) [size=256]
I/O ports at 0400 [size=32]
Kernel driver in use: i801_smbus

01:02.0 FireWire (IEEE 1394): Texas Instruments TSB43AB22/A IEEE-1394a-2000 Controller (PHY/Link) (prog-if 10 [OHCI])
Subsystem: Super Micro Computer Inc Device 1411
Flags: bus master, medium devsel, latency 64, IRQ 18
Memory at fabf7800 (32-bit, non-prefetchable) [size=2K]
Memory at fabf8000 (32-bit, non-prefetchable) [size=16K]
Capabilities: [44] Power Management version 2
Kernel driver in use: firewire_ohci

01:05.0 RAID bus controller: Silicon Image, Inc. SiI 3114 [SATALink/SATARaid] Serial ATA Controller (rev 02)
Subsystem: Silicon Image, Inc. Device 7114
Flags: bus master, 66MHz, medium devsel, latency 64, IRQ 19
I/O ports at bb90 [size=8]
I/O ports at bb88 [size=4]
I/O ports at bb98 [size=8]
I/O ports at bb8c [size=4]
I/O ports at bba0 [size=16]
Memory at fabffc00 (32-bit, non-prefetchable) [size=1K]
Expansion ROM at fac00000 [disabled] [size=512K]
Capabilities: [60] Power Management version 2
Kernel driver in use: sata_sil

01:06.0 Ethernet controller: 3Com Corporation 3c905C-TX/TX-M [Tornado] (rev 78)
Subsystem: 3Com Corporation 3C905CX-TX/TX-M Fast Etherlink for PC Management NIC
Flags: bus master, medium devsel, latency 64, IRQ 17
I/O ports at bc00 [size=128]
Memory at facdfc00 (32-bit, non-prefetchable) [size=128]
Expansion ROM at face0000 [disabled] [size=128K]
Capabilities: [dc] Power Management version 2
Kernel driver in use: 3c59x

03:00.0 Ethernet controller: Intel Corporation 82573E Gigabit Ethernet Controller (Copper) (rev 03)
Subsystem: Super Micro Computer Inc Device 108c
Flags: bus master, fast devsel, latency 0, IRQ 70
Memory at fade0000 (32-bit, non-prefetchable) [size=128K]
I/O ports at cf80 [size=32]
Capabilities: [c8] Power Management version 2
Capabilities: [d0] MSI: Enable+ Count=1/1 Maskable- 64bit+
Capabilities: [e0] Express Endpoint, MSI 00
Capabilities: [100] Advanced Error Reporting
Capabilities: [140] Device Serial Number 00-25-90-ff-ff-24-d1-e4
Kernel driver in use: e1000e

04:00.0 Ethernet controller: Intel Corporation 82573L Gigabit Ethernet Controller
Subsystem: Super Micro Computer Inc Device 109a
Flags: bus master, fast devsel, latency 0, IRQ 72
Memory at faee0000 (32-bit, non-prefetchable) [size=128K]
I/O ports at df80 [size=32]
Capabilities: [c8] Power Management version 2
Capabilities: [d0] MSI: Enable+ Count=1/1 Maskable- 64bit+
Capabilities: [e0] Express Endpoint, MSI 00
Capabilities: [100] Advanced Error Reporting
Capabilities: [140] Device Serial Number 00-25-90-ff-ff-24-d1-e5
Kernel driver in use: e1000e

06:00.0 VGA compatible controller: ATI Technologies Inc RV370 5B60 [Radeon X300 (PCIE)] (prog-if 00 [VGA controller])
Subsystem: PC Partner Limited Radeon X300 (PCIE)
Flags: bus master, fast devsel, latency 0, IRQ 11
Memory at d8000000 (32-bit, prefetchable) [size=128M]
I/O ports at e000 [size=256]
Memory at fafd0000 (32-bit, non-prefetchable) [size=64K]
Expansion ROM at fafe0000 [disabled] [size=128K]
Capabilities: [50] Power Management version 2
Capabilities: [58] Express Endpoint, MSI 00
Capabilities: [80] MSI: Enable- Count=1/1 Maskable- 64bit+
Capabilities: [100] Advanced Error Reporting

06:00.1 Display controller: ATI Technologies Inc RV370 [Radeon X300SE]
Subsystem: PC Partner Limited Radeon X300SE
Flags: bus master, fast devsel, latency 0
Memory at fafc0000 (32-bit, non-prefetchable) [size=64K]
Capabilities: [50] Power Management version 2
Capabilities: [58] Express Endpoint, MSI 00


--Boundary-00=_lECJOkJ+W+9lhYH
Content-Type: text/plain;
charset="utf-8";
name="sde"
Content-Transfer-Encoding: 7bit
Content-Disposition: attachment;
filename="sde"

smartctl 5.40 2010-07-12 r3124 [i686-pc-linux-gnu] (local build)
Copyright (C) 2002-10 by Bruce Allen, http://smartmontools.sourceforge.net

=== START OF INFORMATION SECTION ===
Model Family: Western Digital Caviar Green (Adv. Format) family
Device Model: WDC WD20EARS-00MVWB0
Serial Number: WD-WCAZA6281995
Firmware Version: 51.0AB51
User Capacity: 2,000,398,934,016 bytes
Device is: In smartctl database [for details use: -P show]
ATA Version is: 8
ATA Standard is: Exact ATA specification draft version not indicated
Local Time is: Mon Jul 18 13:45:07 2011 CEST
SMART support is: Available - device has SMART capability.
SMART support is: Enabled


--Boundary-00=_lECJOkJ+W+9lhYH
Content-Type: text/plain;
charset="utf-8";
name="sdd"
Content-Transfer-Encoding: 7bit
Content-Disposition: attachment;
filename="sdd"

smartctl 5.40 2010-07-12 r3124 [i686-pc-linux-gnu] (local build)
Copyright (C) 2002-10 by Bruce Allen, http://smartmontools.sourceforge.net

=== START OF INFORMATION SECTION ===
Model Family: Seagate Barracuda 7200.12 family
Device Model: ST3500418AS
Serial Number: 9VM1WK4N
Firmware Version: CC46
User Capacity: 500,107,862,016 bytes
Device is: In smartctl database [for details use: -P show]
ATA Version is: 8
ATA Standard is: ATA-8-ACS revision 4
Local Time is: Mon Jul 18 13:45:03 2011 CEST
SMART support is: Available - device has SMART capability.
SMART support is: Enabled


--Boundary-00=_lECJOkJ+W+9lhYH
Content-Type: text/plain;
charset="utf-8";
name="sdf"
Content-Transfer-Encoding: 7bit
Content-Disposition: attachment;
filename="sdf"

smartctl 5.40 2010-07-12 r3124 [i686-pc-linux-gnu] (local build)
Copyright (C) 2002-10 by Bruce Allen, http://smartmontools.sourceforge.net

=== START OF INFORMATION SECTION ===
Model Family: Western Digital Caviar Green (Adv. Format) family
Device Model: WDC WD20EARS-00MVWB0
Serial Number: WD-WCAZA5510079
Firmware Version: 51.0AB51
User Capacity: 2,000,398,934,016 bytes
Device is: In smartctl database [for details use: -P show]
ATA Version is: 8
ATA Standard is: Exact ATA specification draft version not indicated
Local Time is: Mon Jul 18 13:45:12 2011 CEST
SMART support is: Available - device has SMART capability.
SMART support is: Enabled


--Boundary-00=_lECJOkJ+W+9lhYH--
--
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

Re: standard performance (write speed 20Mb/s)

On 7/18/2011 7:03 AM, Pol Hallen wrote:
>> Then you have multiple problems causing poor performance. Now is the
>> time for you to post your hardware configuration, drive model
>> number(s), mdadm config, and filesystem. You should have done all of
>> this in your initial post.
>
> hello and sorry for the late :-(
>
> now is a resync in progress, I can't stop it. Try /usr/share/mdadm/checkarray
> -x md0 but nothing..
>
> fs is ext3 (done less 10 days ago)
>
>> You've been on this list long enough to have known of the WD Green
>> sector alignment issue and avoided it, and to know better than to run
>> performance tests while an array is still in its initial sync. Thus I
>> initially assumed your problem was merely the insane dd block size.
>
> when I wrote a post there was not resync in progress..
>
> tell me if you need known other things, thanks

I can't see how. You dumped the entire system. Which is probably why
no one has responded until now. Never provide all this garbage. It
takes too long to sift through and grab the relevant bits, which is only
this:


> Device Model: ST31500341AS
> User Capacity: 1,500,301,910,016 bytes

> Device Model: ST31500341AS
> User Capacity: 1,500,301,910,016 bytes

> Device Model: ST3500418AS
> User Capacity: 500,107,862,016 bytes

> Device Model: WDC WD20EARS-00MVWB0
> User Capacity: 2,000,398,934,016 bytes

> Device Model: WDC WD20EARS-00MVWB0
> User Capacity: 2,000,398,934,016 bytes

This mishmash combo of drives, including two WD Green Advanced Format
drives, is likely the cause of the horrible write performance. You're
assembling the array from partitions. The partitions on the WD20EARS
drives are undoubtedly not 4KB sector aligned, causing excessive
read-modify-write cycles. See:

http://en.wikipedia.org/wiki/Advanced_Format

Repartition the Green drives with proper alignment. If you still have
issues we'll go from there. Note: Having 3 dissimilar drives in an
array is never going to be an optimally performing solution.

--
Stan
--
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

Re: standard performance (write speed 20Mb/s)

> This mishmash combo of drives, including two WD Green Advanced Format
> drives, is likely the cause of the horrible write performance. You're
> assembling the array from partitions.

first of all: sorry but my english is not good :-(

In many howto I read:

"create a partition of disk and change it to "fd" code: linux raid
autodetect"

Now I re-done whole raid (I already have a backup)

I have to create a partition on sigle disk? or remove any partition and stop?

> The partitions on the WD20EARS
> drives are undoubtedly not 4KB sector aligned, causing excessive
> read-modify-write cycles. See:
> http://en.wikipedia.org/wiki/Advanced_Format
> Repartition the Green drives with proper alignment. If you still have
> issues we'll go from there. Note: Having 3 dissimilar drives in an
> array is never going to be an optimally performing solution.

Now I re-create a new raid system with 6 disks (everyone 2Tb wd)

How do about 4Kb sector align?

thanks!

Pol

--
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

Re: standard performance (write speed 20Mb/s)

On 7/20/2011 3:17 PM, Mathias Burén wrote:

> FWIW this is my RAID6 setup:
>=20
> $ sudo fdisk -l /dev/sd[b,c,d,e,f,g,h]
> Password:

Are these indeed advanced format drives? You didn't provide model#s or
manufacturer product line. The only clue we have that they might be AF
drives is the 2048 offset you created. Unless I simply missed it.

> Disk /dev/sdb: 2000.4 GB, 2000398934016 bytes
> 81 heads, 63 sectors/track, 765633 cylinders, total 3907029168 sector=
s
> Units =3D sectors of 1 * 512 =3D 512 bytes
> Sector size (logical/physical): 512 bytes / 512 bytes
> I/O size (minimum/optimal): 512 bytes / 512 bytes
> Disk identifier: 0x0e5b3a7a
>=20
> Device Boot Start End Blocks Id System
> /dev/sdb1 2048 3907029167 1953513560 fd Linux raid
> autodetect
>=20
> Disk /dev/sdc: 2000.4 GB, 2000398934016 bytes
> 81 heads, 63 sectors/track, 765633 cylinders, total 3907029168 sector=
s
> Units =3D sectors of 1 * 512 =3D 512 bytes
> Sector size (logical/physical): 512 bytes / 512 bytes
> I/O size (minimum/optimal): 512 bytes / 512 bytes
> Disk identifier: 0x4fc36d54
>=20
> Device Boot Start End Blocks Id System
> /dev/sdc1 2048 3907029167 1953513560 fd Linux raid
> autodetect
>=20
> Disk /dev/sdd: 2000.4 GB, 2000398934016 bytes
> 81 heads, 63 sectors/track, 765633 cylinders, total 3907029168 sector=
s
> Units =3D sectors of 1 * 512 =3D 512 bytes
> Sector size (logical/physical): 512 bytes / 512 bytes
> I/O size (minimum/optimal): 512 bytes / 512 bytes
> Disk identifier: 0x9e716ecb
>=20
> Device Boot Start End Blocks Id System
> /dev/sdd1 2048 3907029167 1953513560 fd Linux raid
> autodetect
>=20
> Disk /dev/sde: 2000.4 GB, 2000398934016 bytes
> 81 heads, 63 sectors/track, 765633 cylinders, total 3907029168 sector=
s
> Units =3D sectors of 1 * 512 =3D 512 bytes
> Sector size (logical/physical): 512 bytes / 512 bytes
> I/O size (minimum/optimal): 512 bytes / 512 bytes
> Disk identifier: 0x629ab77f
>=20
> Device Boot Start End Blocks Id System
> /dev/sde1 2048 3907029167 1953513560 fd Linux raid
> autodetect
>=20
> Disk /dev/sdf: 2000.4 GB, 2000398934016 bytes
> 123 heads, 18 sectors/track, 1764692 cylinders, total 3907029168 sect=
ors
> Units =3D sectors of 1 * 512 =3D 512 bytes
> Sector size (logical/physical): 512 bytes / 512 bytes
> I/O size (minimum/optimal): 512 bytes / 512 bytes
> Disk identifier: 0x3d454f20
>=20
> Device Boot Start End Blocks Id System
> /dev/sdf1 2048 3907029167 1953513560 fd Linux raid
> autodetect
>=20
> Disk /dev/sdg: 2000.4 GB, 2000398934016 bytes
> 81 heads, 63 sectors/track, 765633 cylinders, total 3907029168 sector=
s
> Units =3D sectors of 1 * 512 =3D 512 bytes
> Sector size (logical/physical): 512 bytes / 512 bytes
> I/O size (minimum/optimal): 512 bytes / 512 bytes
> Disk identifier: 0x918fae9f
>=20
> Device Boot Start End Blocks Id System
> /dev/sdg1 2048 3907029167 1953513560 fd Linux raid
> autodetect
>=20
> Disk /dev/sdh: 2000.4 GB, 2000398934016 bytes
> 123 heads, 18 sectors/track, 1764692 cylinders, total 3907029168 sect=
ors
> Units =3D sectors of 1 * 512 =3D 512 bytes
> Sector size (logical/physical): 512 bytes / 512 bytes
> I/O size (minimum/optimal): 512 bytes / 512 bytes
> Disk identifier: 0x0ac81a1b
>=20
> Device Boot Start End Blocks Id System
> /dev/sdh1 2048 3907029167 1953513560 fd Linux raid
> autodetect

--=20
Stan
--
To unsubscribe from this list: send the line "unsubscribe linux-raid" i=
n
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html

Re: standard performance (write speed 20Mb/s)

Yes, sorry. 5 WD20EARS and 2 Samsung 2TB

On Thursday, 21 July 2011, Stan Hoeppner wrote=
:
> On 7/20/2011 3:17 PM, Mathias Burén wrote:
>
>> FWIW this is my RAID6 setup:
>>
>> $ sudo fdisk -l /dev/sd[b,c,d,e,f,g,h]
>> Password:
>
> Are these indeed advanced format drives?  You didn't provide mod=
el#s or
> manufacturer product line.  The only clue we have that they migh=
t be AF
> drives is the 2048 offset you created.  Unless I simply missed i=
t.
>
>> Disk /dev/sdb: 2000.4 GB, 2000398934016 bytes
>> 81 heads, 63 sectors/track, 765633 cylinders, total 3907029168 secto=
rs
>> Units =3D sectors of 1 * 512 =3D 512 bytes
>> Sector size (logical/physical): 512 bytes / 512 bytes
>> I/O size (minimum/optimal): 512 bytes / 512 bytes
>> Disk identifier: 0x0e5b3a7a
>>
>>    Device Boot      Start     =C2=
=A0   End      Blocks   Id  System
>> /dev/sdb1            2048  390702=
9167  1953513560   fd  Linux raid
>> autodetect
>>
>> Disk /dev/sdc: 2000.4 GB, 2000398934016 bytes
>> 81 heads, 63 sectors/track, 765633 cylinders, total 3907029168 secto=
rs
>> Units =3D sectors of 1 * 512 =3D 512 bytes
>> Sector size (logical/physical): 512 bytes / 512 bytes
>> I/O size (minimum/optimal): 512 bytes / 512 bytes
>> Disk identifier: 0x4fc36d54
>>
>>    Device Boot      Start     =C2=
=A0   End      Blocks   Id  System
>> /dev/sdc1            2048  390702=
9167  1953513560   fd  Linux raid
>> autodetect
>>
>> Disk /dev/sdd: 2000.4 GB, 2000398934016 bytes
>> 81 heads, 63 sectors/track, 765633 cylinders, total 3907029168 secto=
rs
>> Units =3D sectors of 1 * 512 =3D 512 bytes
>> Sector size (logical/physical): 512 bytes / 512 bytes
>> I/O size (minimum/optimal): 512 bytes / 512 bytes
>> Disk identifier: 0x9e716ecb
>>
>>    Device Boot      Start     =C2=
=A0   End      Blocks   Id  System
>> /dev/sdd1            2048  390702=
9167  1953513560   fd  Linux raid
>> autodetect
>>
>> Disk /dev/sde: 2000.4 GB, 2000398934016 bytes
>> 81 heads, 63 sectors/track, 765633 cylinders, total 3907029168 secto=
rs
>> Units =3D sectors of 1 * 512 =3D 512 bytes
>> Sector size (logical/physical): 512 bytes / 512 bytes
>> I/O size (minimum/optimal): 512 bytes / 512 bytes
>> Disk identifier: 0x629ab77f
>>
>>    Device Boot      Start     =C2=
=A0   End      Blocks   Id  System
>> /dev/sde1            2048  390702=
9167  1953513560   fd  Linux raid
>> autodetect
>>
>> Disk /dev/sdf: 2000.4 GB, 2000398934016 bytes
>> 123 heads, 18 sectors/track, 1764692 cylinders, total 3907029168 sec=
tors
>> Units =3D sectors of 1 * 512 =3D 512 bytes
>> Sector size (logical/physical): 512 bytes / 512 bytes
>> I/O size (minimum/optimal): 512 bytes / 512 bytes
>> Disk identifier: 0x3d454f20
>>
>>    Device Boot      Start     =C2=
=A0   End      Blocks   Id  System
>> /dev/sdf1            2048  390702=
9167  1953513560   fd  Linux raid
>> autodetect
>>
>> Disk /dev/sdg: 2000.4 GB, 2000398934016 bytes
>> 81 heads, 63 sectors/track, 765633 cylinders, total 3907029168 secto=
rs
>> Units =3D sectors of 1 * 512 =3D 512 bytes
>> Sector size (logical/physical): 512 bytes / 512 bytes
>> I/O size (minimum/optimal): 512 bytes / 512 bytes
>> Disk identifier: 0x918fae9f
>>
>>    Device Boot      Start     =C2=
=A0   End      Blocks   Id  System
>> /dev/sdg1            2048  390702=
9167  1953513560   fd  Linux raid
>> autodetect
>>
>> Disk /dev/sdh: 2000.4 GB, 2000398934016 bytes
>> 123 heads, 18 sectors/track, 1764692 cylinders, total 3907029168 sec=
tors
>> Units =3D sectors of 1 * 512 =3D 512 bytes
>> Sector size (logical/physical): 512 bytes / 512 bytes
>> I/O size (minimum/optimal): 512 bytes / 512 bytes
>> Disk identifier: 0x0ac81a1b
>>
>>    Device Boot      Start     =C2=
=A0   End      Blocks   Id  System
>> /dev/sdh1            2048  390702=
9167  1953513560   fd  Linux raid
>> autodetect
>
> --
> Stan
>
--
To unsubscribe from this list: send the line "unsubscribe linux-raid" i=
n
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html

Re: standard performance (write speed 20Mb/s)

following is how i configured advanced format drives for raid 5
i created one partition on each disk

fdisk -u /dev/sdX
# -u change the unit displayed by fdisk to sector instead of
cylinders, this way it's easier to configure

# the table partition isn't really modifier until you send the w
command, so if you messed up use the q to quit and restart

#delete first partition of the disk, repeat until you had cleared the d=
isk
d

# create a new partition
n

# select primary parition
p

#select number one (don't know if number is important, i guess it's
means /dev/sdX1)
1

#select first sector, here is the catch, to properly align the disk, se=
lect 64
64

#select default for the last sector


# Change type of partition

#https://raid.wiki.kernel.org/index.php/Partition_Types
#according to this link if you use the option --metadata 1.2 with
madadm --create
# it's better to use the type DA (Non-FS data) instead of FD (Linux
raid auto) but i can't found why
# you can stick to FD, it's what is i used
t
DA or FD

# commit the change so double check the setup with the p command before=
do it
w

Repeat the setup for each advanced format drives and you should be good

to show you the result, here is the result of fdisk -l
WARNING: GPT (GUID Partition Table) detected on '/dev/sda'! The util
fdisk doesn't support GPT. Use GNU Parted.


Disk /dev/sda: 2000.4 GB, 2000398934016 bytes
255 heads, 63 sectors/track, 243201 cylinders
Units =3D cylinders of 16065 * 512 =3D 8225280 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk identifier: 0x00000000

Device Boot Start End Blocks Id System
/dev/sda1 1 243202 1953514552 fd Linux raid auto=
detect

WARNING: GPT (GUID Partition Table) detected on '/dev/sdb'! The util
fdisk doesn't support GPT. Use GNU Parted.


Disk /dev/sdb: 2000.4 GB, 2000398934016 bytes
256 heads, 63 sectors/track, 242251 cylinders
Units =3D cylinders of 16128 * 512 =3D 8257536 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk identifier: 0x00000000

Device Boot Start End Blocks Id System
/dev/sdb1 1 242252 1953514552 fd Linux raid auto=
detect

Disk /dev/sdc: 2000.4 GB, 2000398934016 bytes
255 heads, 63 sectors/track, 243201 cylinders
Units =3D cylinders of 16065 * 512 =3D 8225280 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk identifier: 0x78e9148d

Device Boot Start End Blocks Id System
/dev/sdc1 1 243202 1953514552 fd Linux raid auto=
detect

WARNING: GPT (GUID Partition Table) detected on '/dev/sdd'! The util
fdisk doesn't support GPT. Use GNU Parted.


Disk /dev/sdd: 2000.4 GB, 2000398934016 bytes
255 heads, 63 sectors/track, 243201 cylinders
Units =3D cylinders of 16065 * 512 =3D 8225280 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk identifier: 0x00000000

Device Boot Start End Blocks Id System
/dev/sdd1 1 243202 1953514552 fd Linux raid auto=
detect

WARNING: GPT (GUID Partition Table) detected on '/dev/sde'! The util
fdisk doesn't support GPT. Use GNU Parted.


Disk /dev/sde: 2000.4 GB, 2000398934016 bytes
255 heads, 63 sectors/track, 243201 cylinders
Units =3D cylinders of 16065 * 512 =3D 8225280 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk identifier: 0x00000000

Device Boot Start End Blocks Id System
/dev/sde1 1 243202 1953514552 fd Linux raid auto=
detect

WARNING: GPT (GUID Partition Table) detected on '/dev/sdf'! The util
fdisk doesn't support GPT. Use GNU Parted.


Disk /dev/sdf: 2000.4 GB, 2000398934016 bytes
255 heads, 63 sectors/track, 243201 cylinders
Units =3D cylinders of 16065 * 512 =3D 8225280 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk identifier: 0x00000000

Device Boot Start End Blocks Id System
/dev/sdf1 1 243202 1953514552 fd Linux raid auto=
detect

Disk /dev/md0: 10002.0 GB, 10001978490880 bytes
2 heads, 4 sectors/track, -1853078016 cylinders
Units =3D cylinders of 8 * 512 =3D 4096 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 2097152 bytes / 10485760 bytes
Disk identifier: 0x00000000

Disk /dev/md0 doesn't contain a valid partition table


2011/7/20 Pol Hallen
>
> > This mishmash combo of drives, including two WD Green Advanced Form=
at
> > drives, is likely the cause of the horrible write performance. =A0Y=
ou're
> > assembling the array from partitions.
>
> first of all: sorry but my english is not good :-(
>
> In many howto I read:
>
> "create a partition of disk and change it to "fd" code: linux raid
> autodetect"
>
> Now I re-done whole raid (I already have a backup)
>
> I have to create a partition on sigle disk? or remove any partition a=
nd stop?
>
> > =A0The partitions on the WD20EARS
> > drives are undoubtedly not 4KB sector aligned, causing excessive
> > read-modify-write cycles. =A0See:
> > http://en.wikipedia.org/wiki/Advanced_Format
> > Repartition the Green drives with proper alignment. =A0If you still=
have
> > issues we'll go from there. =A0Note: =A0Having 3 dissimilar drives =
in an
> > array is never going to be an optimally performing solution.
>
> Now I re-create a new raid system with 6 disks (everyone 2Tb wd)
>
> How do about 4Kb sector align?
>
> thanks!
>
> Pol
--
To unsubscribe from this list: send the line "unsubscribe linux-raid" i=
n
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html

Re: standard performance (write speed 20Mb/s)

2011/7/21 Erwan Leroux :
> following is how i configured advanced format drives for raid 5
> i created one partition on each disk
>
> fdisk -u /dev/sdX
> # -u change the unit displayed by fdisk to sector instead of
> cylinders, this way it's easier to configure
>
> # the table partition isn't really modifier until you send the w
> command, so if you messed up use the q to quit and restart
>
> #delete first partition of the disk, repeat until you had cleared the=
disk
> d
>
> # create a new partition
> n
>
> # select primary parition
> p
>
> #select number one (don't know if number is important, i guess it's
> means /dev/sdX1)
> 1
>
> #select first sector, here is the catch, to properly align the disk, =
select 64
> 64
>
Why do you choose 64? One physical sector (4KiB) is 8 logical sectors
(512 B). Would any number greater or equal to 8 and evenly divisible
by 8 work as well? Are you aiming to align partition start with RAID
chunk boundaries?

Just curious.

Paweł
--
To unsubscribe from this list: send the line "unsubscribe linux-raid" i=
n
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html

Re: standard performance (write speed 20Mb/s)

It's 64 because it's the lowest sector that is a multiple of 4kB.
sector 63 is the lowest possible
you can see the result of that choice, using sector 64, the
corresponding cylinder is 1, so the drive is well aligned^^
sudo fdisk -l /dev/sda

WARNING: GPT (GUID Partition Table) detected on '/dev/sda'! The util
fdisk doesn
't support GPT. Use GNU Parted.


Disk /dev/sda: 2000.4 GB, 2000398934016 bytes
255 heads, 63 sectors/track, 243201 cylinders
Units =3D cylinders of 16065 * 512 =3D 8225280 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk identifier: 0x00000000

Device Boot Start End Blocks Id System
/dev/sda1 1 243202 1953514552 fd Linux raid auto=
detect

sudo fdisk -lu /dev/sda

WARNING: GPT (GUID Partition Table) detected on '/dev/sda'! The util
fdisk doesn
't support GPT. Use GNU Parted.


Disk /dev/sda: 2000.4 GB, 2000398934016 bytes
255 heads, 63 sectors/track, 243201 cylinders, total 3907029168 sectors
Units =3D sectors of 1 * 512 =3D 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk identifier: 0x00000000

Device Boot Start End Blocks Id System
/dev/sda1 64 3907029167 1953514552 fd Linux raid auto=
detect

i think i found this setting on that page but not really sure
http://ubuntuforums.org/showpost.php?p=3D9134230


2011/7/21 Paweł Brodacki :
> 2011/7/21 Erwan Leroux :
>> following is how i configured advanced format drives for raid 5
>> i created one partition on each disk
>>
>> fdisk -u /dev/sdX
>> # -u change the unit displayed by fdisk to sector instead of
>> cylinders, this way it's easier to configure
>>
>> # the table partition isn't really modifier until you send the w
>> command, so if you messed up use the q to quit and restart
>>
>> #delete first partition of the disk, repeat until you had cleared th=
e disk
>> d
>>
>> # create a new partition
>> n
>>
>> # select primary parition
>> p
>>
>> #select number one (don't know if number is important, i guess it's
>> means /dev/sdX1)
>> 1
>>
>> #select first sector, here is the catch, to properly align the disk,=
select 64
>> 64
>>
> Why do you choose 64? One physical sector (4KiB) is 8 logical sectors
> (512 B). Would any number greater or equal to 8 and evenly divisible
> by 8 work as well? Are you aiming to align partition start with RAID
> chunk boundaries?
>
> Just curious.
>
> Paweł
> --
> 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.ht=
ml
>
--
To unsubscribe from this list: send the line "unsubscribe linux-raid" i=
n
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html

Re: standard performance (write speed 20Mb/s)

I search my bookmarks to find the original source, which has some
benchmark to compare sector 63 and 64
http://linuxconfig.org/linux-wd-ears-advanced-format

2011/7/21 Erwan Leroux :
> It's 64 because it's the lowest sector that is a multiple of 4kB.
> sector 63 is the lowest possible
> you can see the result of that choice, using sector 64, the
> corresponding cylinder is 1, so the drive is well aligned^^
> sudo fdisk -l /dev/sda
>
> WARNING: GPT (GUID Partition Table) detected on '/dev/sda'! The util
> fdisk doesn
>                 't support GP=
T. Use GNU Parted.
>
>
> Disk /dev/sda: 2000.4 GB, 2000398934016 bytes
> 255 heads, 63 sectors/track, 243201 cylinders
> Units =3D cylinders of 16065 * 512 =3D 8225280 bytes
> Sector size (logical/physical): 512 bytes / 512 bytes
> I/O size (minimum/optimal): 512 bytes / 512 bytes
> Disk identifier: 0x00000000
>
>   Device Boot      Start       =C2=
=A0 End      Blocks   Id  System
> /dev/sda1               1   =C2=
=A0  243202  1953514552   fd  Linux raid autodetect
>
> sudo fdisk -lu /dev/sda
>
> WARNING: GPT (GUID Partition Table) detected on '/dev/sda'! The util
> fdisk doesn
>                 't support GP=
T. Use GNU Parted.
>
>
> Disk /dev/sda: 2000.4 GB, 2000398934016 bytes
> 255 heads, 63 sectors/track, 243201 cylinders, total 3907029168 secto=
rs
> Units =3D sectors of 1 * 512 =3D 512 bytes
> Sector size (logical/physical): 512 bytes / 512 bytes
> I/O size (minimum/optimal): 512 bytes / 512 bytes
> Disk identifier: 0x00000000
>
>   Device Boot      Start       =C2=
=A0 End      Blocks   Id  System
> /dev/sda1              64  39=
07029167  1953514552   fd  Linux raid autodetect
>
> i think i found this setting on that page but not really sure
> http://ubuntuforums.org/showpost.php?p=3D9134230
>
>
> 2011/7/21 Paweł Brodacki :
>> 2011/7/21 Erwan Leroux :
>>> following is how i configured advanced format drives for raid 5
>>> i created one partition on each disk
>>>
>>> fdisk -u /dev/sdX
>>> # -u change the unit displayed by fdisk to sector instead of
>>> cylinders, this way it's easier to configure
>>>
>>> # the table partition isn't really modifier until you send the w
>>> command, so if you messed up use the q to quit and restart
>>>
>>> #delete first partition of the disk, repeat until you had cleared t=
he disk
>>> d
>>>
>>> # create a new partition
>>> n
>>>
>>> # select primary parition
>>> p
>>>
>>> #select number one (don't know if number is important, i guess it's
>>> means /dev/sdX1)
>>> 1
>>>
>>> #select first sector, here is the catch, to properly align the disk=
, select 64
>>> 64
>>>
>> Why do you choose 64? One physical sector (4KiB) is 8 logical sector=
s
>> (512 B). Would any number greater or equal to 8 and evenly divisible
>> by 8 work as well? Are you aiming to align partition start with RAID
>> chunk boundaries?
>>
>> Just curious.
>>
>> Paweł
>> --
>> 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.h=
tml
>>
>
--
To unsubscribe from this list: send the line "unsubscribe linux-raid" i=
n
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html

Re: standard performance (write speed ??Mb/s) - new raid5 array

Hello again :-)

I removed all partitions of my disks and do:

dd if=/dev/zero of=/dev/sdb bs=512 count=1 for all disks..

next, I created a new partition (non-fs data) starting of 64 like below (for
every devices)

fdisk -lu /dev/sdb

Disk /dev/sdb: 2000.4 GB, 2000398934016 bytes
255 heads, 63 sectors/track, 243201 cylinders, total 3907029168 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk identifier: 0xd2017c41

Device Boot Start End Blocks Id System
/dev/sdb1 64 3907029167 1953514552 da Non-FS data

created a new raid5 array:

mdadm --create --verbose /dev/md0 --level=raid5 --raid-devices=5 /dev/sdb
/dev/sdc /dev/sdd /dev/sde /dev/sdf

cat /proc/mdstat

md0 : active raid5 sdf[5] sde[3] sdd[2] sdc[1] sdb[0]
7814051840 blocks super 1.2 level 5, 512k chunk, algorithm 2 [5/4]
[UUUU_]
[>....................] recovery = 0.3% (6625324/1953512960)
finish=971.1min speed=33411K/sec

Now, I've 5 identical disks (2Tb WD)

I've to wait rebuilding time after do new tests performance.

The procedure that I've done is correct?

thanks! :-)

Pol
--
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

Re: standard performance (write speed 65Mb/s)

> fdisk -u /dev/sdX
> # -u change the unit displayed by fdisk to sector instead of
> cylinders, this way it's easier to configure
[...]

thanks for guide :-)

after this, my raid5 (rebuilding in progress):

dd if=/dev/zero of=/dev/md0 bs=1024M count=10
10+0 records in
10+0 records out
10737418240 bytes (11 GB) copied, 166.042 s, 64.7 MB/s

Pol
--
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

Re: standard performance (write speed ??Mb/s) - new raid5 array

On 7/21/2011 12:07 PM, Pol Hallen wrote:
> Hello again :-)
>
> I removed all partitions of my disks and do:
>
> dd if=/dev/zero of=/dev/sdb bs=512 count=1 for all disks..
>
> next, I created a new partition (non-fs data) starting of 64 like below (for
> every devices)

Why did you create partitions? The whole point of zeroing the first 512
bytes was to *eliminate* all the partitions...

> Device Boot Start End Blocks Id System
> /dev/sdb1 64 3907029167 1953514552 da Non-FS data
>
> created a new raid5 array:
>
> mdadm --create --verbose /dev/md0 --level=raid5 --raid-devices=5 /dev/sdb
> /dev/sdc /dev/sdd /dev/sde /dev/sdf

And now you create your array without using partitions...

> cat /proc/mdstat
>
> md0 : active raid5 sdf[5] sde[3] sdd[2] sdc[1] sdb[0]
> 7814051840 blocks super 1.2 level 5, 512k chunk, algorithm 2 [5/4]
> [UUUU_]
> [>....................] recovery = 0.3% (6625324/1953512960)
> finish=971.1min speed=33411K/sec

You created aligned partitions on all disks, and then did not use those
partitions...

> Now, I've 5 identical disks (2Tb WD)
>
> I've to wait rebuilding time after do new tests performance.
>
> The procedure that I've done is correct?

No, you did not. It seems you merged bits and pieces from each array
creation method. The array may still function properly. I've never
tried what you've done here. Maybe others have the correct answer.

--
Stan
--
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

Re: standard performance (write speed 65Mb/s)

On 7/21/2011 12:57 PM, Pol Hallen wrote:

> dd if=/dev/zero of=/dev/md0 bs=1024M count=10
> 10+0 records in
> 10+0 records out
> 10737418240 bytes (11 GB) copied, 166.042 s, 64.7 MB/s

Do you not recall that I explained in detail, not two days ago, why you
should not use a 1GB block size when testing with dd in this manner?
And don't do this with the raw device. The resulting numbers, no matter
how large or small, are irrelevant.

*Put a filesystem on md0* and do:

~$ dd if=/dev/zero of=/some/dir/test.dd bs=4096 count=2621440

And why on earth would you bother running this test while the array is
still building? Again, the resulting figure is worthless to everyone.

--
Stan
--
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

Re: standard performance (write speed ??Mb/s) - new raid5 array

> Why did you create partitions? The whole point of zeroing the first 512
> bytes was to *eliminate* all the partitions...

Follow the post of Erwan Leroux, he advise creare a new partition with non-fs
data :-/

> No, you did not. It seems you merged bits and pieces from each array
> creation method. The array may still function properly. I've never
> tried what you've done here. Maybe others have the correct answer.

I wish it's everything ok :-)

Pol
--
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

Re: standard performance (write speed ??Mb/s) - new raid5 array

I never used the whole disk in my raid, so maybe my procedure is not
useful in this case,
but i think if you create partitions, you should create the array using=
them,
using the following command mdadm --create --verbose /dev/md0
--level=3Draid5 --raid-devices=3D5 /dev/sd[bcdef]1 --metadata 1.2
i can't recall where i see why to specify this metadata level but in
my case the default was not 1.2 so i had to.

When the rebuild is done and a filesystem set , run this command dd
if=3D/dev/zero of=3D/some/dir/test.dd bs=3D4096 count=3D2621440
to actually test the performance of the raid.

2011/7/22 Pol Hallen :
>> Why did you create partitions? =A0The whole point of zeroing the fir=
st 512
>> bytes was to *eliminate* all the partitions...
>
> Follow the post of Erwan Leroux, he advise creare a new partition wit=
h non-fs
> data :-/
>
>> No, you did not. =A0It seems you merged bits and pieces from each ar=
ray
>> creation method. =A0The array may still function properly. =A0I've n=
ever
>> tried what you've done here. =A0Maybe others have the correct answer=

>
> I wish it's everything ok :-)
>
> Pol
> --
> 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 =A0http://vger.kernel.org/majordomo-info.html
>
--
To unsubscribe from this list: send the line "unsubscribe linux-raid" i=
n
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html

Re: standard performance (write speed 65Mb/s)

> *Put a filesystem on md0* and do:
> ~$ dd if=/dev/zero of=/some/dir/test.dd bs=4096 count=2621440
> And why on earth would you bother running this test while the array is
> still building? Again, the resulting figure is worthless to everyone.

Ok.. I waiting finish rebuild and done new test:

dd if=/dev/zero of=/some/dir/test.dd bs=4096 count=2621440

Pol
--
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

Re: standard performance (write speed 20Mb/s)

W dniu 21 lipca 2011 17:42 użytkownik Erwan Leroux
napisał:
> I search my bookmarks to find the original source, which has some
> benchmark to compare sector 63 and 64
> http://linuxconfig.org/linux-wd-ears-advanced-format
>

Thanks for the reply. I understood that the partition must start at a
multiple of 8 512B blocks, to be properly aligned at a 4KB-sector HDD.
I just didn't know, that you couldn't go below sector 64, e.g. to
start a partition at sector 16.
--
To unsubscribe from this list: send the line "unsubscribe linux-raid" i=
n
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html

Re: standard performance (write speed 20Mb/s)

On Sun, Jul 17, 2011 at 5:11 AM, John Robinson
wrote:

> Pretty poor. CentOS 5, Intel ICH10, md RAID 6 over 5 7200rpm 1TB drives,
> then LVM, then ext3:
> # dd if=/dev/zero of=test bs=4096 count=262144
> 262144+0 records in
> 262144+0 records out
> 1073741824 bytes (1.1 GB) copied, 2.5253 seconds, 425 MB/s

What hard drive offers a sustained data rate of 425 MB/s or even half that?

Simon
--
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

Re: standard performance (write speed 20Mb/s)

--Sig_/GsSkgNm=PFdaiJ9pHR5TfT1
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: quoted-printable

On Tue, 26 Jul 2011 22:42:14 -0700
Simon Matthews wrote:

> On Sun, Jul 17, 2011 at 5:11 AM, John Robinson
> wrote:
>=20
> > Pretty poor. CentOS 5, Intel ICH10, md RAID 6 over 5 7200rpm 1TB drives,
> > then LVM, then ext3:
> > # dd if=3D/dev/zero of=3Dtest bs=3D4096 count=3D262144
> > 262144+0 records in
> > 262144+0 records out
> > 1073741824 bytes (1.1 GB) copied, 2.5253 seconds, 425 MB/s
>=20
> What hard drive offers a sustained data rate of 425 MB/s or even half tha=
t?

"md RAID 6 over 5 7200rpm 1TB drives" does? :) At least half that - easily.

But still, the result posted is very much inflated, they forgot the "conv=
=3Dfdatasync" option, so mostly benchmarking the FS cache in RAM.

--=20
With respect,
Roman

--Sig_/GsSkgNm=PFdaiJ9pHR5TfT1
Content-Type: application/pgp-signature; name=signature.asc
Content-Disposition: attachment; filename=signature.asc

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.11 (GNU/Linux)

iEYEARECAAYFAk4vpkgACgkQTLKSvz+PZwi1FQCeN9AS+7PL9avyzamNUr/t hBbR
zAoAnA7wpoVdpSjYKsMF+5Q/P08vkf3X
=bLWL
-----END PGP SIGNATURE-----

--Sig_/GsSkgNm=PFdaiJ9pHR5TfT1--
--
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

Re: standard performance (write speed 20Mb/s)

On 7/27/2011 12:42 AM, Simon Matthews wrote:
> On Sun, Jul 17, 2011 at 5:11 AM, John Robinson
> wrote:
>
>> Pretty poor. CentOS 5, Intel ICH10, md RAID 6 over 5 7200rpm 1TB drives,
>> then LVM, then ext3:
>> # dd if=/dev/zero of=test bs=4096 count=262144
>> 262144+0 records in
>> 262144+0 records out
>> 1073741824 bytes (1.1 GB) copied, 2.5253 seconds, 425 MB/s
>
> What hard drive offers a sustained data rate of 425 MB/s or even half that?

425 MB/s / 3 spindles = 142 MB/s per spindle

That's not poor, it's excellent. Which drives are these? WD Black,
Seagate, Hitachi?

--
Stan
--
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

Re: standard performance (write speed 20Mb/s)

On 27/07/2011 11:22, Stan Hoeppner wrote:
> On 7/27/2011 12:42 AM, Simon Matthews wrote:
>> On Sun, Jul 17, 2011 at 5:11 AM, John Robinson
>> wrote:
>>
>>> Pretty poor. CentOS 5, Intel ICH10, md RAID 6 over 5 7200rpm 1TB drives,
>>> then LVM, then ext3:
>>> # dd if=/dev/zero of=test bs=4096 count=262144
>>> 262144+0 records in
>>> 262144+0 records out
>>> 1073741824 bytes (1.1 GB) copied, 2.5253 seconds, 425 MB/s
>>
>> What hard drive offers a sustained data rate of 425 MB/s or even half that?
>
> 425 MB/s / 3 spindles = 142 MB/s per spindle
>
> That's not poor, it's excellent. Which drives are these? WD Black,
> Seagate, Hitachi?

Gentlemen, we've been round this loop before about 10 days ago. Pol's 20
MB/s was poor because he was testing on an array with unaligned
partitions and a resync was running, my 425 MB/s was a bad test because
it didn't use fdatasync or direct and I said dd was a bad test anyway,
etc etc.

Cheers,

John.
--
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

Re: standard performance (write speed 20Mb/s)

On 07/27/2011 06:26 AM, John Robinson wrote:
> On 27/07/2011 11:22, Stan Hoeppner wrote:
>> On 7/27/2011 12:42 AM, Simon Matthews wrote:
>>> On Sun, Jul 17, 2011 at 5:11 AM, John Robinson
>>> wrote:
>>>
>>>> Pretty poor. CentOS 5, Intel ICH10, md RAID 6 over 5 7200rpm 1TB
>>>> drives,
>>>> then LVM, then ext3:
>>>> # dd if=/dev/zero of=test bs=4096 count=262144

no

oflag=direct

or

sync
date
dd if=/dev/zero of=test bs=4096 count=262144 ...
sync
date

and then a difference between the time stamps ...

>>>> 262144+0 records in
>>>> 262144+0 records out
>>>> 1073741824 bytes (1.1 GB) copied, 2.5253 seconds, 425 MB/s

This is purely file cache performance you have measured, nothing else.

[...]

> Gentlemen, we've been round this loop before about 10 days ago. Pol's 20
> MB/s was poor because he was testing on an array with unaligned

Using a huge blocksize (anything greater than 1/10th ram) isn't terribly
realistic from an actual application point of view in *most* cases. A
few corner cases maybe, but not in most cases.

Testing on a rebuilding array gives you a small fraction of the
available bandwidth ... typically you will see writes (cached) perform
better than reads in these cases, but its not a measurement that tells
you much more than performance during a rebuild.

Unaligned perform is altogether too common, though for streaming access,
isn't normally terribly significant, as the first non-alignment access
cost is amortized against many sequential accesses. Its a bad thing for
more random workloads.

> partitions and a resync was running, my 425 MB/s was a bad test because
> it didn't use fdatasync or direct and I said dd was a bad test anyway,
> etc etc.

dd's not a terrible test. Its a very quick and dirty indicator of a
problem in the event of an issue, if used correctly. Make sure you are
testing IO sizes of 2 or more times ram size, with sync's at the end,
and use date stamps to verify timing.

bonnie++, the favorite of many people, isn't a great IO generator. Nor
is iozone, etc. The best tests are ones that match your use cases.
Finding these are hard.

We like fio, as we can construct models of use cases and run them again
and again. Cached, uncached, etc. Makes for very easy and repeatable
testing.



--
Joseph Landman, Ph.D
Founder and CEO
Scalable Informatics, Inc.
email: landman@scalableinformatics.com
web : http://scalableinformatics.com
http://scalableinformatics.com/sicluster
phone: +1 734 786 8423 x121
fax : +1 866 888 3112
cell : +1 734 612 4615
--
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

Re: standard performance (write speed 20Mb/s)

On 7/27/2011 5:26 AM, John Robinson wrote:
> On 27/07/2011 11:22, Stan Hoeppner wrote:
>> On 7/27/2011 12:42 AM, Simon Matthews wrote:
>>> On Sun, Jul 17, 2011 at 5:11 AM, John Robinson
>>> wrote:
>>>
>>>> Pretty poor. CentOS 5, Intel ICH10, md RAID 6 over 5 7200rpm 1TB
>>>> drives,
>>>> then LVM, then ext3:
>>>> # dd if=/dev/zero of=test bs=4096 count=262144
>>>> 262144+0 records in
>>>> 262144+0 records out
>>>> 1073741824 bytes (1.1 GB) copied, 2.5253 seconds, 425 MB/s
>>>
>>> What hard drive offers a sustained data rate of 425 MB/s or even half
>>> that?
>>
>> 425 MB/s / 3 spindles = 142 MB/s per spindle
>>
>> That's not poor, it's excellent. Which drives are these? WD Black,
>> Seagate, Hitachi?
>
> Gentlemen, we've been round this loop before about 10 days ago. Pol's 20
> MB/s was poor because he was testing on an array with unaligned
> partitions and a resync was running, my 425 MB/s was a bad test because
> it didn't use fdatasync or direct and I said dd was a bad test anyway,
> etc etc.

Of course the 425 number is higher than real world. But this is the dd
"test" method for which many post results, so the number is still
somewhat valid for very coarse comparison purposes among systems. A
10GB run would have been better than 1GB obviously.

The Linpack benchmark is very similar to dd in this regard. It's a
horrible measure of supercomputer performance, but it's what everyone
uses. It's what allows US Government labs to go to Congress with and
say "The Chinese have passed us in the Supercomputer race. We need more
money to take the lead". (And, stupidly, Congress gives them the money)

--
Stan
--
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