From: Tomasz Chmielewski <mangoo@wpkg.org>
To: Goswin von Brederlow <brederlo@informatik.uni-tuebingen.de>
Cc: linux-raid@vger.kernel.org,
LVM general discussion and development <linux-lvm@redhat.com>
Subject: Re: [linux-lvm] Q: Online resizing ext3 FS
Date: Thu, 13 Sep 2007 15:07:52 +0200 [thread overview]
Message-ID: <46E93628.3060902@wpkg.org> (raw)
In-Reply-To: <87ejh2n2kk.fsf@informatik.uni-tuebingen.de>
Goswin von Brederlow schrieb:
> Tomasz Chmielewski <mangoo@wpkg.org> writes:
(...)
>> Yes, I tried to online resize a similar filesystem (600 MB to 1.2 TB)
>> and it didn't work.
>>
>> At some point, resize2fs would just exit with errors.
>> I tried to do it several times before I figured out what's missing;
>> sometimes, I interrupted the process with ctrl+c. No data loss
>> occurred.
>>
>> To do an online ext3 resize, the filesystem needs a "resize_inode"
>> feature. You can check the features with dumpe2fs:
>
> So was that what you were missing or did some other error occur?
>
> I tried to resize an fs without resize_inode and it just plain told me
> and abrted.
It was working for some time (15 or 30 minutes?), the fs grew a couple
of gigabytes, and then it exited with an error. At first I thought it's
because the fs might need fsck, but after I did fsck, it didn't help -
next online tries didn't increase the fs anymore.
--
Tomasz Chmielewski
http://wpkg.org
next prev parent reply other threads:[~2007-09-13 13:08 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-09-12 14:36 [linux-lvm] Q: Online resizing ext3 FS Chris Osicki
2007-09-12 14:56 ` Tomasz Chmielewski
[not found] ` <87ejh2n2kk.fsf@informatik.uni-tuebingen.de>
2007-09-13 13:07 ` Tomasz Chmielewski [this message]
2007-09-18 18:00 ` Bill Davidsen
-- strict thread matches above, loose matches on Subject: below --
2007-09-12 14:40 Hiren Joshi
2007-09-12 20:04 ` Stuart D. Gathman
2007-09-15 10:42 ` raptorfan
2007-09-13 8:09 Hiren Joshi
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=46E93628.3060902@wpkg.org \
--to=mangoo@wpkg.org \
--cc=brederlo@informatik.uni-tuebingen.de \
--cc=linux-lvm@redhat.com \
--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).