From: "Richard B. Johnson" <root@chaos.analogic.com>
To: "Theodore Ts'o" <tytso@mit.edu>
Cc: Larry McVoy <lm@bitmover.com>, Ricky Beam <jfbeam@bluetronic.net>,
Linux Kernel Mail List <linux-kernel@vger.kernel.org>
Subject: Re: data from kernel.bkbits.net
Date: Mon, 24 Nov 2003 16:34:43 -0500 (EST) [thread overview]
Message-ID: <Pine.LNX.4.53.0311241628230.3173@chaos> (raw)
In-Reply-To: <20031124203321.GA9036@thunk.org>
On Mon, 24 Nov 2003, Theodore Ts'o wrote:
> On Mon, Nov 24, 2003 at 03:05:24PM -0500, Richard B. Johnson wrote:
> > Attempt to copy the raw drive to /dev/null. If that works, the
> > drive is likely okay, but the fs got fsucked up by software. You
> > might be able to mount the drive on a 2.4.22 machine if you have a
> > spare. Then you might be able to selectively copy important stuff
> > to another drive, after which you can make a new file-system as
> > a "repair".
>
> The error messages Larry reported were obviously reported by the
> hardware, and were **not** filesystem errors.
>
> - Ted
Yes but an attempt to read beyond the limits of the physical
drive will provide you with a lot of **interesting** hardware
errors. This happens if the file-system gets corrupt.
And I'm not implying that the software screwed up either. The
software doesn't know if an "extra" bit was set during a write
to the drive. These things happen asd a result of bad RAM, bad
DMA, and other hardware-corrupting things....
So, the first check is to see if the drive can be read without
any reference to its contents. Since Read/Write is usually the
software implimentation detail of a direction bit, if you can
read, you can usually write.
Cheers,
Dick Johnson
Penguin : Linux version 2.4.22 on an i686 machine (797.90 BogoMips).
Note 96.31% of all statistics are fiction.
next prev parent reply other threads:[~2003-11-24 21:34 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-11-24 5:19 Larry McVoy
2003-11-24 7:34 ` H. Peter Anvin
2003-11-24 14:57 ` Larry McVoy
2003-11-24 15:43 ` Ricky Beam
2003-11-24 15:50 ` Larry McVoy
2003-11-24 19:17 ` Ricky Beam
2003-11-24 19:24 ` Larry McVoy
2003-11-24 19:35 ` Jamie Lokier
2003-11-24 20:05 ` Richard B. Johnson
2003-11-24 20:33 ` Theodore Ts'o
2003-11-24 21:34 ` Richard B. Johnson [this message]
2003-11-24 22:24 ` Larry McVoy
2003-11-24 22:38 ` Jamie Lokier
2003-11-25 0:30 ` Theodore Ts'o
2003-11-24 20:09 ` Ricky Beam
2003-11-24 9:48 ` Willy Tarreau
2003-11-25 15:00 ` Ben Collins
2003-11-24 19:14 Adam Radford
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=Pine.LNX.4.53.0311241628230.3173@chaos \
--to=root@chaos.analogic.com \
--cc=jfbeam@bluetronic.net \
--cc=linux-kernel@vger.kernel.org \
--cc=lm@bitmover.com \
--cc=tytso@mit.edu \
/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®