Hi,
Thank you for your attempt to help me! By the way...I have checked
/proc/mounts and it was barrier=0 so...I guess that is that.
Unfortunately this leaves me with only one thing to test and that is to
swap the physical SSDs with each other and see if the apparent problems
move from sdb to sda or stay on sdb. If they move I guess it's the SSD
on sdb. But if the problems stay I guess the problem lies elsewhere. I
am just not sure it's safe to swap the 2 devices of an mdraid array.
Thanks again and kind regards!
On 10/22/2013 5:57 AM, Zheng Liu wrote:
On Mon, Oct 21, 2013 at 08:42:50PM +0300, Andrei Banu wrote:
Hi,
Meantime I've created another md device (just 5GB) and I've redone
the tests. I believe
this is easier and less risky than remounting an used md device.
root [/home2]# mount -l | grep md3
/dev/md3 on /home2 type ext4 (rw,barrier=0)
root [/home2]# dd bs=2M count=64 if=/dev/zero of=test6 conv=fdatasync
64+0 records in
64+0 records out
134217728 bytes (134 MB) copied, 12.3287 s, 10.9 MB/s
So the speed issue is still with us I believe.
Thanks for doing this. It seems that the problem we met are different.
Is there some way to check the barrier is really set to 0?
You have seen that from the output of 'mount' command barrier is 0. You
can 'cat /proc/mounts' to double-check it. But it should be the same.
Regards,
- Zheng
--
To unsubscribe from this list: send the line "unsubscribe linux-ext4" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
