From: Javier Guerra <javier@guerrag.com>
To: Christoph Hellwig <hch@lst.de>
Cc: qemu-devel@nongnu.org, kvm@vger.kernel.org, rusty@rustcorp.com.au
Subject: Re: Notes on block I/O data integrity
Date: Tue, 25 Aug 2009 14:33:30 -0500 [thread overview]
Message-ID: <90eb1dc70908251233m4b90ddfuabb4d26bccd62c63@mail.gmail.com> (raw)
In-Reply-To: <20090825181120.GA4863@lst.de>
On Tue, Aug 25, 2009 at 1:11 PM, Christoph Hellwig<hch@lst.de> wrote:
> - barrier requests and cache flushes are supported by all local
> disk filesystem in popular use (btrfs, ext3, ext4, reiserfs, XFS).
> However unlike the other filesystems ext3 does _NOT_ enable barriers
> and cache flush requests by default.
what about LVM? iv'e read somewhere that it used to just eat barriers
used by XFS, making it less safe than simple partitions.
--
Javier
WARNING: multiple messages have this Message-ID (diff)
From: Javier Guerra <javier@guerrag.com>
To: Christoph Hellwig <hch@lst.de>
Cc: rusty@rustcorp.com.au, qemu-devel@nongnu.org, kvm@vger.kernel.org
Subject: [Qemu-devel] Re: Notes on block I/O data integrity
Date: Tue, 25 Aug 2009 14:33:30 -0500 [thread overview]
Message-ID: <90eb1dc70908251233m4b90ddfuabb4d26bccd62c63@mail.gmail.com> (raw)
In-Reply-To: <20090825181120.GA4863@lst.de>
On Tue, Aug 25, 2009 at 1:11 PM, Christoph Hellwig<hch@lst.de> wrote:
> - barrier requests and cache flushes are supported by all local
> disk filesystem in popular use (btrfs, ext3, ext4, reiserfs, XFS).
> However unlike the other filesystems ext3 does _NOT_ enable barriers
> and cache flush requests by default.
what about LVM? iv'e read somewhere that it used to just eat barriers
used by XFS, making it less safe than simple partitions.
--
Javier
next prev parent reply other threads:[~2009-08-25 19:33 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-08-25 18:11 Notes on block I/O data integrity Christoph Hellwig
2009-08-25 18:11 ` [Qemu-devel] " Christoph Hellwig
2009-08-25 19:33 ` Javier Guerra [this message]
2009-08-25 19:33 ` [Qemu-devel] " Javier Guerra
2009-08-25 19:36 ` Christoph Hellwig
2009-08-25 19:36 ` [Qemu-devel] " Christoph Hellwig
2009-08-26 18:57 ` Jamie Lokier
2009-08-26 18:57 ` Jamie Lokier
2009-08-26 22:17 ` Christoph Hellwig
2009-08-26 22:17 ` Christoph Hellwig
2009-08-27 9:00 ` Jamie Lokier
2009-08-25 20:25 ` Nikola Ciprich
2009-08-25 20:25 ` [Qemu-devel] " Nikola Ciprich
2009-08-26 18:55 ` Jamie Lokier
2009-08-26 18:55 ` Jamie Lokier
2009-08-27 0:15 ` Christoph Hellwig
2009-08-27 0:15 ` [Qemu-devel] " Christoph Hellwig
2009-08-27 10:51 ` Rusty Russell
2009-08-27 10:51 ` [Qemu-devel] " Rusty Russell
2009-08-27 13:42 ` Christoph Hellwig
2009-08-27 13:42 ` [Qemu-devel] " Christoph Hellwig
2009-08-28 2:03 ` Rusty Russell
2009-08-28 2:03 ` [Qemu-devel] " Rusty Russell
2009-08-27 14:09 ` [Qemu-devel] " Jamie Lokier
2009-08-27 14:09 ` Jamie Lokier
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=90eb1dc70908251233m4b90ddfuabb4d26bccd62c63@mail.gmail.com \
--to=javier@guerrag.com \
--cc=hch@lst.de \
--cc=kvm@vger.kernel.org \
--cc=qemu-devel@nongnu.org \
--cc=rusty@rustcorp.com.au \
/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.