From: Brassow Jonathan <jbrassow@redhat.com>
To: NeilBrown <neilb@suse.de>
Cc: "linux-raid@vger.kernel.org Raid" <linux-raid@vger.kernel.org>,
Jonathan Brassow <jbrassow@redhat.com>
Subject: Re: [PATCH] MD: Quickly return errors if too many devices have failed.
Date: Mon, 18 Mar 2013 11:15:58 -0500 [thread overview]
Message-ID: <31E9173C-B95C-4D4A-BF91-2D5CE93828A5@redhat.com> (raw)
In-Reply-To: <20130318104905.4a70bc00@notabene.brown>
On Mar 17, 2013, at 6:49 PM, NeilBrown wrote:
>>
>>
>> I would prefer to get immediate errors if nothing can be done to satisfy the
>> request and I've been thinking of something like the attached patch. The
>> patch below is incomplete. It does not take into account any reshaping that
>> is going on, nor does it try to figure out if a mirror set in RAID10 has died;
>> but I hope it gets the basic idea across.
>>
>> Is this a good way to handle this situation, or am I missing something?
>
> I think we do get immediate errors (once all bugs are fixed).
> Your patch does extra work for every request which is only of value if the
> array has failed - and it really doesn't make sense to optimise for a failed
> array.
> The current approach is to just try to satisfy a request and once we find
> that we need to do something that is impossible - return an error at that
> point. I think that is best.
>
> Can you try the commit I identified and see if it makes the problem go away?
Yes, that sounds better. I will try with the commit you mentioned.
thanks,
brassow
next prev parent reply other threads:[~2013-03-18 16:15 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-13 17:29 [PATCH] MD: Quickly return errors if too many devices have failed Jonathan Brassow
2013-03-17 23:49 ` NeilBrown
2013-03-18 16:15 ` Brassow Jonathan [this message]
2013-03-18 17:31 ` Roy Sigurd Karlsbakk
2013-03-19 19:14 ` Brassow Jonathan
2013-03-19 21:15 ` Brassow Jonathan
2013-03-20 2:46 ` NeilBrown
2013-03-20 20:56 ` Brassow Jonathan
2013-03-20 23:04 ` NeilBrown
2013-03-21 13:58 ` Brassow Jonathan
2013-03-28 0:13 ` NeilBrown
2013-04-19 13:22 ` Brassow Jonathan
2013-03-21 14:01 ` Brassow Jonathan
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=31E9173C-B95C-4D4A-BF91-2D5CE93828A5@redhat.com \
--to=jbrassow@redhat.com \
--cc=linux-raid@vger.kernel.org \
--cc=neilb@suse.de \
/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).