From: Robin Bowes <robin-lists@robinbowes.com>
To: Guy <bugzilla@watkins-home.com>
Cc: linux-raid@vger.kernel.org
Subject: Re: Stress testing system?
Date: Sat, 09 Oct 2004 18:19:18 +0100 [thread overview]
Message-ID: <41681D96.9020308@robinbowes.com> (raw)
In-Reply-To: <200410091658.i99GwJN22615@www.watkins-home.com>
Guy wrote:
> Once a drive fails, md will not re-sync it automatically. It will just sit
> there in a failed state. If you had a spare, then it would re-sync
> automatically. I am not 100% sure but I think...if you were to reboot,
> after the reboot md will resync.
>
> If you reboot before the re-sync is done, the re-sync will start over, at
> lease with my version.
I think that's what must have happened.
I replaced the power supply and brought the box back up. It then froze
on me, so I powered down again and investigated, bring the box up and
down a few times in the process. I then noticed the loose power
connection, fixed it, and brought the box back up. I reckon the array
must have been re-syncing from that point and it had nothing to do with
bonnie++.
Incidentally, I do have a spare drive:
[root@dude home]# mdadm --detail /dev/md5
/dev/md5:
Version : 00.90.01
Creation Time : Thu Jul 29 21:41:38 2004
Raid Level : raid5
Array Size : 974566400 (929.42 GiB 997.96 GB)
Device Size : 243641600 (232.35 GiB 249.49 GB)
Raid Devices : 5
Total Devices : 6
Preferred Minor : 5
Persistence : Superblock is persistent
Update Time : Sat Oct 9 18:18:54 2004
State : clean
Active Devices : 5
Working Devices : 6
Failed Devices : 0
Spare Devices : 1
Layout : left-symmetric
Chunk Size : 128K
UUID : a4bbcd09:5e178c5b:3bf8bd45:8c31d2a1
Events : 0.1410301
Number Major Minor RaidDevice State
0 8 2 0 active sync /dev/sda2
1 8 18 1 active sync /dev/sdb2
2 8 34 2 active sync /dev/sdc2
3 8 50 3 active sync /dev/sdd2
4 8 66 4 active sync /dev/sde2
5 8 82 - spare /dev/sdf2
Cheers,
R.
--
http://robinbowes.com
next prev parent reply other threads:[~2004-10-09 17:19 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-10-08 21:32 Stress testing system? Robin Bowes
2004-10-08 22:00 ` Mike Hardy
2004-10-08 22:07 ` Gordon Henderson
2004-10-08 23:49 ` Guy
2004-10-08 22:02 ` Gordon Henderson
2004-10-08 23:44 ` Robin Bowes
2004-10-08 23:48 ` Guy
2004-10-09 9:52 ` Robin Bowes
2004-10-09 16:58 ` Guy
2004-10-09 17:19 ` Robin Bowes [this message]
2004-10-10 20:36 ` Gordon Henderson
2004-10-10 21:35 ` Robin Bowes
2004-10-10 22:38 ` Guy
2004-10-11 8:38 ` Gordon Henderson
2004-10-11 9:01 ` Brad Campbell
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=41681D96.9020308@robinbowes.com \
--to=robin-lists@robinbowes.com \
--cc=bugzilla@watkins-home.com \
--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).