From: "Lars Täuber" <taeuber@bbaw.de>
To: linux-raid@vger.kernel.org
Subject: mark spare as active sync device?
Date: Wed, 15 Jun 2011 12:10:26 +0200 [thread overview]
Message-ID: <20110615121026.f689e4b2.taeuber@bbaw.de> (raw)
Hi there,
is it possible to mark a nearly completly synced device as active in sync?
There was failing a device shortly before a spare drive was completely
synced. I want to get the directory structure from the device.
md3 : active raid6 sdz[16] sdaf[13] sds[0] sdac[10] sdah[15] sdag[14] sdae[12] sdad [11](F) sdab[9] sdaa[17](F) sdy[6] sdx[5] sdw[4] sdv[3] sdu[2] sdt[1]
27349202944 blocks level 6, 64k chunk, algorithm 2 [16/13] [UUUUUUU__UU_UUUU]
[===================>.] recovery = 98.3% (1921986020/1953514496) finish=25.9min speed=20244K/sec
/dev/sdz was the device that was inserted and is now marked as spare. Is it possible to mark sdz as active and in sync?
Is there any chance to get data from this array?
Thanks
Lars
next reply other threads:[~2011-06-15 10:10 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-06-15 10:10 Lars Täuber [this message]
2011-06-16 0:54 ` mark spare as active sync device? NeilBrown
2011-06-16 9:29 ` Lars Täuber
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=20110615121026.f689e4b2.taeuber@bbaw.de \
--to=taeuber@bbaw.de \
--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).