From: Andreas Dilger <adilger@turbolabs.com>
To: Andre Hedrick <andre@linux-ide.org>
Cc: Martin Eriksson <nitrax@giron.wox.org>,
Steve Brueggeman <xioborg@yahoo.com>,
linux-kernel@vger.kernel.org
Subject: Re: Journaling pointless with today's hard disks?
Date: Tue, 27 Nov 2001 00:38:43 -0700 [thread overview]
Message-ID: <20011127003843.Z730@lynx.no> (raw)
In-Reply-To: <20011126170631.O730@lynx.no> <Pine.LNX.4.10.10111261614190.9508-100000@master.linux-ide.org>
In-Reply-To: <Pine.LNX.4.10.10111261614190.9508-100000@master.linux-ide.org>; from andre@linux-ide.org on Mon, Nov 26, 2001 at 04:16:12PM -0800
On Nov 26, 2001 16:16 -0800, Andre Hedrick wrote:
> On Mon, 26 Nov 2001, Andreas Dilger wrote:
> > What happens if you have a slightly bad power supply? Does it immediately
> > go read only all the time? It would definitely need to be able to
> > recover operations as soon as the power was "normal" again, even if this
> > caused basically "sync" I/O to the disk. Maybe it would be able to
> > report this to the user via SMART, I don't know.
>
> ATA/SCSI SMART is already DONE!
>
> To bad most people have not noticed.
Oh, I know SMART is implemented, although I haven't actually seen/used a
tool which takes advantage of it (do you have such a thing?). It would
be nice if there were messages appearing in my syslog (just like the
AIX days) which said "there were 10 temporary read errors at block M on
drive X yesterday" and "1 permanent write error at block M, block remapped
on drive X yesterday", so I would know _before_ my drive craps out
after all of the remapping table is full, or the temporary read errors
become permanent. (I have a special interest in that because my laptop
hard drive sounds like a jet engine at times... ;-).
What I was originally suggesting is that it have a field which can report
to the user that "there were 800 sync/reset operations because of power
drops that were later found not to be power failures". That is what
I was suggesting SMART report in this case (actual power failures are
not interesting). Note also, that this is purely hypothetical, based
on only a vague understanding on what actually happens when the drive
thinks it is losing power, and only ever having seen the hex output
of /proc/ide/hda/smart_{values,thresholds}.
Being able to get a number back from the hard drive that it is performing
poorly (i.e. synchronous I/O + lots of resets) because of a bad power supply
is exactly what SMART was designed to do - predictive failure analysis.
Cheers, Andreas
--
Andreas Dilger
http://sourceforge.net/projects/ext2resize/
http://www-mddsp.enel.ucalgary.ca/People/adilger/
next prev parent reply other threads:[~2001-11-27 7:39 UTC|newest]
Thread overview: 86+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-11-24 13:03 Journaling pointless with today's hard disks? 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 [this message]
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
[not found] ` <mailman.1006644421.6553.linux-kernel2news@redhat.com>
2001-11-25 4:20 ` Pete Zaitcev
2001-11-25 13:52 ` Pedro M. Rodrigues
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
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
-- strict thread matches above, loose matches on Subject: below --
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=20011127003843.Z730@lynx.no \
--to=adilger@turbolabs.com \
--cc=andre@linux-ide.org \
--cc=linux-kernel@vger.kernel.org \
--cc=nitrax@giron.wox.org \
--cc=xioborg@yahoo.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