From: Brad Campbell <lists2009@fnarfbargle.com>
To: Theodore Ts'o <tytso@mit.edu>
Cc: Azat Khuzhin <a3at.mail@gmail.com>, linux-ext4@vger.kernel.org
Subject: Re: Online resize issue with 3.13.5 & 3.15.6
Date: Sat, 26 Jul 2014 11:31:02 +0800 [thread overview]
Message-ID: <53D320F6.40809@fnarfbargle.com> (raw)
In-Reply-To: <20140725140715.GR1865@thunk.org>
On 25/07/14 22:07, Theodore Ts'o wrote:
> On Fri, Jul 25, 2014 at 07:44:07PM +0800, Brad Campbell wrote:
>>
>> Appreciate you taking a look at this and I see where you are going with it.
>
> This patch looks good to me. If you could give it a try, I would
> appreciate it.
>
> This looks like the same bug which was reported in Ubuntu:
>
> https://bugs.launchpad.net/ubuntu/+source/e2fsprogs/+bug/1321958
The patch would not apply automatically to 1.42.11 but was easy enough
to apply by hand.
root@srv:~/src/e2fsprogs/e2fsprogs-1.42.11/resize# ./resize2fs -d 255
/dev/md0
resize2fs 1.42.11 (09-Jul-2014)
fs has 4007207 inodes, 1957 groups required.
fs requires 4374122900 data blocks.
With 1957 group(s), we have 63820826 blocks available.
Added 131540 extra group(s), blks_needed 4374122900, data_blocks
4356990326, last_start 4356599580
Added 523 extra group(s), blks_needed 4374122900, data_blocks
4374059350, last_start 4373440788
Added 2 extra group(s), blks_needed 4374122900, data_blocks 4374124886,
last_start 4373473426
Last group's overhead is 1430
Need 649474 data blocks in last group
Final size of last group is 650904
Estimated blocks needed: 4391437088
Extents safety margin: 2826959
Filesystem at /dev/md0 is mounted on /server; on-line resizing required
old_desc_blocks = 2768, new_desc_blocks = 2795
./resize2fs: Invalid argument While checking for on-line resizing support
[489412.650430] EXT4-fs (md0): resizing filesystem from 5804916736 to
5860149888 blocks
[489412.700282] EXT4-fs warning (device md0): verify_reserved_gdb:713:
reserved GDT 2769 missing grp 177147 (5804755665)
[489412.739676] EXT4-fs (md0): resized filesystem to 5860149888
[489413.215230] EXT4-fs warning (device md0): ext4_group_extend:1720:
can't shrink FS - resize aborted
next prev parent reply other threads:[~2014-07-26 3:31 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-07-20 11:26 Online resize issue with 3.13.5 & 3.15.6 Brad Campbell
2014-07-21 1:03 ` Brad Campbell
2014-07-25 4:33 ` Brad Campbell
2014-07-25 8:13 ` Azat Khuzhin
2014-07-25 11:44 ` Brad Campbell
2014-07-25 14:07 ` Theodore Ts'o
2014-07-26 3:31 ` Brad Campbell [this message]
2014-07-26 4:12 ` Brad Campbell
2014-07-26 7:04 ` Azat Khuzhin
2014-07-26 7:45 ` Azat Khuzhin
2014-07-26 12:45 ` Theodore Ts'o
2014-07-26 12:57 ` Azat Khuzhin
2014-07-26 13:46 ` Brad Campbell
2014-07-26 13:56 ` Theodore Ts'o
2014-07-29 2:46 ` Theodore Ts'o
2014-07-29 8:00 ` Brad Campbell
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=53D320F6.40809@fnarfbargle.com \
--to=lists2009@fnarfbargle.com \
--cc=a3at.mail@gmail.com \
--cc=linux-ext4@vger.kernel.org \
--cc=tytso@mit.edu \
/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.