All of lore.kernel.org
 help / color / mirror / Atom feed
From: Gerd Hoffmann <kraxel@suse.de>
To: Keir Fraser <Keir.Fraser@cl.cam.ac.uk>
Cc: Ian Pratt <m+Ian.Pratt@cl.cam.ac.uk>, xen-devel@lists.xensource.com
Subject: Re: [patch] Add support for barriers to	blk{back,front} drivers.
Date: Thu, 09 Nov 2006 15:15:23 +0100	[thread overview]
Message-ID: <455337FB.3000904@suse.de> (raw)
In-Reply-To: <C178E1F8.4385%Keir.Fraser@cl.cam.ac.uk>

Keir Fraser wrote:
> On 9/11/06 12:48, "Gerd Hoffmann" <kraxel@suse.de> wrote:
> 
>>> What happens (even on native Linux) if you have, say, a RAID array in which
>>> some of the discs support barriers and others don't?
>> The raid0 driver doesn't support barriers in the first place.  Not sure
>> about the other raid drivers.
> 
> Does this mean journalling filesystems cannot run reliably on top of RAID-0?
> That sounds a bit concerning!

Without barrier support available linux filesytems fallback to just wait
until the requests (which would have been submitted as barrier requests)
are finished before submitting the next to make sure the ordering is
fine.  That works ok as long as the disk doesn't do write caching, so
you better turn write caching off in that case.

> What about when running on top of LVM, where an LV is stitched together from
> bits of various PVs. Some may support barriers, some may not. Running on top
> of LVM is default for most distros, so surely it must have a story on write
> barriers?

lvm works ok for me, almost all my domU disks are on lvm.  I have just
one disk in the system though.

I'm not sure what happens with multiple PVs.  I'd expect barriers are
working fine as long as your logical volume is not spread over multiple
physical volumes and the underlying physical volume can handle barriers.

cheers,

  Gerd

-- 
Gerd Hoffmann <kraxel@suse.de>
http://www.suse.de/~kraxel/julika-dora.jpeg

  reply	other threads:[~2006-11-09 14:15 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-10-30 12:15 [patch] Add support for barriers to blk{back, front} drivers Ian Pratt
2006-10-30 12:43 ` [patch] Add support for barriers to blk{back,front} drivers Gerd Hoffmann
2006-11-08 15:38   ` Gerd Hoffmann
2006-11-09  1:04     ` [patch] Add support for barriers to blk{back, front} drivers Ian Pratt
2006-11-09  1:15       ` John Levon
2006-11-09  9:00     ` [patch] Add support for barriers to blk{back,front} drivers Keir Fraser
2006-11-09 12:48       ` Gerd Hoffmann
2006-11-09 13:47         ` Keir Fraser
2006-11-09 14:15           ` Gerd Hoffmann [this message]
  -- strict thread matches above, loose matches on Subject: below --
2006-10-27 13:46 [patch] Add support for barriers to blk{back, front} drivers Ian Pratt
2006-10-30  8:21 ` [patch] Add support for barriers to blk{back,front} drivers Gerd Hoffmann
2006-10-23 11:42 [patch] Add support for barriers to blk{back, front} drivers Ian Pratt
2006-10-23 12:27 ` [patch] Add support for barriers to blk{back,front} drivers Gerd Hoffmann
2006-10-25 16:52   ` Gerd Hoffmann
2006-10-20  8:38 [patch] Add support for barriers to blk{back, front} drivers kraxel
2006-10-20 20:35 ` Ian Pratt

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=455337FB.3000904@suse.de \
    --to=kraxel@suse.de \
    --cc=Keir.Fraser@cl.cam.ac.uk \
    --cc=m+Ian.Pratt@cl.cam.ac.uk \
    --cc=xen-devel@lists.xensource.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 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.