From: Tyler <pml@dtbb.net>
To: "David M. Strang" <dstrang@shellpower.net>
Cc: Neil Brown <neilb@cse.unsw.edu.au>, linux-raid@vger.kernel.org
Subject: Re: Raid5 Failure
Date: Sun, 17 Jul 2005 19:10:37 -0700 [thread overview]
Message-ID: <42DB0F9D.6040904@dtbb.net> (raw)
In-Reply-To: <004b01c58b3a$8e26f910$c200a8c0@NCNF5131FTH>
If you cat /proc/mdstat, it should show the array resyncing... when its
done, it will put the drive back as device 26.
Tyler.
David M. Strang wrote:
> Neil --
>
> That worked, the device has been added to the array. Now, I think the
> next problem is my own ignorance.
>
> -(root@abyss)-(/)- # mdadm --detail /dev/md0
> /dev/md0:
> Version : 01.00.01
> Creation Time : Wed Dec 31 19:00:00 1969
> Raid Level : raid5
> Array Size : 1935556992 (1845.89 GiB 1982.01 GB)
> Device Size : 71687296 (68.37 GiB 73.41 GB)
> Raid Devices : 28
> Total Devices : 28
> Preferred Minor : 0
> Persistence : Superblock is persistent
>
> Update Time : Sun Jul 17 17:32:12 2005
> State : clean, degraded
> Active Devices : 27
> Working Devices : 28
> Failed Devices : 0
> Spare Devices : 1
>
> Layout : left-asymmetric
> Chunk Size : 128K
>
> UUID : 4e2b6b0a8e:92e91c0c:018a4bf0:9bb74d
> Events : 176939
>
> Number Major Minor RaidDevice State
> 0 8 0 0 active sync /dev/evms/.nodes/sda
> 1 8 16 1 active sync /dev/evms/.nodes/sdb
> 2 8 32 2 active sync /dev/evms/.nodes/sdc
> 3 8 48 3 active sync /dev/evms/.nodes/sdd
> 4 8 64 4 active sync /dev/evms/.nodes/sde
> 5 8 80 5 active sync /dev/evms/.nodes/sdf
> 6 8 96 6 active sync /dev/evms/.nodes/sdg
> 7 8 112 7 active sync /dev/evms/.nodes/sdh
> 8 8 128 8 active sync /dev/evms/.nodes/sdi
> 9 8 144 9 active sync /dev/evms/.nodes/sdj
> 10 8 160 10 active sync /dev/evms/.nodes/sdk
> 11 8 176 11 active sync /dev/evms/.nodes/sdl
> 12 8 192 12 active sync /dev/evms/.nodes/sdm
> 13 8 208 13 active sync /dev/evms/.nodes/sdn
> 14 8 224 14 active sync /dev/evms/.nodes/sdo
> 15 8 240 15 active sync /dev/evms/.nodes/sdp
> 16 65 0 16 active sync /dev/evms/.nodes/sdq
> 17 65 16 17 active sync /dev/evms/.nodes/sdr
> 18 65 32 18 active sync /dev/evms/.nodes/sds
> 19 65 48 19 active sync /dev/evms/.nodes/sdt
> 20 65 64 20 active sync /dev/evms/.nodes/sdu
> 21 65 80 21 active sync /dev/evms/.nodes/sdv
> 22 65 96 22 active sync /dev/evms/.nodes/sdw
> 23 65 112 23 active sync /dev/evms/.nodes/sdx
> 24 65 128 24 active sync /dev/evms/.nodes/sdy
> 25 65 144 25 active sync /dev/evms/.nodes/sdz
> 26 0 0 - removed
> 27 65 176 27 active sync
> /dev/evms/.nodes/sdab
>
> 28 65 160 - spare /dev/evms/.nodes/sdaa
>
>
> I've got 28 devices, 1 spare, 27 active. I'm still running as clean,
> degraded.
>
> What do I do next? What I wanted to do was to put /dev/sdaa back in as
> device 26, but now it's device 28 - and flagged as spare. How do I
> make it active in the array again?
>
> -- David M. Strang
>
>
> ----- Original Message ----- From: Neil Brown
> To: David M. Strang
> Cc: linux-raid@vger.kernel.org
> Sent: Sunday, July 17, 2005 9:33 PM
> Subject: Re: Raid5 Failure
>
> Ahhhh... I cannot read my own code, that is the problem!!
>
> This patch should fix it.
>
> Thanks for persisting.
>
> NeilBrown
>
> Signed-off-by: Neil Brown <neilb@cse.unsw.edu.au>
>
> ### Diffstat output
> ./Manage.c | 7 ++-----
> 1 files changed, 2 insertions(+), 5 deletions(-)
>
> diff ./Manage.c~current~ ./Manage.c
> --- ./Manage.c~current~ 2005-07-07 09:19:53.000000000 +1000
> +++ ./Manage.c 2005-07-18 11:31:57.000000000 +1000
> @@ -204,11 +204,8 @@ int Manage_subdevs(char *devname, int fd
> return 1;
> }
> close(tfd);
> -#if 0
> - if (array.major_version == 0) {
> -#else
> - if (md_get_version(fd)%100 < 2) {
> -#endif
> + if (array.major_version == 0 &&
> + md_get_version(fd)%100 < 2) {
> if (ioctl(fd, HOT_ADD_DISK,
> (unsigned long)stb.st_rdev)==0) {
> fprintf(stderr, Name ": hot added %s\n",
> -
> -
> 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-07-18 2:10 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-07-17 15:44 Raid5 Failure David M. Strang
2005-07-17 22:05 ` Neil Brown
2005-07-17 23:15 ` David M. Strang
2005-07-18 0:05 ` Tyler
2005-07-18 0:23 ` David M. Strang
2005-07-18 0:06 ` Neil Brown
2005-07-18 0:52 ` David M. Strang
2005-07-18 1:06 ` Neil Brown
2005-07-18 1:26 ` David M. Strang
2005-07-18 1:31 ` David M. Strang
[not found] ` <001601c58b37$620c69d0$c200a8c0@NCNF5131FTH>
2005-07-18 1:33 ` Neil Brown
2005-07-18 1:46 ` David M. Strang
2005-07-18 2:10 ` Tyler [this message]
2005-07-18 2:12 ` David M. Strang
2005-07-18 2:15 ` Neil Brown
2005-07-18 2:24 ` David M. Strang
2005-07-18 2:09 ` bug report: mdadm-devel-2 , superblock version 1 Tyler
2005-07-18 2:19 ` Tyler
2005-07-25 0:37 ` Neil Brown
2005-07-25 0:36 ` Neil Brown
2005-07-25 3:47 ` Tyler
2005-07-27 2:08 ` Neil Brown
-- strict thread matches above, loose matches on Subject: below --
2005-07-15 0:39 Raid5 Failure David M. Strang
2005-07-15 1:43 ` Neil Brown
2005-07-15 2:16 ` David M. Strang
2005-07-15 20:25 ` David M. Strang
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=42DB0F9D.6040904@dtbb.net \
--to=pml@dtbb.net \
--cc=dstrang@shellpower.net \
--cc=linux-raid@vger.kernel.org \
--cc=neilb@cse.unsw.edu.au \
/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).