diff options
author | Andre Noll <maan@systemlinux.org> | 2009-06-18 08:48:06 +1000 |
---|---|---|
committer | NeilBrown <neilb@suse.de> | 2009-06-18 08:48:06 +1000 |
commit | 8c6ac868b107ed50a46204f6d14e2ad9443ff146 (patch) | |
tree | a0690ce92ed1993cc3211448948f3964c389c082 /drivers/md/raid10.c | |
parent | 50ac168a6e0a061bf5346d53aa9e7beb94c97527 (diff) | |
download | linux-8c6ac868b107ed50a46204f6d14e2ad9443ff146.tar.bz2 |
md: Push down reconstruction log message to personality code.
Currently, the md layer checks in analyze_sbs() if the raid level
supports reconstruction (mddev->level >= 1) and if reconstruction is
in progress (mddev->recovery_cp != MaxSector).
Move that printk into the personality code of those raid levels that
care (levels 1, 4, 5, 6, 10).
Signed-off-by: Andre Noll <maan@systemlinux.org>
Signed-off-by: NeilBrown <neilb@suse.de>
Diffstat (limited to 'drivers/md/raid10.c')
-rw-r--r-- | drivers/md/raid10.c | 4 |
1 files changed, 4 insertions, 0 deletions
diff --git a/drivers/md/raid10.c b/drivers/md/raid10.c index 30029a312cf5..ae12ceafe10c 100644 --- a/drivers/md/raid10.c +++ b/drivers/md/raid10.c @@ -2186,6 +2186,10 @@ static int run(mddev_t *mddev) goto out_free_conf; } + if (mddev->recovery_cp != MaxSector) + printk(KERN_NOTICE "raid10: %s is not clean" + " -- starting background reconstruction\n", + mdname(mddev)); printk(KERN_INFO "raid10: raid set %s active with %d out of %d devices\n", mdname(mddev), mddev->raid_disks - mddev->degraded, |