From: Krzysztof Halasa <khc@pm.waw.pl>
To: Pavel Machek <pavel@ucw.cz>
Cc: Jeff Garzik <jgarzik@pobox.com>, Hans Reiser <reiser@namesys.com>,
"Mudama, Eric" <eric_mudama@Maxtor.com>,
"'Norman Diamond'" <ndiamond@wta.att.ne.jp>,
"'Wes Janzen '" <superchkn@sbcglobal.net>,
"'Rogier Wolff '" <R.E.Wolff@BitWizard.nl>,
"'John Bradford '" <john@grabjohn.com>,
linux-kernel@vger.kernel.org, nikita@namesys.com,
"'Justin Cormack '" <justin@street-vision.com>,
"'Vitaly Fertman '" <vitaly@namesys.com>
Subject: Re: Blockbusting news, results get worse
Date: 28 Oct 2003 13:54:33 +0100 [thread overview]
Message-ID: <m37k2pfrp2.fsf@defiant.pm.waw.pl> (raw)
In-Reply-To: <20031028012143.GA427@elf.ucw.cz>
Pavel Machek <pavel@ucw.cz> writes:
> Well, even without FLUSH CACHE, you can expect that sector being
> writen during powerfail either contains old data *or* new data.
I thinks so. It was not always the case with IBM DTLA drives, though.
--
Krzysztof Halasa, B*FH
next prev parent reply other threads:[~2003-10-28 12:58 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-10-27 17:43 Mudama, Eric
2003-10-27 18:48 ` Hans Reiser
2003-10-27 19:47 ` Jeff Garzik
2003-10-27 20:03 ` John Bradford
2003-10-29 20:01 ` Pavel Machek
2003-10-30 8:30 ` John Bradford
2003-10-28 1:21 ` Pavel Machek
2003-10-28 12:54 ` Krzysztof Halasa [this message]
-- strict thread matches above, loose matches on Subject: below --
2003-10-29 20:11 Mudama, Eric
2003-10-27 18:06 Mudama, Eric
2003-10-27 19:18 ` Andre Hedrick
2003-10-27 13:07 Samium Gromoff
2003-10-26 22:12 Mudama, Eric
2003-10-26 18:33 Mudama, Eric
2003-10-26 22:03 ` Andre Hedrick
2003-10-27 9:34 ` Norman Diamond
2003-10-27 10:23 ` Jan-Benedict Glaw
2003-10-27 23:31 ` Jason Lunz
2003-10-28 20:56 ` Hans Reiser
2003-10-26 7:37 Norman Diamond
2003-10-26 10:39 ` John Bradford
2003-10-26 9:41 ` Pavel Machek
2003-10-26 11:38 ` Norman Diamond
2003-10-26 11:56 ` Pavel Machek
2003-10-26 12:06 ` Hans Reiser
2003-10-26 13:59 ` Krzysztof Halasa
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=m37k2pfrp2.fsf@defiant.pm.waw.pl \
--to=khc@pm.waw.pl \
--cc=R.E.Wolff@BitWizard.nl \
--cc=eric_mudama@Maxtor.com \
--cc=jgarzik@pobox.com \
--cc=john@grabjohn.com \
--cc=justin@street-vision.com \
--cc=linux-kernel@vger.kernel.org \
--cc=ndiamond@wta.att.ne.jp \
--cc=nikita@namesys.com \
--cc=pavel@ucw.cz \
--cc=reiser@namesys.com \
--cc=superchkn@sbcglobal.net \
--cc=vitaly@namesys.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
Powered by JetHome