From: Rogier Wolff <R.E.Wolff@BitWizard.nl>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: Jens Axboe <axboe@suse.de>, Neil Brown <neilb@cse.unsw.edu.au>,
Christoph Hellwig <hch@lst.de>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: bug in md write barrier support?
Date: Sun, 12 Sep 2004 19:13:00 +0200 [thread overview]
Message-ID: <20040912171300.GA14369@bitwizard.nl> (raw)
In-Reply-To: <1094682098.12280.19.camel@localhost.localdomain>
On Wed, Sep 08, 2004 at 11:21:39PM +0100, Alan Cox wrote:
> I2O defines cache flush very losely. It flushes the cache and returns
[...]
> write 1, 2, 3, 4 , 40, 41, flush cache, write 5, 6, 100
> it'll write 1,2,3,4,5,6, 40, 41, report flush cache complete.
which, if 5,6 are the metadata updates beloging to logfile writes
40,41 and the system powers down between 5 and 41 spells trouble.
Roger.
--
** R.E.Wolff@BitWizard.nl ** http://www.BitWizard.nl/ ** +31-15-2600998 **
*-- BitWizard writes Linux device drivers for any device you may have! --*
**** "Linux is like a wigwam - no windows, no gates, apache inside!" ****
prev parent reply other threads:[~2004-09-12 17:13 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-09-03 17:24 bug in md write barrier support? Christoph Hellwig
2004-09-04 0:56 ` Neil Brown
2004-09-04 8:21 ` Jens Axboe
2004-09-06 1:36 ` Neil Brown
2004-09-08 9:23 ` Jens Axboe
2004-09-08 13:35 ` Alan Cox
2004-09-08 15:46 ` Jens Axboe
2004-09-08 22:21 ` Alan Cox
2004-09-09 8:06 ` Jens Axboe
2004-09-09 8:22 ` Arjan van de Ven
2004-09-09 8:29 ` Jens Axboe
2004-09-09 12:51 ` Alan Cox
2004-09-09 14:34 ` Jens Axboe
2004-09-12 17:13 ` Rogier Wolff [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=20040912171300.GA14369@bitwizard.nl \
--to=r.e.wolff@bitwizard.nl \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=axboe@suse.de \
--cc=hch@lst.de \
--cc=linux-kernel@vger.kernel.org \
--cc=neilb@cse.unsw.edu.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.