From: Bill Davidsen <davidsen@tmr.com>
To: linux-kernel@vger.kernel.org
Subject: [2.6.11-rc4-bk9] Bad behaviour using RAID
Date: Mon, 28 Feb 2005 17:54:09 -0500 [thread overview]
Message-ID: <d006fl$7eq$1@gatekeeper.tmr.com> (raw)
I just added a few more 200GB drives on a Promise controller, and they
are configured as:
md0 - raid1, 6GB of stuff I really don't want to lose 64k stripe
md1 - raid0, 350GB for streaming video capture, 512k stripe
This space was configured with "mdadm" if that makes a difference, and I
didn't get the right options to make it start at boot, so it gets run
out of rc.local. I doubt that makes a difference, but I mention it.
Since this machine is often idle for hours, I have the two drives of
interest set to spin down after 20 minutes of disuse. Other than a
fairly slow start I have had no problems with restarting after an idle
period.
There are no problems with data corruption or error messages, nor have I
ever see any indication of a rebuild in progress. HOWEVER, every once in
a while the disk light comes on and the system becomes very
unresponsive. Since the Promise controller isn't connected to the disk
light, the activity is one the original (120gb, 200gb) drives somewhere.
The system is unresponsive for 1-2 minutes, although not totally so, I
can look at /proc/mdstat and see no rebuild, and even guess that the
raid drives are spun down because access takes seconds after the system
seems normal.
The system was up since the night the kernel was released, and I never
saw any such behaviour until I added the other drives, but the activity
is not on the new drives. This happens 1-2 times a day by observation,
and since I use the system remotely during the week, I can only say that
I haven't seen the unresponsive behaviour before, nor observed it on the
weekend in the office. If I see it several times a day it's likely to be
happening more often.
If anyone has even the slightest clue what's happening, I'd love to hear
it. It started when the new hardware was added, but occurs on the old.
--
-bill davidsen (davidsen@tmr.com)
"The secret to procrastination is to put things off until the
last possible moment - but no longer" -me
reply other threads:[~2005-02-28 22:49 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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='d006fl$7eq$1@gatekeeper.tmr.com' \
--to=davidsen@tmr.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