From: "Guilherme G. Piccoli" <gpiccoli@canonical.com>
To: NeilBrown <neilb@suse.com>, linux-raid@vger.kernel.org
Cc: jay.vosburgh@canonical.com, songliubraving@fb.com,
dm-devel@redhat.com, Neil F Brown <nfbrown@suse.com>,
linux-block@vger.kernel.org
Subject: Re: [PATCH 1/2] md/raid0: Introduce new array state 'broken' for raid0
Date: Tue, 30 Jul 2019 08:43:13 -0300 [thread overview]
Message-ID: <20348d5f-fa41-58f1-a7d8-2989233b97f1@canonical.com> (raw)
In-Reply-To: <87wog0l6u2.fsf@notabene.neil.brown.name>
On 29/07/2019 21:11, NeilBrown wrote:
> [...]
>> - else {
>> +
>> + if ((mddev->pers->level == 0) &&
>
> Don't test if ->level is 0. Instead, test if ->is_missing_dev is not
> NULL.
>
> NeilBrown
Hi Neil, thanks for the feedback. I'll change that in a potential V2,
(if the patches are likely to be accepted), good idea.
Cheers,
Guilherme
>
>
>> + ((st == clean) || (st == broken))) {
>> + if (mddev->pers->is_missing_dev(mddev))
>> + st = broken;
>> + else
>> + st = clean;
>> + }
>> + } else {
>> if (list_empty(&mddev->disks) &&
>> mddev->raid_disks == 0 &&
>> mddev->dev_sectors == 0)
>> @@ -4315,6 +4329,7 @@ array_state_store(struct mddev *mddev, const char *buf, size_t len)
>> break;
>> case write_pending:
>> case active_idle:
>> + case broken:
>> /* these cannot be set */
>> break;
>> }
>> diff --git a/drivers/md/md.h b/drivers/md/md.h
>> index 41552e615c4c..e7b42b75701a 100644
>> --- a/drivers/md/md.h
>> +++ b/drivers/md/md.h
>> @@ -590,6 +590,8 @@ struct md_personality
>> int (*congested)(struct mddev *mddev, int bits);
>> /* Changes the consistency policy of an active array. */
>> int (*change_consistency_policy)(struct mddev *mddev, const char *buf);
>> + /* Check if there is any missing/failed members - RAID0 only for now. */
>> + bool (*is_missing_dev)(struct mddev *mddev);
>> };
>>
>> struct md_sysfs_entry {
>> diff --git a/drivers/md/raid0.c b/drivers/md/raid0.c
>> index 58a9cc5193bf..79618a6ae31a 100644
>> --- a/drivers/md/raid0.c
>> +++ b/drivers/md/raid0.c
>> @@ -455,6 +455,31 @@ static inline int is_io_in_chunk_boundary(struct mddev *mddev,
>> }
>> }
>>
>> +bool raid0_is_missing_dev(struct mddev *mddev)
>> +{
>> + struct md_rdev *rdev;
>> + static int already_missing;
>> + int def_disks, work_disks = 0;
>> + struct r0conf *conf = mddev->private;
>> +
>> + def_disks = conf->strip_zone[0].nb_dev;
>> + rdev_for_each(rdev, mddev)
>> + if (rdev->bdev->bd_disk->flags & GENHD_FL_UP)
>> + work_disks++;
>> +
>> + if (unlikely(def_disks - work_disks)) {
>> + if (!already_missing) {
>> + already_missing = 1;
>> + pr_warn("md: %s: raid0 array has %d missing/failed members\n",
>> + mdname(mddev), (def_disks - work_disks));
>> + }
>> + return true;
>> + }
>> +
>> + already_missing = 0;
>> + return false;
>> +}
>> +
>> static void raid0_handle_discard(struct mddev *mddev, struct bio *bio)
>> {
>> struct r0conf *conf = mddev->private;
>> @@ -789,6 +814,7 @@ static struct md_personality raid0_personality=
>> .takeover = raid0_takeover,
>> .quiesce = raid0_quiesce,
>> .congested = raid0_congested,
>> + .is_missing_dev = raid0_is_missing_dev,
>> };
>>
>> static int __init raid0_init (void)
>> --
>> 2.22.0
next prev parent reply other threads:[~2019-07-30 11:43 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-07-29 20:31 [PATCH 0/2] Introduce new raid0 state 'broken' Guilherme G. Piccoli
2019-07-29 20:31 ` [PATCH 1/2] md/raid0: Introduce new array state 'broken' for raid0 Guilherme G. Piccoli
2019-07-30 0:11 ` NeilBrown
2019-07-30 11:43 ` Guilherme G. Piccoli [this message]
2019-07-30 6:20 ` Bob Liu
2019-07-30 12:18 ` Guilherme G. Piccoli
2019-07-31 0:28 ` NeilBrown
2019-07-31 13:04 ` Guilherme G. Piccoli
2019-07-31 19:47 ` Song Liu
2019-07-31 19:43 ` Song Liu
2019-08-01 12:07 ` Guilherme G. Piccoli
2019-08-16 13:48 ` Guilherme G. Piccoli
2019-07-29 20:31 ` [PATCH 2/2] mdadm: " Guilherme G. Piccoli
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=20348d5f-fa41-58f1-a7d8-2989233b97f1@canonical.com \
--to=gpiccoli@canonical.com \
--cc=dm-devel@redhat.com \
--cc=jay.vosburgh@canonical.com \
--cc=linux-block@vger.kernel.org \
--cc=linux-raid@vger.kernel.org \
--cc=neilb@suse.com \
--cc=nfbrown@suse.com \
--cc=songliubraving@fb.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).