The Linux Kernel Mailing List
 help / color / mirror / Atom feed
From: Larry McVoy <lm@bitmover.com>
To: Ricky Beam <jfbeam@bluetronic.net>
Cc: Larry McVoy <lm@bitmover.com>,
	Linux Kernel Mail List <linux-kernel@vger.kernel.org>
Subject: Re: data from kernel.bkbits.net
Date: Mon, 24 Nov 2003 11:24:32 -0800	[thread overview]
Message-ID: <20031124192432.GA20839@work.bitmover.com> (raw)
In-Reply-To: <Pine.GSO.4.33.0311241405070.13188-100000@sweetums.bluetronic.net>

On Mon, Nov 24, 2003 at 02:17:44PM -0500, Ricky Beam wrote:
> On Mon, 24 Nov 2003, Larry McVoy wrote:
> >Sorry to be short but I already said that I'd eliminated this source of
> >error.  What did you think I was doing all weekend?
> 
> Let me be equally short.  Your original message gave no details of what
> debugging steps had been taken. (I can assume you would know what you're
> doing, but frankly, I could be wrong.)  You venture a guess that the
> system had been h4x0r3d in some inventive way to prevent your attempts
> to recover data and proceed to paste error messages from the 3ware
> driver that indicate a problem with the hardware (either driver bug,
> cabling, controller, or channel on that controller) including the
> drive itself.
> 
> Please do not attribute to hackers what is simply a half dead drive.  So,
> was the machine powered down for an extended period as I aluded? (to
> preserve the machine until someone had time to look at it.)

As I said, *both* drives have extensive file system problems.  No, the 
machine was not powered down for a long time, and no, neither of these
drives are old, and no, they are not from the same factory batch (they
aren't even the same vendor, one is a Maxtor and the other is a Seagate),
and yes, I of course tried different cable/controller/machine combos.

Any other questions?
-- 
---
Larry McVoy              lm at bitmover.com          http://www.bitmover.com/lm

  reply	other threads:[~2003-11-24 19:24 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-11-24  5:19 data from kernel.bkbits.net 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 [this message]
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
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
  -- strict thread matches above, loose matches on Subject: below --
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=20031124192432.GA20839@work.bitmover.com \
    --to=lm@bitmover.com \
    --cc=jfbeam@bluetronic.net \
    --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