From: NeilBrown <neilb@suse.de>
To: Lukasz Dorau <lukasz.dorau@intel.com>
Cc: linux-raid@vger.kernel.org, dan.j.williams@intel.com,
ed.ciechanowski@intel.com
Subject: Re: [PATCH] imsm: fix: rebuild does not continue after reboot
Date: Mon, 23 Apr 2012 09:52:05 +1000 [thread overview]
Message-ID: <20120423095205.40cdacde@notabene.brown> (raw)
In-Reply-To: <20120420114502.2484.68027.stgit@gklab-128-085.igk.intel.com>
[-- Attachment #1: Type: text/plain, Size: 2355 bytes --]
On Fri, 20 Apr 2012 13:45:02 +0200 Lukasz Dorau <lukasz.dorau@intel.com>
wrote:
> If system is rebooted during rebuild, md driver changes sync_action
> from 'recover' to 'idle' (during stopping all md devices).
> If mdmon is still running then, it detects the change of sync_action state,
> finishes rebuild and writes metadata to disks. After computer's restart
> the RAID volume is in Normal state in OROM and rebuild seems to be finished.
> After system's start-up RAID volume is in auto-read-only state
> and metadata is in Dirty state. Rebuild seems to be finished but it is not.
> Data is inconsistent (out-of-sync).
>
> When mdmon detects the change of sync_action from 'recover' to 'idle',
> it has to check if rebuild is really finished. Appropriate test was added.
> Now mdmon examines each volume's member if it is being rebuilt.
>
> Signed-off-by: Lukasz Dorau <lukasz.dorau@intel.com>
> ---
> super-intel.c | 17 +++++++++++++++++
> 1 files changed, 17 insertions(+), 0 deletions(-)
>
> diff --git a/super-intel.c b/super-intel.c
> index e405d97..1ad5e47 100644
> --- a/super-intel.c
> +++ b/super-intel.c
> @@ -7273,6 +7273,8 @@ static void imsm_set_disk(struct active_array *a, int n, int state)
> struct imsm_dev *dev = get_imsm_dev(super, inst);
> struct imsm_map *map = get_imsm_map(dev, MAP_0);
> struct imsm_disk *disk;
> + struct mdinfo *mdi;
> + int recovery_not_finished = 0;
> int failed;
> __u32 ord;
> __u8 map_state;
> @@ -7313,6 +7315,21 @@ static void imsm_set_disk(struct active_array *a, int n, int state)
> dprintf("normal: ");
> if (is_rebuilding(dev)) {
> dprintf("while rebuilding");
> + /* check if recovery is really finished */
> + for (mdi = a->info.devs; mdi ; mdi = mdi->next)
> + if (mdi->recovery_start != MaxSector) {
> + recovery_not_finished = 1;
> + break;
> + }
> + if (recovery_not_finished) {
> + dprintf("\nimsm: Rebuild has not finished yet, "
> + "state not changed");
> + if (a->last_checkpoint < mdi->recovery_start) {
> + a->last_checkpoint = mdi->recovery_start;
> + super->updates_pending++;
> + }
> + break;
> + }
> end_migration(dev, super, map_state);
> map = get_imsm_map(dev, MAP_0);
> map->failed_disk_num = ~0;
Applied, thanks.
NeilBrown
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 828 bytes --]
prev parent reply other threads:[~2012-04-22 23:52 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-04-20 11:45 [PATCH] imsm: fix: rebuild does not continue after reboot Lukasz Dorau
2012-04-22 23:52 ` NeilBrown [this message]
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=20120423095205.40cdacde@notabene.brown \
--to=neilb@suse.de \
--cc=dan.j.williams@intel.com \
--cc=ed.ciechanowski@intel.com \
--cc=linux-raid@vger.kernel.org \
--cc=lukasz.dorau@intel.com \
/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).