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 09:26:52 +0100	[thread overview]
Message-ID: <200712120926.53348.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.
>
> see dm_request():
>
>         /*
>          * There is no use in forwarding any barrier request since we
> can't * guarantee it is (or can be) handled by the targets correctly.
> */
>         if (unlikely(bio_barrier(bio))) {
>                 bio_endio(bio, -EOPNOTSUPP);
>                 return 0;
>         }

Thanks for your definitive answer.

What does that mean? What is the target in that case? If it is the libata 
PATA internal notebook drive it actually should support barriers and then 
I actually would like device mapper to support them too. Or is LVM2 the 
target and device mapper can't tell that LVM2 supports it?

I ask myself the question why write barrier if half the kernel does not 
handle it correctly and I am limited to plain partitions if I want to use 
it? Well I think I will just file a bug report at kernel.bugzilla.org 
about it.

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

  reply	other threads:[~2007-12-12  8:27 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 [this message]
2007-12-12 22:05   ` Martin Steigerwald

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=200712120926.53348.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