[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20131022025729.GA6247@gmail.com>
Date: Tue, 22 Oct 2013 10:57:29 +0800
From: Zheng Liu <gnehzuil.liu@...il.com>
To: Andrei Banu <andrei.banu@...host.ro>
Cc: linux-ext4@...r.kernel.org
Subject: Re: Weird jbd2 I/O load
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
>
> Thanks a lot!
>
> On 10/21/2013 4:53 PM, Zheng Liu wrote:
> >Hi Andrei,
> >
> >Could you please disable barrier for ext4 and try your 'dd' test again?
> > $ sudo mount -t ext4 -o remount,barrier=0 ${DEV} ${MNT}
> >
> >*WARNING: you could lost your data with barrier=0 when you get a power
> >failure or cold reset.*
> >
> >We have met a similar problem that is because some SSDs couldn't handle
> >barrier command properly.
> >
> >Regards,
> > - Zheng
>
--
To unsubscribe from this list: send the line "unsubscribe linux-ext4" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Powered by blists - more mailing lists