From mboxrd@z Thu Jan 1 00:00:00 1970 From: Mike Hardy Subject: Re: mdadm source rpm build error + command-line parsing error + resync reporting problem Date: Thu, 08 Dec 2005 22:31:31 -0800 Message-ID: <439924C3.5020509@h3c.com> References: <4399198D.5050206@h3c.com> <17305.7226.5007.891700@cse.unsw.edu.au> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: <17305.7226.5007.891700@cse.unsw.edu.au> Sender: linux-raid-owner@vger.kernel.org To: Neil Brown Cc: linux-raid@vger.kernel.org List-Id: linux-raid.ids Neil Brown wrote: > On Thursday December 8, mhardy@h3c.com wrote: > >>Not really on-topic, but has anyone else gotten ext2online to work? I >>get this "Dec 8 21:27:02 istanbul kernel: JBD: ext2online wants too >>many credits (2050 > 2048)" after letting it attempt to extend the FS to >>cover the entire device. > > > I haven't used ext2online myself, but I believe that there are some > aspects of the filesystem that it is not able to resize, and you have > to have created your filesystem with the understanding that you might > want to grow it later. > From the mkfs.ext3 man page: > > -E extended-options > ... > resize=max-online-resize > Reserve enough space so that the block group > descriptor table can grow to support a filesystem > that has max-online-resize blocks. > > > Not a very desirable situation, but just part of the legacy that > ext2/3 brings with it. > > So this time when you mkfs your new arrays, plan for growth :-) > > NeilBrown I was able to boot off the redhat install CD, use the 'linux rescue' mode to get a shell, and then use resize2fs to do what I wanted. Basically, if you didn't plan ahead with the right max-online-resize option, you can still grow the filesystem, just not while it's mounted and running. So at this point, I've got twice the disk space on both the systems I was working on. If only I had more to do, now that I know what I'm doing... -Mike