From: NeilBrown <neilb@suse.de>
To: Iruwen <iruwen@gmx.net>
Cc: linux-raid@vger.kernel.org
Subject: Re: Disk with backup-file died during reshape
Date: Tue, 27 Aug 2013 10:48:27 +1000 [thread overview]
Message-ID: <20130827104827.60262d5a@notabene.brown> (raw)
In-Reply-To: <521B3E43.5050707@gmx.net>
[-- Attachment #1: Type: text/plain, Size: 2510 bytes --]
On Mon, 26 Aug 2013 13:38:43 +0200 Iruwen <iruwen@gmx.net> wrote:
> Hi,
>
> the disk holding backup-file unfortunately died during an mdadm --grow
> /dev/md0 --level=6 --raid-devices=4 --backup-file=/mnt/backup/md0.bak.
> The speed of the reshape dropped to 0K/sec, apart from that the RAID
> seems fine.
>
>
> Personalities : [raid6] [raid5] [raid4]
> md0 : active raid6 sda1[4] sdc1[2] sdd1[3] sdb1[1]
> 2930271232 blocks super 1.2 level 6, 512k chunk, algorithm 18
> [4/3] [UUU_]
> [==========>..........] reshape = 53.6% (786497536/1465135616)
> finish=55405950.5min speed=0K/sec
>
> unused devices: <none>
>
>
> /dev/md0:
> Version : 1.2
> Creation Time : Fri Feb 11 21:10:18 2011
> Raid Level : raid6
> Array Size : 2930271232 (2794.52 GiB 3000.60 GB)
> Used Dev Size : 1465135616 (1397.26 GiB 1500.30 GB)
> Raid Devices : 4
> Total Devices : 4
> Persistence : Superblock is persistent
>
> Update Time : Mon Aug 26 13:32:09 2013
> State : clean, degraded, recovering
> Active Devices : 3
> Working Devices : 4
> Failed Devices : 0
> Spare Devices : 1
>
> Layout : left-symmetric-6
> Chunk Size : 512K
>
> Reshape Status : 53% complete
> New Layout : left-symmetric
>
> Name : backup:0 (local to host backup)
> UUID : 832a100a:2996471b:51867bfa:aaf5c38f
> Events : 1053146
>
> Number Major Minor RaidDevice State
> 3 8 49 0 active sync /dev/sdd1
> 1 8 17 1 active sync /dev/sdb1
> 2 8 33 2 active sync /dev/sdc1
> 4 8 1 3 spare rebuilding /dev/sda1
>
>
> What's the right thing to do now, is this recoverable? I have backups of
> course and since the RAID is still working I could just copy everything
> off and recreate it, but I'd rather fix this the "right way" than to set
> up a new system.
You should be able to simply stop the array and re-assemble with a different
backup file and the magic flag "--invalid-backup" (required mdadm 3.2 or
later).
The backup-file is only really needed in case of a crash. As you will stop
the array cleanly there will be no need to recover anything when you
re-assemble, so --invalid-backup (Which say "there is nothing in the backup
file, but that is OK) is perfectly safe.
NeilBrown
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 828 bytes --]
prev parent reply other threads:[~2013-08-27 0:48 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-08-26 11:38 Disk with backup-file died during reshape Iruwen
2013-08-27 0:48 ` NeilBrown [this message]
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=20130827104827.60262d5a@notabene.brown \
--to=neilb@suse.de \
--cc=iruwen@gmx.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 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).