From: David Weinehall <tao@acc.umu.se>
To: "Richard B. Johnson" <johnson@groveland.analogic.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Linux 2.4.3
Date: Thu, 8 Mar 2001 16:44:19 +0100 [thread overview]
Message-ID: <20010308164419.C18769@khan.acc.umu.se> (raw)
In-Reply-To: <Pine.LNX.4.21.0103052124250.1132-100000@groveland.analogic.com>
In-Reply-To: <Pine.LNX.4.21.0103052124250.1132-100000@groveland.analogic.com>; from johnson@groveland.analogic.com on Mon, Mar 05, 2001 at 09:35:30PM -0500
On Mon, Mar 05, 2001 at 09:35:30PM -0500, Richard B. Johnson wrote:
>
> Attempts to run linux-2.4.3-pre2 on chaos.analogic.com results
> in **MASSIVE** file-system destruction. I have (had) all SCSI
> disks, using the BusLogic controller.
>
> There is something **MAJOR** going on BAD, BAD, BAD, even disks
> that were not mounted got trashed.
>
> This is (was) a 400MHz SMP machine with 256 Mb of RAM. I don't
> know what else to say, since I have nothing to mount. I can
> "get back" but it will take several days. I have to install a
> minimum system then restore everything from tapes.
>
> I -- S T R O N G L Y -- suggest that nobody use this kernel with
> a BusLogic SCSI controller until this problem is fixed.
>
> This is being sent from another machine, not on the list (actually
> from home where I am trying to see what happened -- I brought all
> 4 of my disks home). It looks like some kind of a loop. I have
> a pattern written throughout one of the disks.
Anything new on this? It sounds rather strange considering your
unmounted disks got trashed too, so either it's a problem with the
SCSI subsystem (or the driver; it might be a bug that got triggered
by something else) or some sort of hardware failure.
What kind of pattern was repeated on the disk, by the way? Maybe this
could shed some light unto what happened.
/David Weinehall
_ _
// David Weinehall <tao@acc.umu.se> /> Northern lights wander \\
// Project MCA Linux hacker // Dance across the winter sky //
\> http://www.acc.umu.se/~tao/ </ Full colour fire </
next prev parent reply other threads:[~2001-03-08 15:45 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-03-06 2:35 Richard B. Johnson
2001-03-06 3:02 ` Mike Fedyk
2001-03-06 3:33 ` Linux 2.4.2-ac12 Scott M. Hoffman
2001-03-06 4:21 ` Linus Torvalds
2001-03-06 10:34 ` God
2001-03-06 13:17 ` Scott M. Hoffman
2001-03-06 13:30 ` Alan Cox
2001-03-06 13:56 ` Scott M. Hoffman
2001-03-06 14:09 ` Alan Cox
2001-03-06 18:10 ` Linux 2.4.2-ac12, ac11 no good either Scott M. Hoffman
2001-03-07 3:31 ` Linux 2.4.2-ac12 God
2001-03-06 18:07 ` Wayne Whitney
2001-03-06 23:43 ` God
2001-03-06 3:42 ` Linux 2.4.3 Linus Torvalds
2001-03-08 0:16 ` Krzysztof Halasa
2001-03-08 15:44 ` David Weinehall [this message]
2001-03-08 16:09 ` Richard B. Johnson
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=20010308164419.C18769@khan.acc.umu.se \
--to=tao@acc.umu.se \
--cc=johnson@groveland.analogic.com \
--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®