I have 6x WD Caviar Black 1,5 TB in Software RAID 10 / 1 / 0 (Centos 6.2 / mdadm)
cat /proc/mdstat
Personalities : [raid10] [raid0] [raid1]
md0 : active raid1 sdf2[5] sda2[0] sdb2[1] sdd2[3] sdc2[2] sde2[4]
1023988 blocks super 1.0 [6/6] [UUUUUU]
md126 : active raid0 sde1[4] sda1[0] sdd1[3] sdb1[1] sdc1[2] sdf1[5]
122873856 blocks super 1.2 64k chunks
md127 : active raid10 sde3[4] s
I've seen the advice everywhere (including here and here): keep your OS partition, DB data files and DB transaction logs on separate discs/arrays.
I'm creating RAID10 array from 6 drives. When created in near layout, e.g.
mdadm --create /dev/md2 --chunk=64 --level=10 --raid-devices=6 --layout=n2 /dev/sda1 ...
Checking stripe size as reported by the system:
cat /sys/devices/virtual/block/md2/queue/optimal_io_size
Result is 196608, as expected, e.g.
Iotop tool reports md2_raid1 takes HDD IO up to 99 %.
The server's HDD becomes busy and it's impossible to do any operation on it.
Here is the output of cat /proc/mdstat
Personalities : [raid0] [raid1] [raid6] [raid5] [raid4] [raid10]
md2 : active raid1 sda3[0] sdb3[1]
1462766336 blocks [2/2] [UU]
md1 : active raid1 sda2[0] sdb2[1]
264960 blocks [2/2] [UU]
md0 : active raid1 sda1[
I have Software Raid 10 setup, it has been working great a few months.
When I did a quick HD speed test:
dd if=/dev/zero of=test bs=64k count=16k conv=fdatasync
It is taking forever and I had to terminate it, the result was:
1073741824 bytes (1.1 GB) copied, 151.27 s, 7.1 MB/s
What causing this?
[root@host ~]# cat /proc/mdstat
Personalities : [raid1] [raid10]
md2 : active raid1 sdc1[4]
Basing this question on information I got in Why does df shows only half the size of a RAID10 array?,
how should I create a RAID10 array using EBS volumes on Amazon, in a way that will not be redundant too much ?
As the linked question shows, I was using a guide from the 10gen company (that created mongodb) for how to create a raid10 array using EBS.
I encounter an issue with the size of the cre
Basing this question on information I got in Why does df shows only half the size of a RAID10 array?,
how should I create a RAID10 array using EBS volumes on Amazon, in a way that will not be redundant too much ?
As the linked question shows, I was using a guide from the 10gen company (that created mongodb) for how to create a raid10 array using EBS.
I encounter an issue with the size of the cre
Hello, I have 2 servers with broken raid 1, but each one gives me a different
error, I dont know what is the difference.
Code:
[root@ ~]# cat /proc/mdstat
Personalities : [raid1] [raid0] [raid6] [raid5] [raid4] [raid10]
md0 : active raid1 sdb1[2](F) sda1[0]
2102464 blocks [2/1] [U_]
md1 : active raid1 sdb2[2](F) sda2[0]
264960 blocks [2/1] [U_]
md
I've created a RAID10 array using 4 75G drives, to create a storage of 150G.
After everything finished (including the initial syncing), everything looked good except the output of df -h which showed only 73G storage on the designated mount point.
Details:
The machine is an m1.large Ubuntu 11.10 instance on Amazon EC2.
The 4 drives are EBS drives, each is 75G in size.
The RAID10 array was crea