From: 谢纲 <xiegang112@gmail.com>
To: linux-fsdevel@vger.kernel.org
Subject: ordered I/O with multipath
Date: Wed, 8 Apr 2009 12:59:49 +0800 [thread overview]
Message-ID: <d364733c0904072159q39d7a52dyd322bd75f528cca1@mail.gmail.com> (raw)
Hi,
Some journal filesystem use barrier i/o to ensure the order of the
committing data. But if the filesystem is on the top of volume manager
which support the raid and multipath. The barrier i/o might not be
handled correctly. How does journal filesystem deal with this?
--
Xie Gang
next reply other threads:[~2009-04-08 4:59 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-04-08 4:59 谢纲 [this message]
2009-04-08 14:30 ` ordered I/O with multipath Jamie Lokier
2009-04-08 14:53 ` 谢纲
2009-04-09 18:32 ` Bryan Henderson
2009-04-09 20:00 ` Jamie Lokier
2009-04-10 16:42 ` Bryan Henderson
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=d364733c0904072159q39d7a52dyd322bd75f528cca1@mail.gmail.com \
--to=xiegang112@gmail.com \
--cc=linux-fsdevel@vger.kernel.org \
/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;
as well as URLs for NNTP newsgroup(s).