Hi,
I had a power failure during a RAID5 reshape.
I added two drives to an existing RAID5 of three drives.
After the machine came back up (on a rescue disk) I thought I'd simply have to
go through the process again. So I use add add the new disk again.
Although that worked, I am now unable to
Hi,
During the process of reshaping a Raid5 from 3 (/dev/sd[a-c]) to 5
devices (/dev/sd[a-e]) the system was accidentally shut down.
I know I was stupid I should have used a --backup-file but stupid me didn't.
Thanks for not rubbing it any further. :(
Ok, here is what I have:
nas:~# uname -a
to find out where
Grow_restart() stumbles. By looking at it I'm not even sure it's able
to resume and not just restart. :-/
- Message from [EMAIL PROTECTED] -
Date: Tue, 09 Oct 2007 20:58:47 +0200
From: Nagilum [EMAIL PROTECTED]
Reply-To: Nagilum [EMAIL PROTECTED]
Subject
- Message from [EMAIL PROTECTED] -
Date: Fri, 12 Oct 2007 09:51:08 +1000
From: Neil Brown [EMAIL PROTECTED]
Reply-To: Neil Brown [EMAIL PROTECTED]
Subject: Re: Help RAID5 reshape Oops / backup-file
To: Nagilum [EMAIL PROTECTED]
Cc: linux-raid@vger.kernel.org
You may be able to temporary revive one of your dead disks by putting
them in a fridge (properly wrapped and protected against condensation
water!!, search the net on how to do that).
Then you can mark them as bad and linux will sync to a spare.
As for your sdc, I'd test it outside of the
Oct 2007 08:43:28 +0200
From: Nagilum [EMAIL PROTECTED]
Reply-To: Nagilum [EMAIL PROTECTED]
Subject: Re: Help RAID5 reshape Oops / backup-file
To: Neil Brown [EMAIL PROTECTED]
Cc: linux-raid@vger.kernel.org
- Message from [EMAIL PROTECTED] -
Date: Fri, 12 Oct 2007
- Message from [EMAIL PROTECTED] -
Date: Mon, 15 Oct 2007 09:31:23 +1000
From: Neil Brown [EMAIL PROTECTED]
Reply-To: Neil Brown [EMAIL PROTECTED]
Subject: Re: Help RAID5 reshape Oops / backup-file
To: Nagilum [EMAIL PROTECTED]
Cc: linux-raid@vger.kernel.org
- Message from [EMAIL PROTECTED] -
Date: Mon, 15 Oct 2007 13:55:22 +0200
From: Nagilum [EMAIL PROTECTED]
Reply-To: Nagilum [EMAIL PROTECTED]
Subject: Re: Help RAID5 reshape Oops / backup-file
To: Neil Brown [EMAIL PROTECTED]
Cc: linux-raid@vger.kernel.org
- Message from [EMAIL PROTECTED] -
Date: Tue, 16 Oct 2007 14:50:09 +0200
From: Nagilum [EMAIL PROTECTED]
Reply-To: Nagilum [EMAIL PROTECTED]
Subject: Re: Help RAID5 reshape Oops / backup-file
To: Neil Brown [EMAIL PROTECTED]
Cc: linux-raid@vger.kernel.org
- Message from [EMAIL PROTECTED] -
Date: Mon, 22 Oct 2007 21:46:08 +1000
From: Sam Redfern [EMAIL PROTECTED]
Reply-To: Sam Redfern [EMAIL PROTECTED]
Subject: Fwd: issues rebuilding raid array.
To: linux-raid@vger.kernel.org
The array was build using 2.6.18-7 Now i'm
Hi,
I'm running 2.6.23.8 x86_64 using mdadm v2.6.4.
I was adding a disk (/dev/sdf) to an existing raid5 (/dev/sd[a-e] - md0)
During that reshape (at around 4%) /dev/sdd reported read errors and
went offline.
I replaced /dev/sdd with a new drive and tried to reassemble the array
(/dev/sdd was
- Message from [EMAIL PROTECTED] -
Date: Sat, 24 Nov 2007 12:02:09 +0100
From: Nagilum [EMAIL PROTECTED]
Reply-To: Nagilum [EMAIL PROTECTED]
Subject: raid5 reshape/resync
To: linux-raid@vger.kernel.org
Hi,
I'm running 2.6.23.8 x86_64 using mdadm v2.6.4.
I was adding
- Message from [EMAIL PROTECTED] -
Date: Thu, 29 Nov 2007 16:48:47 +1100
From: Neil Brown [EMAIL PROTECTED]
Reply-To: Neil Brown [EMAIL PROTECTED]
Subject: Re: raid5 reshape/resync
To: Nagilum [EMAIL PROTECTED]
Cc: linux-raid@vger.kernel.org
Hi,
I'm running
- Message from [EMAIL PROTECTED] -
Date: Sat, 01 Dec 2007 15:48:17 +0100
From: Nagilum [EMAIL PROTECTED]
Reply-To: Nagilum [EMAIL PROTECTED]
Subject: Re: raid5 reshape/resync
To: Neil Brown [EMAIL PROTECTED]
Cc: linux-raid@vger.kernel.org
I'm not sure how
- Message from [EMAIL PROTECTED] -
Date: Sun, 16 Dec 2007 14:16:45 +0100
From: Janek Kozicki [EMAIL PROTECTED]
Reply-To: Janek Kozicki [EMAIL PROTECTED]
Subject: Re: raid5 reshape/resync
To: Nagilum [EMAIL PROTECTED]
Cc: linux-raid@vger.kernel.org
Nagilum said
- Message from [EMAIL PROTECTED] -
- Message from [EMAIL PROTECTED] -
Nagilum said: (by the date of Tue, 18 Dec 2007 11:09:38 +0100)
Ok, I've recreated the problem in form of a semiautomatic testcase.
All necessary files (plus the old xfs_repair output
- Message from [EMAIL PROTECTED] -
Date: Wed, 26 Dec 2007 21:22:42 -0800
From: Cody Yellan [EMAIL PROTECTED]
I had a 4x500GB SATA2 array, md0. I added one 500GB drive and
reshaping began at ~2500K/sec. Changing
/proc/sys/dev/raid/speed_limit_m{in,ax} or
Ok, since my previous thread didn't seem to attract much attention,
let me try again.
An interrupted RAID5 reshape will cause the md device in question to
contain one corrupt chunk per stripe if resumed in the wrong manner.
A testcase can be found at http://www.nagilum.de/md/ .
The first testcase
- Message from [EMAIL PROTECTED] -
Date: Mon, 31 Dec 2007 12:02:14 -0500 (EST)
From: Justin Piszcz [EMAIL PROTECTED]
Reply-To: Justin Piszcz [EMAIL PROTECTED]
Subject: Re: Change Stripe size?
To: Greg Cormier [EMAIL PROTECTED]
Cc: linux-raid@vger.kernel.org
- Message from [EMAIL PROTECTED] -
Date: Sat, 05 Jan 2008 11:05:00 -0500
From: Jim [EMAIL PROTECTED]
Reply-To: [EMAIL PROTECTED]
Subject: Raid 1, can't get the second disk added back in.
To: linux-raid@vger.kernel.org
Sometime in the distant past, I lost a member of
- Message from [EMAIL PROTECTED] -
Date: Fri, 4 Jan 2008 09:37:24 +1100
From: Neil Brown [EMAIL PROTECTED]
Reply-To: Neil Brown [EMAIL PROTECTED]
Subject: Re: PROBLEM: RAID5 reshape data corruption
To: Nagilum [EMAIL PROTECTED]
Cc: linux-raid@vger.kernel.org
- Message from [EMAIL PROTECTED] -
Date: Sat, 5 Jan 2008 18:11:38 -0800 (PST)
From: Hxsrmeng [EMAIL PROTECTED]
I hope the mdadm monitor function can pass all three command-line
arguments to my-script, including the name of the event, the name of the
md device and the name of
- Message from [EMAIL PROTECTED] -
Date: Sun, 06 Jan 2008 06:13:06 -0500
From: Jim [EMAIL PROTECTED]
[EMAIL PROTECTED]:~# mdadm /dev/md0 --re-add /dev/hdb5
mdadm: Cannot open /dev/hdb5: Device or resource busy
Have you tried stopping (-S) /dev/md0 and then re-assemble the
- Message from [EMAIL PROTECTED] -
Date: Sun, 06 Jan 2008 00:31:46 +0100
From: Nagilum [EMAIL PROTECTED]
At the moment I'm thinking about writing a small perl program that
will generate me a shell script or makefile containing dd commands
that will copy the chunks from
- Message from [EMAIL PROTECTED] -
Date: Wed, 23 Jan 2008 16:05:40 +1100
From: Michael Harris [EMAIL PROTECTED]
Reply-To: Michael Harris [EMAIL PROTECTED]
Subject: identifying failed disk/s in an array.
To: linux-raid@vger.kernel.org
Hi,
I have just built a Raid 5
Hi,
After having been through a few ups and downs with md and mdadm I
think it would be a good idea if mdadm had a safe mode for growing
raid5.
Safe mode would entail several things:
1. It would kick off a resync.
2. It would write to the spare drive to ensure it is ok. (we have to
wait
- Message from [EMAIL PROTECTED] -
Date: Wed, 6 Feb 2008 12:58:55 -
From: Steve Fairbairn [EMAIL PROTECTED]
Reply-To: Steve Fairbairn [EMAIL PROTECTED]
Subject: Disk failure during grow, what is the current state.
To: linux-raid@vger.kernel.org
As you can see,
, Nagilum
[EMAIL PROTECTED] said:
[ ... ]
* Doing unaligned writes on a 13+1 or 12+2 is catastrophically
slow because of the RMW cycle. This is of course independent
of how one got to the something like 13+1 or a 12+2.
nagilum Changing a single byte in a 2+1 raid5 or a 13+1 raid5
nagilum requires
28 matches
Mail list logo
