From: Steven Lembark <lembark@wrkhors.com>
To: linux-lvm@sistina.com
Subject: Re: [linux-lvm] Re: [PATCH] 64 bit scsi read/write
Date: Sat, 14 Jul 2001 08:54:30 -0500 [thread overview]
Message-ID: <750880000.995118870@dizzy> (raw)
In-Reply-To: <E15LL3Y-0000yJ-00@the-village.bc.nu>
- Alan Cox <alan@lxorguk.ukuu.org.uk> on 07/14/01 09:45:44 +0100:
>> If, after a power outage, the IDE disk can keep going for long enough
>> to write its write cache out to the reserved vendor area (which will
>> only take 20-30 milliseconds) then the data may be considered *safe*
>> as soon as it hits writecache.
>
> Hohohoho.
Don't laugh, it works. A 10KRPM drive has enough inertia and
stored charge to write a full cyl in less time than the BFC's in
the switcher can discharge.
>> If I'm right then the only open question is: which disks do and
>> do not do the right thing when the lights go out.
>
> As far as I can tell none of them at least in the IDE world
Some SCSI's will use intertia to write a single cyl if the power
goes out. I've never seen a spec for IDE's that allows for this.
One more reason to use SCSI.
next prev parent reply other threads:[~2001-07-14 13:54 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20010703065312.J4841@vestdata.no>
[not found] ` <Pine.LNX.4.33.0107032211120.30968-100000@toomuch.toronto.redhat.com>
2001-07-05 6:34 ` [linux-lvm] Re: [PATCH] 64 bit scsi read/write Ragnar Kjørstad
2001-07-05 7:35 ` Ben LaHaise
2001-07-05 16:46 ` AJ Lewis
2001-07-05 17:09 ` Eric M. Hopper
2001-07-10 13:45 ` Heinz J. Mauelshagen
2001-07-13 18:20 ` Albert D. Cahalan
2001-07-13 20:41 ` Andreas Dilger
2001-07-13 21:14 ` Alan Cox
2001-07-14 3:23 ` Andrew Morton
2001-07-14 8:45 ` Alan Cox
2001-07-14 13:54 ` Steven Lembark [this message]
[not found] ` <20010715025001.B6722@weta.f00f.org>
2001-07-14 15:41 ` Jonathan Lundell
2001-07-14 20:11 ` Daniel Phillips
2001-07-15 1:21 ` Andrew Morton
2001-07-15 1:53 ` Daniel Phillips
[not found] ` <20010715153607.A7624@weta.f00f.org>
2001-07-15 6:05 ` John Alvord
[not found] ` <20010715180752.B7993@weta.f00f.org>
2001-07-15 13:16 ` Ken Hirsch
2001-07-15 22:14 ` Daniel Phillips
2001-07-17 0:31 ` Juan Quintela
2001-07-15 13:44 ` Daniel Phillips
[not found] ` <20010716023911.A10576@weta.f00f.org>
2001-07-15 15:06 ` Jonathan Lundell
[not found] ` <20010716032220.B10635@weta.f00f.org>
2001-07-15 17:44 ` Jonathan Lundell
2001-07-15 17:47 ` Justin T. Gibbs
2001-07-15 23:14 ` Rod Van Meter
[not found] ` <20010716205633.G11938@weta.f00f.org>
2001-07-16 13:19 ` Daniel Phillips
2001-07-16 14:26 ` Heinz J. Mauelshagen
2001-07-15 15:32 ` Alan Cox
2001-07-14 17:33 ` Jonathan Lundell
[not found] ` <20010715160247.I7624@weta.f00f.org>
2001-07-15 5:46 ` Jonathan Lundell
[not found] <20010714090703.B5737@weta.f00f.org>
2001-07-13 22:04 ` Andreas Dilger
2001-07-14 0:49 ` Jonathan Lundell
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=750880000.995118870@dizzy \
--to=lembark@wrkhors.com \
--cc=linux-lvm@sistina.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