public inbox for linux-xfs@vger.kernel.org
 help / color / mirror / Atom feed
From: Martin Steigerwald <Martin@lichtvoll.de>
To: linux-xfs@oss.sgi.com
Subject: Re: write barrier over device mapper supported or not?
Date: Wed, 12 Dec 2007 23:05:51 +0100	[thread overview]
Message-ID: <200712122305.52726.Martin@lichtvoll.de> (raw)
In-Reply-To: <475F5746.8080405@sandeen.net>

Am Mittwoch 12 Dezember 2007 schrieb Eric Sandeen:
> Martin Steigerwald wrote:
> > Hello!
> >
> > Are write barriers over device mapper supported or not?
>
> Nope.

[...]

> > But back then I also looked at the ext3 / jbd sources and found that
> > jbd issues a warning when barrier support is not available. However I
> > do not find that one either.
>
> in journal_write_commit_record() there is such a warning, but not in
> the mount path:
>
>                 printk(KERN_WARNING
>                         "JBD: barrier-based sync failed on %s - "
>                         "disabling barriers\n",
>                         bdevname(journal->j_dev, b));
>
> and if I set barrier=1 on an lvm-root test box, I do get:
>
> JBD: barrier-based sync failed on dm-0 - disabling barriers

Yes, I get it after actually touching a file and waiting for the kjournald 
commit interval of 5 seconds to occur.

Well I reported a bug about it, lets see what happens:

http://bugzilla.kernel.org/show_bug.cgi?id=9554

One might consider it being a feature wish of course.

-- 
Martin 'Helios' Steigerwald - http://www.Lichtvoll.de
GPG: 03B0 0D6C 0040 0710 4AFA  B82F 991B EAAC A599 84C7

      parent reply	other threads:[~2007-12-12 22:06 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-12-11 22:42 write barrier over device mapper supported or not? Martin Steigerwald
2007-12-12  3:36 ` Eric Sandeen
2007-12-12  8:26   ` Martin Steigerwald
2007-12-12 22:05   ` Martin Steigerwald [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=200712122305.52726.Martin@lichtvoll.de \
    --to=martin@lichtvoll.de \
    --cc=linux-xfs@oss.sgi.com \
    /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