From: John Robinson <john.robinson@anonymous.org.uk>
To: Linux RAID <linux-raid@vger.kernel.org>
Cc: Goswin von Brederlow <goswin-v-b@web.de>
Subject: Re: Poor write performance with write-intent bitmap?
Date: Thu, 23 Apr 2009 09:04:44 +0100 [thread overview]
Message-ID: <49F0211C.3010306@anonymous.org.uk> (raw)
In-Reply-To: <20090422142148.GC13280@skl-net.de>
On 22/04/2009 15:21, Andre Noll wrote:
> On 13:41, John Robinson wrote:
>>> Normal shutdown should put the raid in read-only mode as last step. At
>>> least Debian does that. That way even a mounted raid will be clean
>>> after reboot.
>> Yes, I would have thought it should as well. But I've just looked at
>> CentOS 5's /etc/rc.d/halt and as far as I can see it doesn't try to
>> switch md devices to read-only.
>
> There's no need to do that in the shutdown script as the kernel will
> switch all arrays to read-only mode on halt/reboot.
>
> Moreover, as raid arrays are automatically marked clean if no writes
> are pending for some small time period, a simple "sync; sleep 1"
> at the end of the shutdown script is usually enough to have a clean
> array during the next boot.
But that's still only "usually". Considering the enormous efforts taken
to unmount filesystems (or remount them read-only) so they're certain to
be clean at the next startup, it seems odd to settle for "usually"...
and CentOS 5 doesn't even appear to do that.
Goswin, please can you tell me what command Debian uses? I think I want
to combine both of these into my systems' halt scripts.
Cheers,
John.
next prev parent reply other threads:[~2009-04-23 8:04 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-04-20 17:12 Performance of a software raid 5 Johannes Segitz
2009-04-20 23:46 ` John Robinson
2009-04-21 0:10 ` Johannes Segitz
2009-04-21 0:52 ` John Robinson
2009-04-21 1:05 ` Johannes Segitz
2009-04-21 1:12 ` John Robinson
2009-04-21 1:19 ` NeilBrown
2009-04-21 2:04 ` Johannes Segitz
2009-04-21 5:46 ` Neil Brown
2009-04-21 12:40 ` Johannes Segitz
2009-04-24 13:49 ` Johannes Segitz
2009-04-26 17:03 ` Johannes Segitz
2009-04-21 18:56 ` Corey Hickey
2009-04-22 12:29 ` Bill Davidsen
2009-04-22 22:32 ` Corey Hickey
2009-04-22 9:07 ` Goswin von Brederlow
2009-04-21 0:44 ` Poor write performance with write-intent bitmap? John Robinson
2009-04-21 1:33 ` NeilBrown
2009-04-21 2:13 ` John Robinson
2009-04-21 5:50 ` Neil Brown
2009-04-21 12:05 ` John Robinson
2009-05-22 23:00 ` Redeeman
2009-04-22 9:16 ` Goswin von Brederlow
2009-04-22 12:41 ` John Robinson
2009-04-22 14:02 ` Goswin von Brederlow
2009-04-23 7:48 ` John Robinson
2009-04-22 14:21 ` Andre Noll
2009-04-23 8:04 ` John Robinson [this message]
2009-04-23 20:23 ` Goswin von Brederlow
2009-04-21 16:00 ` Bill Davidsen
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=49F0211C.3010306@anonymous.org.uk \
--to=john.robinson@anonymous.org.uk \
--cc=goswin-v-b@web.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).