From: Kenny Simpson <theonetruekenny@yahoo.com>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: linux kernel <linux-kernel@vger.kernel.org>
Subject: Re: RAID controller safety
Date: Fri, 30 Dec 2005 22:55:03 -0800 (PST) [thread overview]
Message-ID: <20051231065503.68614.qmail@web34110.mail.mud.yahoo.com> (raw)
In-Reply-To: <1135990179.28365.40.camel@localhost.localdomain>
Ok, I finally tracked through the i2o code, and found that i2o_block_device_flush is ultimately
called for fsync. Sorry for being so dense.
However, it does look like barriers are not directly supported. So, are they safe to use in ext3,
or is ext3 all fine without them? Would barriers benefit i2o devices, or is there some reason to
not have them?
As for the controller defaulting to write-back, I still cannot find anything that would set the
cache mode to write-through in the non-battery-backed case.
-Kenny
__________________________________
Yahoo! for Good - Make a difference this year.
http://brand.yahoo.com/cybergivingweek2005/
next prev parent reply other threads:[~2005-12-31 6:55 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-12-29 16:29 RAID controller safety Kenny Simpson
2005-12-30 15:17 ` Alan Cox
2005-12-30 16:18 ` Kenny Simpson
2005-12-30 18:20 ` Alan Cox
2005-12-30 18:58 ` Kenny Simpson
2005-12-30 19:31 ` Bernd Eckenfels
2005-12-31 0:49 ` Alan Cox
2005-12-31 3:25 ` Kenny Simpson
2005-12-31 3:29 ` Kenny Simpson
2005-12-31 6:55 ` Kenny Simpson [this message]
2005-12-31 7:57 ` Kenny Simpson
-- strict thread matches above, loose matches on Subject: below --
2006-01-06 14:33 Salyzyn, Mark
2006-01-06 14:46 ` Alan Cox
2006-01-06 15:18 ` Kenny Simpson
2006-01-06 16:02 ` Alan Cox
2006-01-06 17:06 Salyzyn, Mark
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=20051231065503.68614.qmail@web34110.mail.mud.yahoo.com \
--to=theonetruekenny@yahoo.com \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=linux-kernel@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