9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: erik quanstrom <quanstro@quanstro.net>
To: 9fans@9fans.net
Subject: Re: [9fans] fossil caching venti errors
Date: Sat, 28 Mar 2009 11:13:15 -0400	[thread overview]
Message-ID: <5d7b27445236807043536410a584ee46@quanstro.net> (raw)
In-Reply-To: <9795467bbf361247c67dd50a1d03ac4f@terzarima.net>

On Sat Mar 28 06:54:35 EDT 2009, forsyth@terzarima.net wrote:
> i've seen that just recently, but thought it might have been
> a failing (very old) drive, or a power failure beyond the endurance of the UPS.
> if neither of those are true in your case, it might be worth a deeper look.
> i also found there is a persistent problem that `check fix' won't fix.
> (since it's my principal file server at home, i can't easily investigate more
> until i can transfer the service to a new drive, leaving the old drive
> for experiment.)

i hope this is useful information, but i fear it might not be.

if the very old disk in question is a scsi disk, disk/smart in my
contrib area should be gentle enough to run on a live server
with any kernel.

if the very old disk in question is an ata disk, disk/smart requires
the sd changes in my contrib area to run raw ata commands
like smart return status.  it is also should be gentle enough to run
on a live server.

unfortunately, disk/smart is not smart enough to access ata
general purpose logging information (gpl), yet.  manufacturer
diagnostic tools are still helpful here but require booting into
dos.

by the way, i think there are a number of interesting gsoc projects
related to devsd and ata.  for example, a devsd device that adds
checksumming to another devsd device.  gpl support could be
done entirely outside the kernel.

- erik



  parent reply	other threads:[~2009-03-28 15:13 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-03-28  3:48 Nathaniel W Filardo
2009-03-28 11:11 ` Charles Forsyth
2009-03-28 14:47   ` david bulkow
2009-03-28 15:13   ` erik quanstrom [this message]
2009-03-28 16:27   ` Nathaniel W Filardo
2009-03-28 17:31     ` erik quanstrom
2009-03-28 18:40       ` Nathaniel W Filardo
2009-04-08 14:44   ` Richard Miller
2009-04-08 14:56     ` ron minnich
2009-04-08 15:36       ` C H Forsyth
2009-04-08 15:55       ` Richard Miller
2009-04-08 16:46     ` cinap_lenrek
2009-04-08 17:01     ` cinap_lenrek
2009-04-08 17:28       ` Richard Miller
2009-04-08 17:41         ` cinap_lenrek
2009-04-08 18:18           ` Richard Miller
2009-04-08 17:36     ` Steve Simon
2009-03-28 20:38 erik quanstrom
2009-03-30 11:45 ` C H Forsyth
2009-03-30 11:55   ` C H Forsyth
2009-03-30 19:06     ` lucio
2009-03-30 19:15       ` erik quanstrom
2009-03-30 16:19 Pavel Klinkovsky
2010-01-08  6:53 Josef Artur

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=5d7b27445236807043536410a584ee46@quanstro.net \
    --to=quanstro@quanstro.net \
    --cc=9fans@9fans.net \
    /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;
as well as URLs for NNTP newsgroup(s).