From: linux@horizon.com
To: linux@horizon.com, neilb@suse.de
Cc: linux-raid@vger.kernel.org
Subject: Re: Interesting RAID checking observations
Date: 28 Aug 2006 09:15:52 -0400 [thread overview]
Message-ID: <20060828131552.5776.qmail@science.horizon.com> (raw)
In-Reply-To: <17650.16675.561765.886119@cse.unsw.edu.au>
> I don't think the processor is saturating. I've seen reports of this
> sort of thing before and until recently had no idea what was happening,
> couldn't reproduce it, and couldn't think of any more useful data to
> collect.
Well I can reproduce it easily enough. It's a production server, but
I can do low-risk experiments after hours.
I'd like to note that the symptoms include not even being
able to *type* at the console, which I thought was all in-kernel
code, not subject to being swapped out. But whatever.
> I'm not sure exactly how that translates into the machine being
> unresponsive, but it wouldn't surprise me. I'll try to post a patch
> for that to linux-raid in a soonish.
I look forward to testing it!
> How much RAM does this system have?
1 GB (ECC). 133 MHz SDR SDRAM.
> Again, you aren't the first to report this. I haven't seen it myself,
> but my regular test machine is busy at the moment. I'll try to
> organise some testing soon.
I can do a fair bit of experimentation with this machine, as long as I
don't lose the data that's on it.
> Thanks for the reports.
Thanks for the response! Sorry to be a pain.
next prev parent reply other threads:[~2006-08-28 13:15 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-08-27 6:46 Interesting RAID checking observations linux
2006-08-27 11:18 ` Justin Piszcz
2006-08-28 13:00 ` linux
2006-08-28 1:04 ` Neil Brown
2006-08-28 13:15 ` linux [this message]
2006-09-04 17:16 ` Bill Davidsen
2006-09-04 21:15 ` linux
-- strict thread matches above, loose matches on Subject: below --
2006-09-21 6:58 linux
2006-09-21 18:48 ` linux
2006-09-21 18:55 ` Rob Bray
2006-09-22 2:13 ` linux
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=20060828131552.5776.qmail@science.horizon.com \
--to=linux@horizon.com \
--cc=linux-raid@vger.kernel.org \
--cc=neilb@suse.de \
/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;
as well as URLs for NNTP newsgroup(s).