From: Brett King <king.br@gmail.com>
To: linux-raid@vger.kernel.org
Subject: Re: compute_blocknr: map not correct error during RAID6 reshape 6 -> 7 disks, mdadm 3.1.2 / kernel 2.6.34-rc3
Date: Tue, 20 Apr 2010 13:43:08 +1000 [thread overview]
Message-ID: <z2q8cf253381004192043haf99536cvfb2bf6fcfb40fa4d@mail.gmail.com> (raw)
In-Reply-To: <u2j8cf253381004151856l76b4e227mc6327534e0e304ad@mail.gmail.com>
Hello,
It's been quiet on this issue to date and I assume everyone's working
on important fixes and features etc - my apologies for the annoyance
however at this point I'm looking for some collective guidance on my
next move as I can't leave things in this state.
To summarize, I am attempting to grow a RAID6 array from 6 to 7x 2TB
disks however the reshape is stalling at 87.9% and throwing
'compute_blocknr: map not correct' errors. The system still responds
but needs a hard reset to do anything MD related.
I've tried varying kernel and mdadm versions all with the same result:
2.6.31, 2.6.33, 2.6.34-rc3 & rc4, each with mdadm 2.6.8, 3.0.2 &
3.1.2.
The only kernel source file containing this string is
drivers/md/raid5.c so I'm in the right place.
So I am asking you fellow linux-raid'ers, what can be done in this
situation ? I've filed a bug on bugzilla and now would only like to
know if this issue has been experienced by others, if perhaps a fix is
in the pipeline and any tips, tricks etc that may get the reshape
completed then the data accessible again.
I can see the only other non-destructuve option right now is to pull
out the disks, restore from backup onto a new array & wait for a
future kernel / mdadm version which will allow completion of the
reshape.
Cheers,
Brett.
next prev parent reply other threads:[~2010-04-20 3:43 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-04-16 1:56 compute_blocknr: map not correct error during RAID6 reshape 6 -> 7 disks, mdadm 3.1.2 / kernel 2.6.34-rc3 Brett King
2010-04-20 3:43 ` Brett King [this message]
2010-04-20 4:14 ` Neil Brown
2010-04-22 3:43 ` Brett King
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=z2q8cf253381004192043haf99536cvfb2bf6fcfb40fa4d@mail.gmail.com \
--to=king.br@gmail.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).