From: Reuben Farrelly <reuben-lkml@reub.net>
To: NeilBrown <neilb@suse.de>
Cc: linux-raid@vger.kernel.org, linux-kernel@vger.kernel.org,
Andrew Morton <akpm@osdl.org>
Subject: Re: [PATCH 000 of 3] md: Introduction - 3 bugfixs for -mm
Date: Thu, 18 May 2006 00:04:40 +1200 [thread overview]
Message-ID: <446B1158.8030608@reub.net> (raw)
In-Reply-To: <20060516111036.2649.patches@notabene>
On 16/05/2006 1:12 p.m., NeilBrown wrote:
> The first of these fixes issues with the new bmap based bitmap file
> access code, and possibly should be an -mm hotfix, and without it,
> 'internal' bitmaps don't work any more :-(
>
> Others are minor and unrelated.
>
> Thanks,
> NeilBrown
>
>
> [PATCH 001 of 3] md: Change md/bitmap file handling to use bmap to file blocks-fix
> [PATCH 002 of 3] md: Fix inverted test for 'repair' directive.
> [PATCH 003 of 3] md: Calculate correct array size for raid10 in new offset mode.
Patch 1 fixes the problems I was having with RAID-1 arrays not able to start up
on 2.6.17-rc4-mm1. Thanks for that.
However things appear still not quite right on boot, as each mount works but
displays as though it didn't work, ie:
md: considering sdc2 ...
md: adding sdc2 ...
md: adding sda2 ...
md: created md0
md: bind<sda2>
md: bind<sdc2>
md: running: <sdc2><sda2>
raid1: raid set md0 active with 0 out of 2 mirrors
0 out of 2 ?
cat /proc/mdstats shows that everything does in fact seem to be working:
md0 : active raid1 sdc2[1] sda2[0]
24410688 blocks [2/2] [UU]
bitmap: 21/187 pages [84KB], 64KB chunk
The array otherwise seems to be fine. I guess it's just a visual glitch.
reuben
next prev parent reply other threads:[~2006-05-17 12:04 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-05-16 1:12 [PATCH 000 of 3] md: Introduction - 3 bugfixs for -mm NeilBrown
2006-05-16 1:13 ` [PATCH 001 of 3] md: Change md/bitmap file handling to use bmap to file blocks-fix NeilBrown
2006-05-16 1:54 ` Andrew Morton
2006-05-16 2:16 ` Neil Brown
2006-05-16 1:13 ` [PATCH 002 of 3] md: Fix inverted test for 'repair' directive NeilBrown
2006-05-16 1:13 ` [PATCH 003 of 3] md: Calculate correct array size for raid10 in new offset mode NeilBrown
2006-05-17 12:04 ` Reuben Farrelly [this message]
2006-05-17 23:28 ` [PATCH 000 of 3] md: Introduction - 3 bugfixs for -mm Neil Brown
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=446B1158.8030608@reub.net \
--to=reuben-lkml@reub.net \
--cc=akpm@osdl.org \
--cc=linux-kernel@vger.kernel.org \
--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).