From: Sam Bingner <sam@bingner.com>
To: Veedar Hokstadt <veedar@gmail.com>,
"linux-raid@vger.kernel.org" <linux-raid@vger.kernel.org>
Subject: Re: Recovery possible after partial reshape failure?
Date: Sun, 14 Jul 2013 08:09:12 +0000 [thread overview]
Message-ID: <CE077E5D.139E8%sam@bingner.com> (raw)
In-Reply-To: <CANb3qHfPELcUdFeAOzRaZNE2d4ZAS=8ZHNc6he0qbcRAibpTNA@mail.gmail.com>
On 7/13/13 10:01 AM, "Veedar Hokstadt" <veedar@gmail.com> wrote:
>Hello, Please consider the following RAID5 recovery attempt after a
>failed partial reshape.
>Copy-on-write devices were created to protect original drives.
>Any assistance on how to reassemble would be most welcome.
>
>...Operating environment is from a systemrescuecd...
>% mdadm -V
>mdadm - v3.1.4 - 31st August 2010
>% /usr/local/sbin/mdadm -V <<<<<< compiled latest by hand
>mdadm - v3.2.6 - 25th October 2012
>% uname -a
>Linux dallas 3.2.33-std311-amd64 #2 SMP Wed Oct 31 07:31:30 UTC 2012
>x86_64 Intel(R) Core(TM) i7-2600K CPU @ 3.40GHz GenuineIntel GNU/Linux
>
>...Drive /dev/mapper/cow_sdc1 appears damaged and goes offline
>sporadically, so I'm trying to reassemble with out sdc1...
>...In any case sdc1 is out of sync with the other drives and it's
>reshape pos'n is at zero...
>...Also /usb/foo is an empty file...
sdc and sdf's event counts are both 2 events higher than the other
devicesŠ I suspect this is causing issues because sdf's event count and
update time is higher than the other good devices, but I'm not sure how to
correct it. I wanted to see if you can verify that the original sdf also
has this problem (updated later than all the other devices with an
incremented event count)
I'm sure somebody with more knowledge than I will be able to give you more
information.
Sam
--
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:[~2013-07-14 8:09 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-07-13 20:01 Recovery possible after partial reshape failure? Veedar Hokstadt
2013-07-14 8:09 ` Sam Bingner [this message]
2013-07-15 22:08 ` Veedar Hokstadt
2013-07-16 1:35 ` NeilBrown
2013-07-30 1:45 ` Veedar Hokstadt
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=CE077E5D.139E8%sam@bingner.com \
--to=sam@bingner.com \
--cc=linux-raid@vger.kernel.org \
--cc=veedar@gmail.com \
/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.