From: Ian Stirling <root@mauve.demon.co.uk>
To: landley@trommello.org
Cc: root@mauve.demon.co.uk (Ian Stirling),
andre@linux-ide.org (Andre Hedrick), cw@f00f.org (Chris Wedgwood),
linux-kernel@vger.kernel.org
Subject: Re: Journaling pointless with today's hard disks?
Date: Tue, 27 Nov 2001 03:39:05 +0000 (GMT) [thread overview]
Message-ID: <200111270339.DAA06920@mauve.demon.co.uk> (raw)
In-Reply-To: <0111261800340R.02001@localhost.localdomain> from "Rob Landley" at Nov 26, 2001 06:00:34 PM
>
> On Monday 26 November 2001 20:23, Ian Stirling wrote:
>
> > > Now a cache large enough to hold 2 full tracks could also hold dozens of
> > > individual sectors scattered around the disk, which could take a full
> > > second to write off and power down. This is a "doctor, it hurts when I
> > > do this" question. DON'T DO THAT.
> >
> > Or, to seek to a journal track, and write the cache to it.
>
> Except that at most you have one seek to write out all the pending cache data
> anyway, so what exactly does seeking to a journal track buy you?
The ability to possibly dramatically improve performance by allowing
more than one or two tracks to be write cached at once.
Yes, in theory, the system should be able to elevator all seeks, but
it may not know that track 400 has really been remapped to 200, the
drive does.
With write-caching on, the system doesn't know where the head is,
the drive does.
And, it's nearly free (an extra meg of space)
<snip>
> Possibly. I still don't see what it gets you if you only have one track
> other than the one you're over to write to. (is the journal track near the
> area the head parks in? That could be a power saving method, I suppose. But
> it's also wasting disk space that would probably otherwise be used for
> storage or a block remapping, and how do you remap a bad sector out of the
> journal track if that happens?)
You simply pick another track for the journal, the same as you would
if an ordinary track goes bad.
(it's tested on boot)
The waste of disk space is utterly trivial.
A meg in drives where the entry level is 40G?
next prev parent reply other threads:[~2001-11-27 3:47 UTC|newest]
Thread overview: 86+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <mailman.1006644421.6553.linux-kernel2news@redhat.com>
2001-11-24 13:03 ` Florian Weimer
2001-11-24 13:40 ` Rik van Riel
2001-11-24 16:36 ` Phil Howard
2001-11-24 17:19 ` Charles Marslett
2001-11-24 17:31 ` Florian Weimer
2001-11-24 17:41 ` Matthias Andree
2001-11-24 19:20 ` Florian Weimer
2001-11-24 19:29 ` Rik van Riel
2001-11-24 22:51 ` John Alvord
2001-11-24 23:41 ` Phil Howard
2001-11-25 0:24 ` Ian Stirling
2001-11-25 0:53 ` Phil Howard
2001-11-25 1:25 ` H. Peter Anvin
2001-11-25 1:44 ` Sven.Riedel
2001-11-24 22:28 ` H. Peter Anvin
2001-11-25 4:49 ` Andre Hedrick
2001-11-24 23:04 ` Pedro M. Rodrigues
2001-11-24 23:23 ` Stephen Satchell
2001-11-24 23:29 ` H. Peter Anvin
2001-11-26 18:05 ` Steve Brueggeman
2001-11-26 23:49 ` Martin Eriksson
2001-11-27 0:06 ` Andreas Dilger
2001-11-27 0:16 ` Andre Hedrick
2001-11-27 7:38 ` Andreas Dilger
2001-11-27 11:48 ` Ville Herva
2001-11-27 0:18 ` Jonathan Lundell
2001-11-27 1:01 ` Ian Stirling
2001-11-27 1:33 ` H. Peter Anvin
2001-11-27 1:57 ` Steve Underwood
2001-11-27 5:04 ` Stephen Satchell
2001-11-25 4:20 ` Pete Zaitcev
2001-11-25 12:30 ` Matthias Andree
2001-11-25 15:04 ` Barry K. Nathan
2001-11-25 16:31 ` Matthias Andree
2001-11-27 2:39 ` Pavel Machek
2001-12-03 10:23 ` Matthias Andree
2001-11-25 9:14 ` Chris Wedgwood
2001-11-25 22:55 ` Daniel Phillips
2001-11-26 16:59 ` Rob Landley
2001-11-26 20:30 ` Andre Hedrick
2001-11-26 20:35 ` Rob Landley
2001-11-26 23:59 ` Andreas Dilger
2001-11-27 0:24 ` H. Peter Anvin
2001-11-27 0:52 ` H. Peter Anvin
2001-11-27 1:11 ` Andrew Morton
2001-11-27 1:15 ` H. Peter Anvin
2001-11-27 16:59 ` Matthias Andree
2001-11-27 16:56 ` Matthias Andree
2001-11-27 1:23 ` Ian Stirling
2001-11-26 23:00 ` Rob Landley
2001-11-27 2:41 ` H. Peter Anvin
2001-11-27 0:19 ` Rob Landley
2001-11-27 23:35 ` Andreas Bombe
2001-11-28 14:32 ` Rob Landley
2001-11-27 3:39 ` Ian Stirling [this message]
2001-11-27 7:03 ` Ville Herva
2001-11-27 16:50 ` Matthias Andree
2001-11-27 20:31 ` Rob Landley
2001-11-28 18:43 ` Matthias Andree
2001-11-28 18:46 ` Rob Landley
2001-11-28 22:19 ` Matthias Andree
2001-11-29 22:21 ` Pavel Machek
2001-12-01 10:55 ` Jeff V. Merkey
2001-12-02 0:08 ` Matthias Andree
2001-12-03 20:04 ` Pavel Machek
2001-11-26 20:53 ` Richard B. Johnson
2001-11-26 21:18 ` Journaling pointless with today's hard disks? [wandering OT] Rob Landley
2001-11-27 0:32 ` Journaling pointless with today's hard disks? H. Peter Anvin
2001-11-27 16:39 ` Matthias Andree
2001-11-27 17:42 ` Martin Eriksson
2001-11-28 16:35 ` Ian Stirling
2001-11-26 17:14 ` Steve Brueggeman
2001-11-26 20:36 ` Andre Hedrick
2001-11-26 21:14 ` Steve Brueggeman
2001-11-26 21:36 ` Andre Hedrick
2001-11-27 16:36 ` Steve Brueggeman
2001-11-27 20:04 ` Bill Davidsen
2001-11-27 21:28 ` Wayne Whitney
2001-11-27 21:52 ` Andre Hedrick
2001-11-28 11:53 ` Pedro M. Rodrigues
2001-11-25 13:52 ` Pedro M. Rodrigues
2001-11-25 1:20 dnu478nt5w@mailexpire.com
2001-11-28 14:36 Galappatti, Kishantha
2001-11-28 17:22 David Balazic
2001-11-28 23:25 Frank de Lange
2001-11-29 1:52 ` Matthias Andree
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=200111270339.DAA06920@mauve.demon.co.uk \
--to=root@mauve.demon.co.uk \
--cc=andre@linux-ide.org \
--cc=cw@f00f.org \
--cc=landley@trommello.org \
--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
all inboxes | Powered by JetHome®