From: David Greaves <david@dgreaves.com>
To: linux-raid@vger.kernel.org
Subject: Re: Raid 5 questions
Date: Thu, 03 Jun 2004 16:50:49 +0100 [thread overview]
Message-ID: <40BF48D9.6020409@dgreaves.com> (raw)
In-Reply-To: <40BF35D7.9050902@dgreaves.com>
Answering my own post:
<snip>
> Rebuild Status : 0% complete
<snip>
Yeah, ok, I'm dim :)
Maybe the output could be a little more helpful? State = rebuilding?
and for anyone else, cat /proc/mdstat gave me the hint!!
Other things:
1)
in Manage mode it's documented to allow multiple commands and yet:
cu:~# mdadm /dev/md0 -f /dev/sdc1 -r /dev/sdc1
mdadm: set /dev/sdc1 faulty in /dev/md0
mdadm: hot remove failed for /dev/sdc1: Device or resource busy
cu:~# mdadm /dev/md0 -r /dev/sdc1
mdadm: hot removed /dev/sdc1
2)
To allow autodetection on startup you're supposed to set the partition
type to 0xfd
What if you're using whole disks? Are you supposed to create massive
partitions?
3)
I'm having some odd responses from the Monitor mode:
Here is the system:
cu:~# mdadm --detail /dev/md0
/dev/md0:
Version : 00.90.01
Creation Time : Thu Jun 3 17:03:11 2004
Raid Level : raid5
Array Size : 1975552 (1.88 GiB 2.02 GB)
Device Size : 987776 (964.63 MiB 1011.48 MB)
Raid Devices : 3
Total Devices : 4
Preferred Minor : 0
Persistence : Superblock is persistent
Update Time : Thu Jun 3 17:32:45 2004
State : clean, no-errors
Active Devices : 3
Working Devices : 4
Failed Devices : 0
Spare Devices : 1
Layout : left-symmetric
Chunk Size : 128K
Number Major Minor RaidDevice State
0 8 1 0 active sync /dev/sda1
1 8 17 1 active sync /dev/sdb1
2 8 33 2 active sync /dev/sdc1
3 8 2 -1 spare /dev/sda2
UUID : 9120f538:88dcabef:ba6f5f75:d2ce9e00
Events : 0.3904
I run the monitor using a PROGRAM to ensure I see all events (#'s below
are annotations :) )
cu:~# mdadm --monitor -d 1 -t /dev/md0
mdadm: Monitor using program "/bin/echo" from config file
TestMessage /dev/md0
# -f a device at this point
Fail /dev/md0
# Note that the device is not reported.
# A bit later (not long now I'm using 1Gb test partitions!)
SpareActive /dev/md0 /dev/sda2
# Note there were no RebuildStarted, RebuildNN, RebuildFinished events?
# -r the device - no events
# -a the device - no events
# mdadm --stop /dev/md0 here
DeviceDisappeared /dev/md0
Also stopping the monitor and degrading the array (-f a device) followed
by a monitor restart doesn't give a DegradedArray event.
David
next prev parent reply other threads:[~2004-06-03 15:50 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-06-03 14:29 Raid 5 questions David Greaves
2004-06-03 15:13 ` Guy
2004-06-03 15:50 ` David Greaves [this message]
2004-06-03 16:43 ` Guy
-- strict thread matches above, loose matches on Subject: below --
2004-08-01 1:57 RAID " Ninti Systems
2004-08-01 3:08 ` Daniel Pittman
2004-08-01 3:31 ` Jim Paris
2004-08-01 3:50 ` Alvin Oga
2004-08-02 6:01 ` Jarmo Järvenpää
2004-08-02 6:08 ` Luca Berra
2004-08-02 6:55 ` Jarmo Järvenpää
2004-08-02 6:09 ` Jim Paris
2004-08-02 7:27 ` Jarmo Järvenpää
2004-08-03 20:23 ` Frank van Maarseveen
2004-08-04 8:52 ` Tim Small
2004-08-01 9:33 ` Luca Berra
2004-08-01 10:24 ` Frank van Maarseveen
2004-08-03 5:19 ` misty-
2004-08-06 0:49 ` H. Peter Anvin
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=40BF48D9.6020409@dgreaves.com \
--to=david@dgreaves.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).