From: Alexander Stockinger <stockina@fmi.uni-passau.de>
To: linux-raid@vger.kernel.org
Subject: RAID 5 disks not spinning down
Date: Sat, 12 Mar 2005 09:54:40 +0100 [thread overview]
Message-ID: <d0uamj$s15$1@sea.gmane.org> (raw)
Hi all,
I have a linux software RAID 5 running on a Debian Sarge with 2.6.7-smp.
Since I installed the system (several kernel updates ago) the disks of
the RAID 5 won't stay spinned down. Having them sent to standy manually
using hdparm ends up in having the disks spin up within the next minute
or so.
To further investigate the problem I watched the /proc/diskstats file
for /dev/md0 and realized that prior to the spinup a single read access
to the RAID is issued - consequently the disks attached to the read spin
up again...
In order to find the reason for that read I did a dnotify on the mount
point of the RAID - however this didn't show ANY file read at all when
this single read access occurs.
I also tried noflushd - it simply keeps segfaulting after a few seconds.
Plus I'd be happy to resolve the issue in the first place instead of
fixing the symptoms anyway...
Any ideas what to do?
Thanks,
Alex
next reply other threads:[~2005-03-12 8:54 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-03-12 8:54 Alexander Stockinger [this message]
2005-03-12 14:09 ` RAID 5 disks not spinning down Brad Campbell
2005-03-12 14:19 ` Alexander Stockinger
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='d0uamj$s15$1@sea.gmane.org' \
--to=stockina@fmi.uni-passau.de \
--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 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).