From: "JaniD++" <djani22@dynamicweb.hu>
To: Marc <linux-raid@liquid-nexus.net>
Cc: linux-raid@vger.kernel.org
Subject: Re: where is the spare drive? :-)
Date: Thu, 5 Jan 2006 12:06:25 +0100 [thread overview]
Message-ID: <007f01c611e8$135573d0$a400a8c0@dcccs> (raw)
In-Reply-To: 20060105061133.M54165@liquid-nexus.net
----- Original Message -----
From: "Marc" <linux-raid@liquid-nexus.net>
To: "JaniD++" <djani22@dynamicweb.hu>; <linux-raid@vger.kernel.org>
Sent: Thursday, January 05, 2006 7:16 AM
Subject: Re: where is the spare drive? :-)
> On Mon, 2 Jan 2006 00:26:58 +0100, JaniD++ wrote
> > Hello, list,
> >
> > I found something interesting when i try to create a brand new array
> > on brand new drives....
> >
>
> <snip>
>
> > 5. The question
> >
> > Why shows sdh2 as spare?
> > The MD array size is correct.
> > And i really can see, the all drive is reading, and sdh2 is *ONLY*
writing.
> >
>
> I'm not 100% sure but from a post by Neil a while a go on the list, the
spare
> device is a temporary construct created during the resync operation. Once
the
> resync is complete it should disappear.
>
> You could try searching the list archives for the post - choice of
keywords is
> up to you ;)
Thanks, but i have found the bug already. ;-)
If i create new raid5, it should only parity resyncing, and not spare
rebuilding!
This happens, only if i use mdadm.
With raidtools works fine.
My problem is now the bitmap. :(
Only mdadm supports this....
Cheers,
Janos
>
> Regards,
> Marc
>
> -
> 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:[~2006-01-05 11:06 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-01-01 23:26 where is the spare drive? :-) JaniD++
2006-01-05 6:16 ` Marc
2006-01-05 11:06 ` JaniD++ [this message]
2006-01-12 3:07 ` Neil Brown
2006-01-12 9:11 ` JaniD++
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='007f01c611e8$135573d0$a400a8c0@dcccs' \
--to=djani22@dynamicweb.hu \
--cc=linux-raid@liquid-nexus.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.