From: NeilBrown <neilb@suse.de>
To: Joe Lawrence <joe.lawrence@stratus.com>
Cc: "Martin K. Petersen" <martin.petersen@oracle.com>,
"H. Peter Anvin" <hpa@zytor.com>,
Dan Williams <dan.j.williams@gmail.com>,
linux-raid <linux-raid@vger.kernel.org>
Subject: Re: RAID-10 keeps aborting
Date: Wed, 12 Jun 2013 13:15:43 +1000 [thread overview]
Message-ID: <20130612131543.1c79e077@notabene.brown> (raw)
In-Reply-To: <20130610101505.33b32d07@jlaw-desktop.mno.stratus.com>
[-- Attachment #1: Type: text/plain, Size: 2465 bytes --]
On Mon, 10 Jun 2013 10:15:05 -0400 Joe Lawrence <joe.lawrence@stratus.com>
wrote:
> A few outstanding questions that I have, maybe Neil or someone more
> familiar with the code could answer.
>
> Q1 - Is mddev->chunk_sectors is always zero for RAID1?
Not always. But often. It is largely ignored. I think the only effect is
to round the size of the device down to a multiple of the chunk size.
>
> Q2 - I noticed handle_write_finished calls narrow_write_error to try and
> potentially avoid failing an entire device. In my tests,
> narrow_write_error never succeeded as rdev->badblocks.shift = -1.
Yes. You would need a newer mdadm (from my git tree) to get badblocks.shift
to something else.
>
> I think this part of the bad block list code Neil has been working
> on. I don't suppose this is the proper place for MD to reset
> write_same_max_bytes to disable future WRITE SAME and handling the
> individual writes here instead of the block layer?
If a drive reports that WRITE SAME works, but it doesn't, then I'm not sure
that I can be happy about working with that drive.
If a drive has some quirky behaviour wrt WRITE SAME, then that should be
handled in some place where 'quirks' are handled - certainly not in md.
I've applied that patch below - thanks.
NeilBrown
>
> Regards,
>
> -- Joe
>
>
> From b12c24ee0fce802f35263da65d236694b01c99cf Mon Sep 17 00:00:00 2001
> From: Joe Lawrence <joe.lawrence@stratus.com>
> Date: Fri, 7 Jun 2013 15:25:54 -0400
> Subject: [PATCH] raid1: properly set blk_queue_max_write_same_sectors
>
> MD RAID1 chunk_sectors will always be zero, unlike RAID0, so RAID1 does
> not need to worry about limiting the write same sectors in that regard.
> Let disk_stack_limits choose the minimum of the RAID1 components write
> same values.
>
> Signed-off-by: Joe Lawrence <joe.lawrence@stratus.com>
> ---
> drivers/md/raid1.c | 3 ---
> 1 file changed, 3 deletions(-)
>
> diff --git a/drivers/md/raid1.c b/drivers/md/raid1.c
> index fd86b37..3dc9ad6 100644
> --- a/drivers/md/raid1.c
> +++ b/drivers/md/raid1.c
> @@ -2821,9 +2821,6 @@ static int run(struct mddev *mddev)
> if (IS_ERR(conf))
> return PTR_ERR(conf);
>
> - if (mddev->queue)
> - blk_queue_max_write_same_sectors(mddev->queue,
> - mddev->chunk_sectors);
> rdev_for_each(rdev, mddev) {
> if (!mddev->gendisk)
> continue;
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 828 bytes --]
next prev parent reply other threads:[~2013-06-12 3:15 UTC|newest]
Thread overview: 64+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-06-03 3:57 RAID-10 keeps aborting H. Peter Anvin
2013-06-03 4:05 ` H. Peter Anvin
2013-06-03 5:47 ` Dan Williams
2013-06-03 6:06 ` H. Peter Anvin
2013-06-03 6:14 ` Dan Williams
2013-06-03 6:30 ` H. Peter Anvin
2013-06-03 14:39 ` H. Peter Anvin
2013-06-11 16:47 ` Joe Lawrence
2013-06-11 17:12 ` H. Peter Anvin
2013-06-03 15:47 ` H. Peter Anvin
2013-06-03 16:09 ` Joe Lawrence
2013-06-03 17:22 ` Dan Williams
2013-06-03 17:40 ` H. Peter Anvin
2013-06-03 18:35 ` Martin K. Petersen
2013-06-03 18:38 ` H. Peter Anvin
2013-06-03 18:40 ` H. Peter Anvin
2013-06-03 22:20 ` H. Peter Anvin
2013-06-03 22:34 ` H. Peter Anvin
2013-06-04 15:56 ` Martin K. Petersen
2013-06-03 23:19 ` H. Peter Anvin
2013-06-04 15:39 ` Joe Lawrence
2013-06-04 15:46 ` H. Peter Anvin
2013-06-04 15:54 ` Martin K. Petersen
2013-06-05 10:02 ` Bernd Schubert
2013-06-05 11:38 ` Bernd Schubert
2013-06-05 12:53 ` [PATCH] scsi: Check if the device support WRITE_SAME_10 Bernd Schubert
2013-06-05 19:14 ` Martin K. Petersen
2013-06-05 20:09 ` Bernd Schubert
2013-06-07 2:15 ` Martin K. Petersen
2013-06-12 19:34 ` Bernd Schubert
2013-06-05 19:11 ` RAID-10 keeps aborting Martin K. Petersen
2013-06-04 17:36 ` Dan Williams
2013-06-04 17:54 ` Martin K. Petersen
2013-06-04 17:57 ` H. Peter Anvin
2013-06-04 18:04 ` Martin K. Petersen
2013-06-04 18:32 ` Dan Williams
2013-06-04 18:38 ` H. Peter Anvin
2013-06-04 18:56 ` Dan Williams
2013-06-05 2:39 ` H. Peter Anvin
[not found] ` <(H.>
[not found] ` <Peter>
[not found] ` <Anvin's>
[not found] ` <message>
[not found] ` <of>
[not found] ` <"Wed>
[not found] ` <"Thu>
[not found] ` <"Tue>
[not found] ` <04>
[not found] ` <Jun>
[not found] ` <2013>
[not found] ` <14:27:47>
[not found] ` <-0400")>
2013-06-07 2:19 ` Martin K. Petersen
2013-06-10 14:15 ` Joe Lawrence
2013-06-12 3:15 ` NeilBrown [this message]
2013-06-12 4:07 ` H. Peter Anvin
2013-06-12 6:29 ` Bernd Schubert
2013-06-12 10:22 ` Joe Lawrence
2013-06-12 14:28 ` Martin K. Petersen
2013-06-12 14:25 ` Martin K. Petersen
2013-06-12 14:29 ` H. Peter Anvin
2013-06-12 14:34 ` Martin K. Petersen
2013-06-12 14:37 ` H. Peter Anvin
2013-06-12 14:45 ` H. Peter Anvin
[not found] ` <5AA430FFE4486C448003201AC83BC85E0360CE3F@EXHQ.corp.stratus! .com>
[not found] ` <5AA430FFE4486C448003201AC83BC85E0360CE3F@EXHQ.corp.stratus.com>
2013-06-12 15:58 ` H. Peter Anvin
2013-06-13 3:10 ` NeilBrown
2013-06-13 3:13 ` H. Peter Anvin
2013-06-13 3:31 ` NeilBrown
2013-06-13 21:40 ` Martin K. Petersen
2013-06-13 2:45 ` Joe Lawrence
2013-06-13 3:11 ` NeilBrown
[not found] ` <19:39:58>
[not found] ` <-0700")>
2013-06-05 19:29 ` Martin K. Petersen
2013-06-06 18:27 ` Joe Lawrence
[not found] ` <(Joe>
2013-06-06 18:36 ` H. Peter Anvin
2013-06-12 14:43 ` Martin K. Petersen
2013-06-11 21:50 ` Joe Lawrence
2013-06-11 21:53 ` H. Peter Anvin
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=20130612131543.1c79e077@notabene.brown \
--to=neilb@suse.de \
--cc=dan.j.williams@gmail.com \
--cc=hpa@zytor.com \
--cc=joe.lawrence@stratus.com \
--cc=linux-raid@vger.kernel.org \
--cc=martin.petersen@oracle.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).