From: Tyler <pml@dtbb.net>
To: linux-raid@vger.kernel.org
Subject: raid sync looping filling log files
Date: Wed, 27 Apr 2005 04:14:47 -0700 [thread overview]
Message-ID: <426F7427.3070504@dtbb.net> (raw)
The other day i ran across a problem trying to rebuild a raid using a
spare, but didn't seem to be getting anywhere. Below is what is in the
log files, over and over and over, eventually filling up the small 2gb
root partition with log files (six hundred plus megabytes worth).
Thankfully this was just a new raid, and didn't have any data on it yet,
and i found the easiest way to fix it, was to stop the array, and
re-create it. Currently its syncing, and I will write the list again if
it happens again.. but I am curious if this is a known problem, and what
might have caused it, as I have other raid5's that i hope don't have the
same problem one day.
.<6>md: syncing RAID array md0
md: minimum _guaranteed_ reconstruction speed: 1000 KB/sec/disc.
md: using maximum available idle IO bandwith (but not more than 200000
KB/sec) for reconstruction.
md: using 128k window, over a total of 195360896 blocks.
md: md0: sync done.
over and over and over, the above message hits the logs several times
per second.
Regards,
Tyler.
reply other threads:[~2005-04-27 11:14 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=426F7427.3070504@dtbb.net \
--to=pml@dtbb.net \
--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).