LKML Archive on
help / color / mirror / Atom feed
From: Ian Stirling <>
To: Bartlomiej Zolnierkiewicz <>
Cc: Giuliano Pochini <>,
	"Eric D. Mudama" <>,
	Tom Vier <>,
Subject: Re: Linux Kernel 2.6.6 IDE shutdown problems.
Date: Wed, 26 May 2004 11:21:11 +0100	[thread overview]
Message-ID: <> (raw)
In-Reply-To: <>

Bartlomiej Zolnierkiewicz wrote:
> On Tuesday 25 of May 2004 11:05, Giuliano Pochini wrote:
>>On Mon, 24 May 2004, Eric D. Mudama wrote:
>>>Picture a nice fast drive doing 100 writes/second to the media... if
>>>you give it over 200 writes at a time, it'll occupy your 2 seconds.
>>>Newer drives with 8MB or larger buffers are certainly capable of
>>>caching a lot more than 200 writes...
>>Quite unlikely. Usually disks have a big cache but it can hold a very
>>limited number of blocks. 8MB of cache is probably divided in 8 blocks
>>of 1MB each.
> No.

It is indeed likely that the worst case is around 16000 writes, which if
on seperate tracks may take over 30 seconds to complete if done individually.

However, it's likely that any drive designer with a clue would allocate a
couple of journal tracks, so that the write cache and two backup copies can
be stored for replay when the drive is powered on again.

Why do I suspect that some designers don't have clue, or haven't really thought
enough about this case.

  reply	other threads:[~2004-05-26 10:21 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-05-15 12:20 Justin Piszcz
2004-05-15 13:06 ` Bartlomiej Zolnierkiewicz
2004-05-17 22:25   ` Bill Davidsen
2004-05-24  2:41     ` Tom Vier
2004-05-24  3:09       ` Daniel Pittman
2004-05-24 17:16       ` Eric D. Mudama
2004-05-25  9:05         ` Giuliano Pochini
2004-05-25 15:03           ` Bartlomiej Zolnierkiewicz
2004-05-26 10:21             ` Ian Stirling [this message]
2004-05-25 17:02           ` Eric D. Mudama
  -- strict thread matches above, loose matches on Subject: below --
2004-05-15 14:59 Justin Piszcz
2004-05-15 12:02 Justin Piszcz

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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \ \ \ \ \ \ \ \
    --subject='Re: Linux Kernel 2.6.6 IDE shutdown problems.' \

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).