From: "Jakob Østergaard" <jakob@unthought.net>
To: "Potthoff, Kay" <Kay.Potthoff@force.de>
Cc: "Linux RAID Mailing List (E-mail)" <linux-raid@vger.kernel.org>
Subject: Re: Q: Priority of md_thread()
Date: Wed, 22 May 2002 22:45:03 +0200 [thread overview]
Message-ID: <20020522224503.E586@unthought.net> (raw)
In-Reply-To: <9CFB9DA5261CD611A29B00508B789048654302@ex-deu-munich02.force.de>; from Kay.Potthoff@force.de on Wed, May 22, 2002 at 01:59:57PM +0200
On Wed, May 22, 2002 at 01:59:57PM +0200, Potthoff, Kay wrote:
> I have a question regarding the priority of the md_thread() function
> (defined in md.c).
>
> I have seen that the priority of this thread is set to -20 (parameter
> current->nice), which means that this thread takes the highest priority. The
> problem I have is that this thread blocks some other task that is answering
> keep alive network pings from another (sibling) node. Because the keep alive
> answers are blocked the other node decides to take-over the RAID. This
> situation leeds to the fact that two nodes try to start the RAID. MD don't
> like this. The RAID is considered to be faulty and both nodes try to repair
> it, that is a problem.
That system cannot be stable.
Remember the -20 is only for the CPU scheduler, and the md_thread is not CPU
bound (unless you have ISA controllers, or *very* special disks). What I am
trying to say is, I doubt much would change if the nice level was changed to
20 instead...
I think your problem is that something (and probably as you state, md_thread)
is causing fluctuations in the ping replies, causing your other nodes to take
an action which they shouldn't take based on a ping fluctuation (that could
just as easily be caused by a packet loss or some other random event in the
whole computer-network-computer system).
If you want multiple nodes mounting the same array, you need some consistency
protocol to be able to *guarantee* that no two nodes will try to master the
same array simultaneously. Ping fluctuations do not constitute a consistency
protocol.
> I figuered out that the cause of this problem is the high priority of the
> md_thread() function. I feel tempted to decrease this priority, but I feel
> some upcoming ache in my belly because I don't know the exact reason why the
> priority had been set to -20. I hope that somebody can explain me why! The
> comments in the sources seem to regard to RAID-5 personality. If so that
> would be no problem, I intend only to use RAID-1.
Please let me know if I completely misunderstood the situation :)
--
................................................................
: jakob@unthought.net : And I see the elder races, :
:.........................: putrid forms of man :
: Jakob Østergaard : See him rise and claim the earth, :
: OZ9ABN : his downfall is at hand. :
:.........................:............{Konkhra}...............:
-
To unsubscribe from this list: send the line "unsubscribe linux-raid" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2002-05-22 20:45 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-05-22 11:59 Q: Priority of md_thread() Potthoff, Kay
2002-05-22 20:45 ` Jakob Østergaard [this message]
-- strict thread matches above, loose matches on Subject: below --
2002-05-23 8:31 Potthoff, Kay
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=20020522224503.E586@unthought.net \
--to=jakob@unthought.net \
--cc=Kay.Potthoff@force.de \
--cc=linux-raid@vger.kernel.org \
/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.