From: Zheng Liu <gnehzuil.liu@gmail.com>
To: Andrei Banu <andrei.banu@redhost.ro>
Cc: linux-ext4@vger.kernel.org
Subject: Re: Weird jbd2 I/O load
Date: Tue, 22 Oct 2013 10:57:29 +0800 [thread overview]
Message-ID: <20131022025729.GA6247@gmail.com> (raw)
In-Reply-To: <5265679A.4050600@redhost.ro>
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
>
next prev parent reply other threads:[~2013-10-22 2:55 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-10-15 21:41 Weird jbd2 I/O load Andrei Banu
2013-10-21 13:53 ` Zheng Liu
2013-10-21 14:24 ` Andrei Banu
2013-10-21 16:55 ` Zheng Liu
2013-10-21 17:11 ` Zheng Liu
2013-10-21 17:42 ` Andrei Banu
2013-10-22 2:57 ` Zheng Liu [this message]
2013-10-22 7:22 ` Andrei Banu
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20131022025729.GA6247@gmail.com \
--to=gnehzuil.liu@gmail.com \
--cc=andrei.banu@redhost.ro \
--cc=linux-ext4@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox