From: Folkert van Heusden <folkert@vanheusden.com>
To: Mark Lord <lkml@rtr.ca>
Cc: Andi Kleen <andi@firstfloor.org>,
Anton Ertl <anton@mips.complang.tuwien.ac.at>,
linux-kernel@vger.kernel.org
Subject: Re: Out-of-order writing by disk drives
Date: Fri, 17 Apr 2009 21:46:46 +0200 [thread overview]
Message-ID: <20090417194646.GC10554@vanheusden.com> (raw)
In-Reply-To: <49E4CA75.902@rtr.ca>
>> A full listing of what devices do and don't support barriers would
>> be likely very long. You would actually need to list down to hard disks.
>>
>> A common problem is barriers over LVM. Since 2.6.29 they work
>> with a single device (and if the underlying device supports it) with
>> dm linear, but not in any other LVM setup.
> ..
>
> Does anyone else here find this rather peculiar?
> The folks who actually care about barriers the most
> (apart from kernel developers) are probably enterprise users.
> And who is most likely to be using RAID and LVM,
> where barriers generally don't work at all ?
What about iSCSI? Does it support barriers?
Folkert van Heusden
--
MultiTail cok yonlu kullanimli bir program, loglari okumak, verilen
kommandolari yerine getirebilen. Filter, renk verme, merge, 'diff-
view', vs. http://www.vanheusden.com/multitail/
----------------------------------------------------------------------
Phone: +31-6-41278122, PGP-key: 1F28D8AE, www.vanheusden.com
next prev parent reply other threads:[~2009-04-17 19:47 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-04-07 20:04 Out-of-order writing by disk drives Anton Ertl
2009-04-14 14:10 ` Andi Kleen
2009-04-14 16:33 ` Anton Ertl
2009-04-14 17:24 ` Andi Kleen
2009-04-14 17:40 ` Mark Lord
2009-04-14 17:48 ` Michael Tokarev
2009-04-14 17:54 ` Andi Kleen
2009-04-14 18:09 ` Michael Tokarev
2009-04-14 18:50 ` Andi Kleen
2009-04-14 19:27 ` Chris Mason
2009-04-15 12:46 ` Jens Axboe
2009-04-17 19:46 ` Folkert van Heusden [this message]
2009-04-17 20:29 ` Andi Kleen
2009-04-17 21:07 ` Folkert van Heusden
2009-04-18 9:06 ` Anton Ertl
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=20090417194646.GC10554@vanheusden.com \
--to=folkert@vanheusden.com \
--cc=andi@firstfloor.org \
--cc=anton@mips.complang.tuwien.ac.at \
--cc=linux-kernel@vger.kernel.org \
--cc=lkml@rtr.ca \
/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