From: Mike Snitzer <snitzer@redhat.com>
To: Song Liu <songliubraving@fb.com>, axboe@kernel.dk
Cc: linux-raid@vger.kernel.org, dm-devel@redhat.com,
Xiao Ni <xni@redhat.com>,
linux-kernel@vger.kernel.org,
Matthew Ruffell <matthew.ruffell@canonical.com>
Subject: Re: [dm-devel] Revert "dm raid: remove unnecessary discard limits for raid10"
Date: Wed, 9 Dec 2020 17:36:15 -0500 [thread overview]
Message-ID: <20201209223615.GA2752@redhat.com> (raw)
In-Reply-To: <20201209215814.2623617-1-songliubraving@fb.com>
On Wed, Dec 09 2020 at 4:58pm -0500,
Song Liu <songliubraving@fb.com> wrote:
> This reverts commit f0e90b6c663a7e3b4736cb318c6c7c589f152c28.
>
> Matthew Ruffell reported data corruption in raid10 due to the changes
> in discard handling [1]. Revert these changes before we find a proper fix.
>
> [1] https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1907262/
> Cc: Matthew Ruffell <matthew.ruffell@canonical.com>
> Cc: Xiao Ni <xni@redhat.com>
> Cc: Mike Snitzer <snitzer@redhat.com>
> Signed-off-by: Song Liu <songliubraving@fb.com>
If you're reverting all the MD code that enabled this DM change, then
obviously the DM change must be reverted too. But please do _not_
separate the DM revert from the MD reverts.
Please include this in a v2 pull request to Jens.
Mike
> ---
> drivers/md/dm-raid.c | 11 +++++++++++
> 1 file changed, 11 insertions(+)
>
> diff --git a/drivers/md/dm-raid.c b/drivers/md/dm-raid.c
> index 9c1f7c4de65b3..dc8568ab96f24 100644
> --- a/drivers/md/dm-raid.c
> +++ b/drivers/md/dm-raid.c
> @@ -3728,6 +3728,17 @@ static void raid_io_hints(struct dm_target *ti, struct queue_limits *limits)
>
> blk_limits_io_min(limits, chunk_size_bytes);
> blk_limits_io_opt(limits, chunk_size_bytes * mddev_data_stripes(rs));
> +
> + /*
> + * RAID10 personality requires bio splitting,
> + * RAID0/1/4/5/6 don't and process large discard bios properly.
> + */
> + if (rs_is_raid10(rs)) {
> + limits->discard_granularity = max(chunk_size_bytes,
> + limits->discard_granularity);
> + limits->max_discard_sectors = min_not_zero(rs->md.chunk_sectors,
> + limits->max_discard_sectors);
> + }
> }
>
> static void raid_postsuspend(struct dm_target *ti)
> --
> 2.24.1
>
--
dm-devel mailing list
dm-devel@redhat.com
https://www.redhat.com/mailman/listinfo/dm-devel
WARNING: multiple messages have this Message-ID (diff)
From: Mike Snitzer <snitzer@redhat.com>
To: Song Liu <songliubraving@fb.com>, axboe@kernel.dk
Cc: linux-raid@vger.kernel.org, linux-kernel@vger.kernel.org,
dm-devel@redhat.com,
Matthew Ruffell <matthew.ruffell@canonical.com>,
Xiao Ni <xni@redhat.com>
Subject: Re: Revert "dm raid: remove unnecessary discard limits for raid10"
Date: Wed, 9 Dec 2020 17:36:15 -0500 [thread overview]
Message-ID: <20201209223615.GA2752@redhat.com> (raw)
In-Reply-To: <20201209215814.2623617-1-songliubraving@fb.com>
On Wed, Dec 09 2020 at 4:58pm -0500,
Song Liu <songliubraving@fb.com> wrote:
> This reverts commit f0e90b6c663a7e3b4736cb318c6c7c589f152c28.
>
> Matthew Ruffell reported data corruption in raid10 due to the changes
> in discard handling [1]. Revert these changes before we find a proper fix.
>
> [1] https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1907262/
> Cc: Matthew Ruffell <matthew.ruffell@canonical.com>
> Cc: Xiao Ni <xni@redhat.com>
> Cc: Mike Snitzer <snitzer@redhat.com>
> Signed-off-by: Song Liu <songliubraving@fb.com>
If you're reverting all the MD code that enabled this DM change, then
obviously the DM change must be reverted too. But please do _not_
separate the DM revert from the MD reverts.
Please include this in a v2 pull request to Jens.
Mike
> ---
> drivers/md/dm-raid.c | 11 +++++++++++
> 1 file changed, 11 insertions(+)
>
> diff --git a/drivers/md/dm-raid.c b/drivers/md/dm-raid.c
> index 9c1f7c4de65b3..dc8568ab96f24 100644
> --- a/drivers/md/dm-raid.c
> +++ b/drivers/md/dm-raid.c
> @@ -3728,6 +3728,17 @@ static void raid_io_hints(struct dm_target *ti, struct queue_limits *limits)
>
> blk_limits_io_min(limits, chunk_size_bytes);
> blk_limits_io_opt(limits, chunk_size_bytes * mddev_data_stripes(rs));
> +
> + /*
> + * RAID10 personality requires bio splitting,
> + * RAID0/1/4/5/6 don't and process large discard bios properly.
> + */
> + if (rs_is_raid10(rs)) {
> + limits->discard_granularity = max(chunk_size_bytes,
> + limits->discard_granularity);
> + limits->max_discard_sectors = min_not_zero(rs->md.chunk_sectors,
> + limits->max_discard_sectors);
> + }
> }
>
> static void raid_postsuspend(struct dm_target *ti)
> --
> 2.24.1
>
next prev parent reply other threads:[~2020-12-09 22:36 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-12-09 21:58 [dm-devel] [PATCH] Revert "dm raid: remove unnecessary discard limits for raid10" Song Liu
2020-12-09 21:58 ` Song Liu
2020-12-09 22:36 ` Mike Snitzer [this message]
2020-12-09 22:36 ` Mike Snitzer
2020-12-09 23:14 ` [dm-devel] " Song Liu
2020-12-09 23:14 ` Song Liu
2020-12-09 22:38 ` [dm-devel] " Mike Snitzer
2020-12-09 22:38 ` Mike Snitzer
2020-12-10 4:09 ` [dm-devel] [PATCH] " kernel test robot
2020-12-10 4:09 ` kernel test robot
2020-12-10 4:09 ` kernel test robot
2020-12-10 5:33 ` [dm-devel] " kernel test robot
2020-12-10 5:33 ` kernel test robot
2020-12-10 5:33 ` kernel test robot
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=20201209223615.GA2752@redhat.com \
--to=snitzer@redhat.com \
--cc=axboe@kernel.dk \
--cc=dm-devel@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-raid@vger.kernel.org \
--cc=matthew.ruffell@canonical.com \
--cc=songliubraving@fb.com \
--cc=xni@redhat.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.