From: Mike Hardy <mhardy@h3c.com>
To: Neil Brown <neilb@suse.de>
Cc: linux-raid@vger.kernel.org
Subject: Re: mdadm source rpm build error + command-line parsing error + resync reporting problem
Date: Thu, 08 Dec 2005 22:31:31 -0800 [thread overview]
Message-ID: <439924C3.5020509@h3c.com> (raw)
In-Reply-To: <17305.7226.5007.891700@cse.unsw.edu.au>
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
next prev parent reply other threads:[~2005-12-09 6:31 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-12-09 5:43 mdadm source rpm build error + command-line parsing error + resync reporting problem Mike Hardy
2005-12-09 5:55 ` Neil Brown
2005-12-09 6:31 ` Mike Hardy [this message]
-- strict thread matches above, loose matches on Subject: below --
2005-12-09 5:11 Mike Hardy
2005-12-09 5:16 ` Mike Hardy
2005-12-09 5:33 ` Neil Brown
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=439924C3.5020509@h3c.com \
--to=mhardy@h3c.com \
--cc=linux-raid@vger.kernel.org \
--cc=neilb@suse.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.