From: Stef Telford <stef@chronozon.artofdns.com>
To: Neil Brown <neilb@cse.unsw.edu.au>
Cc: linux-raid@vger.kernel.org
Subject: Re: 2.5.62 oops and Raid-5
Date: 20 Feb 2003 19:42:22 -0500 [thread overview]
Message-ID: <1045788141.20059.18.camel@Indra.hades> (raw)
In-Reply-To: <15953.51012.470042.33785@notabene.cse.unsw.edu.au>
Neil wrote:
> Hmm... I cannot see how recent changes would have affected this, but
> does the following patch help?
actually, believe it or not but the patch made things
worse ?! that being said, i removed isapnp (as that
was also mentioned in one of the symoops) and the
oops on mount went away. Notice that the oops on
mount didnt stop the raid5 from being mounted
and accessible, jst it was annoying to see
an oops on mount. I can understand the
hotplug causing problems with raid (sudden
appearance of an entire 240gig raid5 disk
could cause hotplug to 'fire events' :) but
isapnp ? very curious indeed.
This of course means that i cant use my isa NIC, but
i can live without it. so no problem there.
one last thing that i noticed going from 2.5.58 to
2.5.62, if i do a cat /proc/mdstat it will stop at
around md198 (from md255 down to and including md198)
and the syslog will generate this error:
Feb 19 14:48:50 survivor kernel: proc_file_read: Apparent buffer
overflow!
This isnt really a 'major problem' for me, and i should
point out that even though md0 is mounted, it is currently
in degraded status and is being rebuilt. Incase that
makes any difference (jst in case ;)
regards
Stef
next prev parent reply other threads:[~2003-02-21 0:42 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-02-18 0:19 2.5.62 oops and Raid-5 Stef Telford
2003-02-18 5:40 ` Neil Brown
2003-02-21 0:42 ` Stef Telford [this message]
-- strict thread matches above, loose matches on Subject: below --
2003-02-18 0:50 Stef Telford
2003-02-17 23:46 Stef Telford
2003-02-18 5:02 ` Neil Brown
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=1045788141.20059.18.camel@Indra.hades \
--to=stef@chronozon.artofdns.com \
--cc=linux-raid@vger.kernel.org \
--cc=neilb@cse.unsw.edu.au \
/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