From: Molle Bestefich <molle.bestefich@gmail.com>
To: linux-raid@vger.kernel.org
Subject: Re: Spare disk could not sleep / standby
Date: Tue, 8 Mar 2005 06:20:36 +0100 [thread overview]
Message-ID: <62b0912f0503072120776e0b56@mail.gmail.com> (raw)
In-Reply-To: <16941.11443.107607.735855@cse.unsw.edu.au>
Neil Brown wrote:
> It is writes, but don't be scared. It is just super-block updates.
>
> In 2.6, the superblock is marked 'clean' whenever there is a period of
> about 20ms of no write activity. This increases the chance on a
> resync won't be needed after a crash.
> (unfortunately) the superblocks on the spares need to be updated too.
Ack, one of the cool things that a linux md array can do that others
can't is imho that the disks can spin down when inactive. Granted,
it's mostly for home users who want their desktop RAID to be quiet
when it's not in use, and their basement multi-terabyte facility to
use a minimum of power when idling, but anyway.
Is there any particular reason to update the superblocks every 20
msecs when they're already marked clean?
next prev parent reply other threads:[~2005-03-08 5:20 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-03-08 4:05 Spare disk could not sleep / standby Peter Evertz
2005-03-08 4:14 ` Guy
2005-03-08 4:40 ` Neil Brown
2005-03-08 5:20 ` Molle Bestefich [this message]
2005-03-08 5:36 ` Neil Brown
2005-03-08 5:46 ` Molle Bestefich
2005-03-08 6:03 ` Neil Brown
2005-03-08 6:24 ` Molle Bestefich
[not found] ` <422D625C.5020803@medien.uni-weimar.de>
2005-03-08 8:57 ` Molle Bestefich
2005-03-08 10:51 ` Tobias Hofmann
2005-03-08 13:13 ` Gordon Henderson
2005-03-09 5:11 ` Brad Campbell
2005-03-09 9:03 ` Tobias Hofmann
2005-03-08 8:51 ` David Greaves
2005-03-08 15:59 ` Mike Tran
2005-03-09 15:53 ` Spare disk could not sleep / standby [probably dangerous PATCH] Peter Evertz
2005-03-09 10:44 ` Mike Tran
2005-03-09 20:05 ` Peter Evertz
2005-03-09 16:29 ` Mike Tran
2005-03-09 23:20 ` Peter Evertz
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=62b0912f0503072120776e0b56@mail.gmail.com \
--to=molle.bestefich@gmail.com \
--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).