From: Jens Axboe <axboe@suse.de>
To: Tetsuo Takata <takatan.linux@gmail.com>
Cc: akpm@osdl.org, linux-kernel@vger.kernel.org, doubt@developer.osdl.jp
Subject: Re: [PATCH] enable XFS write barrier
Date: Mon, 23 Jan 2006 15:48:04 +0100 [thread overview]
Message-ID: <20060123144803.GJ12773@suse.de> (raw)
In-Reply-To: <8e8498350601230640x49d8f866q@mail.gmail.com>
On Mon, Jan 23 2006, Tetsuo Takata wrote:
> I found out that the q->ordered is not being set properly on XFS.
>
>
> I'm testing the write barrier support of XFS.
> I run the test on kernel 2.6.16-rc1-git4.
> but I found out that the "-o barrier" option is automatically disabled
> in my environment.
> For this reason I could not test the write barrier's execution path.
>
> The error message in "/var/log/messages" is:
> Filesystem "sdb1": Disabling barriers, not supported by the underlying device
>
>
> This patch fixes these bugs.
Woops, thanks!
--
Jens Axboe
prev parent reply other threads:[~2006-01-23 14:46 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-01-23 14:40 [PATCH] enable XFS write barrier Tetsuo Takata
2006-01-23 14:48 ` Jens Axboe [this message]
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=20060123144803.GJ12773@suse.de \
--to=axboe@suse.de \
--cc=akpm@osdl.org \
--cc=doubt@developer.osdl.jp \
--cc=linux-kernel@vger.kernel.org \
--cc=takatan.linux@gmail.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