From: NeilBrown <nfbrown@novell.com>
To: Benjamin Meier <maillists@ferienwohnung-altenbeken.de>,
linux-raid@vger.kernel.org
Subject: Re: Recovery after failed chunk size change
Date: Fri, 01 Apr 2016 16:25:24 +1100 [thread overview]
Message-ID: <87a8ldrjcr.fsf@notabene.neil.brown.name> (raw)
In-Reply-To: <56FD7B92.1030102@ferienwohnung-altenbeken.de>
[-- Attachment #1: Type: text/plain, Size: 2869 bytes --]
On Fri, Apr 01 2016, Benjamin Meier wrote:
> Hi there,
>
> I tried to do a chunk size change from 4096k to 64k on a 7-disk RAID6
> array. I am using Debian Jessie with kernel 3.16 and mdadm 3.3.2. After
> I initiated the change the process staled immediately. I could watch it
> in /proc/mdadm that there has not been any progress at all. The
> backup-file hasn't been touched for days now.
>
> So I decided to backup all data from that device in case it isn't
> starting at next reboot. Accidentally the system was restarted before
> the backup was finished. And now the array is not assembling any more,
> even with the correct --backup-file. I get "mdadm: Failed to restore
> critical section for reshape, sorry.".
>
> So the first question is: How can I access the data again? I think there
> is no damage at this time- I appended an output from --examine at the
> end of this message. All seven drives giving me the same output in all
> relevant topics. Especially "Chunk Size", "New Chunksize" and "Reshape
> pos'n" is all the same.
> What is the best way now that I do not damage any data?
mdadm --assemble --force --update=revert-reshape --invalid-backup
--backup-file=/whatever /dev/md/TA /dev/list-of-devices
using mdadm 3.4.
>
> Second question: Is the problem with the level change a known bug?
Yes, this has been happening to a few people. The shape doesn't really
start properly.
If someone can provide a recipe for how to reproduce the problem
(e.g. using loop-back devices) I'll happily look into fixing it, or
identifying which kernel it is already fixed in.
Neilbrown
>
> Thanks for reading!
>
> --
> /dev/disk/by-partlabel/hyper_TA_1:
> Magic : a92b4efc
> Version : 1.2
> Feature Map : 0x5
> Name : hyper:TA (local to host hyper)
> Raid Level : raid6
> Raid Devices : 7
>
> Avail Dev Size : 3434725376 (1637.80 GiB 1758.58 GB)
> Array Size : 8586813440 (8189.02 GiB 8792.90 GB)
> Data Offset : 147456 sectors
> Super Offset : 8 sectors
> Unused Space : before=147368 sectors, after=0 sectors
> State : clean
>
> Internal Bitmap : 8 sectors from superblock
> Reshape pos'n : 0
> New Chunksize : 64K
>
> Update Time : Thu Mar 31 17:57:01 2016
> Bad Block Log : 512 entries available at offset 72 sectors
> Checksum : e7172c1f - correct
> Events : 527046
>
> Layout : left-symmetric
> Chunk Size : 4096K
>
> Device Role : Active device 5
> Array State : AAAAAAA ('A' == active, '.' == missing, 'R' == replacing)
>
> --
> 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
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 818 bytes --]
next prev parent reply other threads:[~2016-04-01 5:25 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-31 19:33 Recovery after failed chunk size change Benjamin Meier
2016-04-01 5:25 ` NeilBrown [this message]
2016-04-01 20:03 ` Benjamin Meier
2016-04-11 15:29 ` Benjamin Meier
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=87a8ldrjcr.fsf@notabene.neil.brown.name \
--to=nfbrown@novell.com \
--cc=linux-raid@vger.kernel.org \
--cc=maillists@ferienwohnung-altenbeken.de \
/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