From: Bill Davidsen <davidsen@tmr.com>
To: Rainer Fuegenstein <rfu@kaneda.iguw.tuwien.ac.at>
Cc: linux-raid@vger.kernel.org
Subject: Re: resync duration ?
Date: Mon, 18 May 2009 11:02:41 -0400 [thread overview]
Message-ID: <4A117891.1000909@tmr.com> (raw)
In-Reply-To: <1308264373.20090514150647@kaneda.iguw.tuwien.ac.at>
Rainer Fuegenstein wrote:
> Hi guys,
>
> I'm a but confused about the duration of a raid5 resync:
>
> - occasionally, my server with 4*750 gb sata raid5 crashed (because of
> problems with the power supply); after rebooting it took about 10 to 12
> hours to resync the raid5 (guess it just re-created some parity
> information or however it works internally, but didn't have to copy
> any data)
>
>
I have a test machine which crashes regularly (used for kernel and
hardware tests), and that sounds long. Are you running without a bitmap,
by any chance?
> - right now I replaced one 750GB disk with a 1.5TB disk, but now
> resyncing (according to /proc/mdstat) it is supposed to take only 160
> minutes ?! although it needs top copy data to a blank disk ?
>
> is this normal or should I be worried, especially before I pull out
> the next 750GB disk and replace it with the next 1.5TB disk ?
>
> tnx in advance.
>
> --
> 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
>
>
--
bill davidsen <davidsen@tmr.com>
CTO TMR Associates, Inc
"You are disgraced professional losers. And by the way, give us our money back."
- Representative Earl Pomeroy, Democrat of North Dakota
on the A.I.G. executives who were paid bonuses after a federal bailout.
prev parent reply other threads:[~2009-05-18 15:02 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-05-14 13:06 resync duration ? Rainer Fuegenstein
2009-05-14 13:58 ` Bryan Mesich
2009-05-14 16:26 ` Ryan Wagoner
2009-05-14 17:03 ` Re[2]: " Rainer Fuegenstein
2009-05-14 17:06 ` John Robinson
2009-05-14 18:07 ` Bryan Mesich
2009-05-14 19:38 ` Richard Scobie
2009-05-15 1:22 ` Neil Brown
2009-05-15 4:04 ` Leslie Rhorer
2009-05-15 4:44 ` NeilBrown
2009-05-15 5:07 ` Leslie Rhorer
2009-05-15 20:21 ` Richard Scobie
2009-05-15 21:51 ` Neil Brown
2009-05-16 2:47 ` Richard Scobie
2009-05-16 8:10 ` NeilBrown
2009-05-18 15:00 ` Bill Davidsen
2009-05-28 16:43 ` John Robinson
2009-05-15 11:16 ` Rainer Fuegenstein
2009-05-18 15:02 ` Bill Davidsen [this message]
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=4A117891.1000909@tmr.com \
--to=davidsen@tmr.com \
--cc=linux-raid@vger.kernel.org \
--cc=rfu@kaneda.iguw.tuwien.ac.at \
/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).