From: Mike Hardy <mhardy@h3c.com>
To: danci@agenda.si
Cc: linux-raid@vger.kernel.org
Subject: Re: Is there any way to delay reconstruction
Date: Wed, 25 May 2005 08:12:09 -0700 [thread overview]
Message-ID: <429495C9.3090208@h3c.com> (raw)
In-Reply-To: <Pine.LNX.4.61.0505251019280.16854@desktop.agenda.si>
I've had this problem. I turned the raid speed limit max to 0, slept for
a second (just because), did my hdparm commands, slept another second
(again, just because - may not be necessary), then turned the raid speed
limit back to something that was good for background reconstruction.
That got rid of my dropped interrupts
-Mike
danci@agenda.si wrote:
> On Wed, 25 May 2005, Catalin(ux aka Dino) BOIE wrote:
>
>
>>>So I need to know if there is any way (kernel parameter would be
>>>ideal) to delay reconstruction for X seconds/minutes?
>>>
>>>Any other suggestions to deal with the problem?
>>
>>You can hot-remove the previous failed disk (anyway, it just started to
>>resync). Then, activate DMA, then hot-add the disk to array.
>>
>>Hope it helps.
>
>
> Thanks for the suggestion - this may be the last resort (I'd like to keep
> the init-scripts as clean as possible).
>
> I forgot to mention that I'm using 2.4 kernels (2.4.27 at the moment,
> 2.4.30 on the test machine - but it does the same thing).
>
> There is a module 'piix.o' that needs to be loaded before I can use DMA at
> all. It's loaded via init scripts - I will try putting it in the initrd.
>
> D.
>
> -
> 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:[~2005-05-25 15:12 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-05-25 6:16 Is there any way to delay reconstruction danci
2005-05-25 6:26 ` Catalin(ux aka Dino) BOIE
2005-05-25 8:25 ` danci
2005-05-25 15:12 ` Mike Hardy [this message]
2005-05-26 6:48 ` danci
2005-05-25 15:09 ` Tim Moore
2005-05-26 6:41 ` danci
2005-05-25 15:25 ` Derek Piper
2005-05-25 16:58 ` Mike Hardy
2005-05-26 6:59 ` danci
2005-05-26 16:07 ` Mike Hardy
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=429495C9.3090208@h3c.com \
--to=mhardy@h3c.com \
--cc=danci@agenda.si \
--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 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).