From: "Mark Williams (MWP)" <mwp@internode.on.net>
To: Tomas Szepe <szepe@pinerecords.com>
Cc: Linux Kernel <linux-kernel@vger.kernel.org>
Subject: Re: ReiserFS causing kernel panic?
Date: Mon, 13 Oct 2003 01:54:34 +0930 [thread overview]
Message-ID: <20031012162434.GB725@linux.comp> (raw)
In-Reply-To: <20031012143245.GA21010@louise.pinerecords.com>
> On Oct-12 2003, Sun, 23:30 +0930
> Mark Williams (MWP) <mwp@internode.on.net> wrote:
>
> > > "Mark Williams (MWP)" <mwp@internode.on.net> writes:
> > >
> > > > I am having rather ugly problems with this card using the PDC20269 chip.
> > > > Almost as soon as either of the HDDs on the controller are used, the
> > > > kernel hangs solid with a dump of debugging info.
> > >
> > > That dump could be useful. Also full output of dmesg and "lspci -vv"
> > > can be helpful.
> >
> > Ok, seems this is not a controller fault, but really a problem with
> > ReiserFS (!!).
>
> Do you really expect reiserfs code (or any other fs code for that matter)
> not to choke on a corrupted filesystem?
>
> Put the disk on a trusted controller and fsck.
No, i wouldnt expect reiserfs to handle the data on the FS, but i also
wouldnt have expected it to cause a kernel panic and hang the system.
next prev parent reply other threads:[~2003-10-12 16:24 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-10-12 12:13 Promise Ultra133-TX2 (PCD20269) Mark Williams (MWP)
2003-10-12 12:28 ` Måns Rullgård
2003-10-12 14:00 ` ReiserFS causing kernel panic? Mark Williams (MWP)
2003-10-12 14:32 ` Tomas Szepe
2003-10-12 16:24 ` Mark Williams (MWP) [this message]
2003-10-13 7:13 ` Hans Reiser
2003-10-12 20:42 ` Hans Reiser
2003-10-14 13:27 ` Promise Ultra133-TX2 (PCD20269) Marcelo Tosatti
[not found] <FNmF.1ky.9@gated-at.bofh.it>
[not found] ` <FNFZ.1JI.3@gated-at.bofh.it>
[not found] ` <FP59.3H0.17@gated-at.bofh.it>
[not found] ` <FVkc.42S.5@gated-at.bofh.it>
2003-10-12 22:27 ` ReiserFS causing kernel panic? Ihar 'Philips' Filipau
2003-10-13 5:28 ` Hans Reiser
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=20031012162434.GB725@linux.comp \
--to=mwp@internode.on.net \
--cc=linux-kernel@vger.kernel.org \
--cc=szepe@pinerecords.com \
/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