From: Brad Campbell <lists2009@fnarfbargle.com>
To: linux-ext4@vger.kernel.org
Subject: Re: Online resize issue with 3.13.5 & 3.15.6
Date: Fri, 25 Jul 2014 12:33:29 +0800 [thread overview]
Message-ID: <53D1DE19.9000503@fnarfbargle.com> (raw)
In-Reply-To: <53CC66DA.2080804@fnarfbargle.com>
On 21/07/14 09:03, Brad Campbell wrote:
> On 20/07/14 19:26, Brad Campbell wrote:
>> G'day all,
>>
>> Machine was running 3.13.5. x86_64.
>>
>> I had a 12 device (2TB) RAID-6 formatted ext4. I added 2 drives to its
>> underlying md and restriped it (no issues). After the restripe I
>> attempted an online resize using ext2progs 1.42.5 (Debian stable). This
>> failed with a message about the size not fitting into 32 bits so I
>> compiled 1.42.11 and tried again.
>
>
> More info:
> I discovered the debug flags, so this is resize2fs -f 255 /dev/md0
>
> last_start just keeps incrementing for as long as I care to leave it run.
>
> fs has 4007207 inodes, 1957 groups required.
> fs requires 4374122900 data blocks.
> With 1957 group(s), we have 63820826 blocks available.
Ping? Working filesystem that locks up resize2fs 1.42.11 and
consequently fails to fill the entire device. Passes fsck cleanly but
will not resize either online or off.
Is there any other data I can provide or pointers on how I might
un-break things?
Regards,
Brad
next prev parent reply other threads:[~2014-07-25 4:33 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 [this message]
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
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=53D1DE19.9000503@fnarfbargle.com \
--to=lists2009@fnarfbargle.com \
--cc=linux-ext4@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 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.