All of lore.kernel.org
 help / color / mirror / Atom feed
From: Andrei Banu <andrei.banu@redhost.ro>
To: linux-ext4@vger.kernel.org
Subject: Re: Weird jbd2 I/O load
Date: Mon, 21 Oct 2013 17:24:45 +0300	[thread overview]
Message-ID: <5265392D.1020500@redhost.ro> (raw)
In-Reply-To: <20131021135338.GA3392@gmail.com>

Hi Zheng,

Thank you for your reply. We can make this test and if it doesn't help 
we'll re-enable
the barrier but first I need to ask a few questions:

1. /dev/md2 is mounted on /. So your command should look like this?

$ mount -t ext4 -o remount,barrier=0    /dev/md2    /

In /etc/fstab I have other parameters as well: 
noatime,usrjquota=quota.user,jqfmt=vfsv0
Do I also add these like this:

$ mount -t ext4 -o 
remount,barrier=0,noatime,usrjquota=quota.user,jqfmt=vfsv0 /dev/md2     /

2. Can the command above be run on an active (very active) cPanel server?

3. How do I re-enable the barrier?

4. What is the probability of data loss in case of cold reboot?

Thanks!

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


  reply	other threads:[~2013-10-21 14:25 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 [this message]
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
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=5265392D.1020500@redhost.ro \
    --to=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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.