mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Jan Kara <jack@suse.cz>
To: "Gábor Lénárt" <lgb@lgb.hu>
Cc: linux-kernel@vger.kernel.org
Subject: Re: barrier-based sync failed - disabling barriers
Date: Wed, 9 Nov 2011 01:23:55 +0100	[thread overview]
Message-ID: <20111109002355.GC21318@quack.suse.cz> (raw)
In-Reply-To: <20111018081159.GA21728@vega.lgb.hu>

  Hello,

On Tue 18-10-11 10:11:59, Gábor Lénárt wrote:
> I have a kernel log entry I've never seen before:
> 
> JBD: barrier-based sync failed on cciss!c0d0p3-8 - disabling barriers
> JBD: barrier-based sync failed on cciss!c0d0p1-8 - disabling barriers
> 
> Should I worry? Can it be blamed for the poor I/O performance? How can I
> solve this problem? Even if it doesn't mean too much (what I should
> worry about), it's a bit annoying (as always) to see odd messages.
> 
> The ext4 filesystems were created by the installer of an older (ubuntu)
> distribution, I guess, it can cause problems after the upgrade. Can I
> convert/modify the filesystem (like with tune2fs) not to have these messages
> and problem?
  You didn't choose the best list for this question -
linux-ext4@vger.kernel.org would be a better fit. LKML has far too big
traffic and things get lost... That's why I'm answering your email that
late as well.

  The messages about barriers are normal with the HW. They say that the
hardware (or the storage driver) does not support cache flush command.
Generally, if the array has battery backed write caches (or is otherwise
protected from power failure), you don't have to use barriers anyway (and
you can gain some performance boost by that). If you don't want to see
those messages in the log, use nobarrier mount option.

  These messages can only have positive effect on performance so if you
have some performance problems, it's something else...

								Honza

      parent reply	other threads:[~2011-11-09  0:23 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-10-18  8:11 Gábor Lénárt
2011-10-18  9:04 ` Gábor Lénárt
2011-11-09  0:23 ` Jan Kara [this message]

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=20111109002355.GC21318@quack.suse.cz \
    --to=jack@suse.cz \
    --cc=lgb@lgb.hu \
    --cc=linux-kernel@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

all inboxes | Powered by JetHome®