From: Molle Bestefich <molle.bestefich@gmail.com>
To: linux-raid@vger.kernel.org
Subject: Re: kernel panic??
Date: Tue, 8 Mar 2005 04:41:04 +0100 [thread overview]
Message-ID: <62b0912f050307194144c3ea8@mail.gmail.com> (raw)
In-Reply-To: <422D079B.7050507@advocap.org>
John McMonagle wrote:
> All panics seem to be associated with accessing bad spot on sdb
> It seems really strange that one can get panic from a drive problem.
<sarcasm> Wow, yeah, never seen that happen with Linux before! </sarcasm>
Just for the fun of it, try digging up a disk which has a bad spot
somewhere, preferably track 0, otherwise point an extended partition
table to the bad spot. Then try and get your linux box to even boot
with the disk in the system :-D.
God, Linux is so stable.. Bwahaha...
next prev parent reply other threads:[~2005-03-08 3:41 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-03-02 15:49 slow resync?? John McMonagle
2005-03-03 14:12 ` slow resync+ kernel panic?? John McMonagle
2005-03-08 2:02 ` John McMonagle
2005-03-08 3:41 ` Molle Bestefich [this message]
2005-03-08 3:51 ` Molle Bestefich
-- strict thread matches above, loose matches on Subject: below --
2005-04-11 16:30 kernel panic! sauro
2005-04-11 17:09 ` Lee Revell
2008-03-17 2:36 kernel panic??? zshan
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=62b0912f050307194144c3ea8@mail.gmail.com \
--to=molle.bestefich@gmail.com \
--cc=linux-raid@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.