From mboxrd@z Thu Jan 1 00:00:00 1970 From: Jules Bean Subject: Re: After partition resize, RAID5 array does not assemble on boot Date: Fri, 06 Jun 2008 15:46:32 +0100 Message-ID: <48494DC8.20308@jellybean.co.uk> References: <4844E994.8020808@jellybean.co.uk> <4845B573.7090801@jellybean.co.uk> <48675.192.168.1.70.1212528422.squirrel@neil.brown.name> <484636B9.20700@jellybean.co.uk> <48464B3A.7070206@dgreaves.com> <4846529B.1000809@jellybean.co.uk> <484681AF.8030004@dgreaves.com> <48469523.4050601@jellybean.co.uk> <4849412D.9030607@tmr.com> <48494CC3.5050805@dgreaves.com> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: <48494CC3.5050805@dgreaves.com> Sender: linux-raid-owner@vger.kernel.org To: David Greaves Cc: Bill Davidsen , NeilBrown , linux-raid@vger.kernel.org List-Id: linux-raid.ids David Greaves wrote: > Bill Davidsen wrote: >> What is needed is to do something like assume-clean on the old data and >> a sync on the new chunks. I don't see that there is a remotely safe way >> to do that, > > I assumed that --grow --size=max on a v1.2 superblock would do exactly that... > (well, start a resync at the old partition-end location anyway). I can confirm that when I did this on my array, it only resynced from the old-end. It "started" at 70% complete or so. Jules