From: Azat Khuzhin <a3at.mail@gmail.com>
To: Theodore Ts'o <tytso@mit.edu>
Cc: Brad Campbell <lists2009@fnarfbargle.com>, linux-ext4@vger.kernel.org
Subject: Re: Online resize issue with 3.13.5 & 3.15.6
Date: Sat, 26 Jul 2014 16:57:05 +0400 [thread overview]
Message-ID: <20140726125705.GD24045@azat> (raw)
In-Reply-To: <20140726124557.GB6725@thunk.org>
On Sat, Jul 26, 2014 at 08:45:57AM -0400, Theodore Ts'o wrote:
> Filesystem features: has_journal ext_attr resize_inode dir_index filetype
> extent 64bit flex_bg sparse_super large_file huge_file uninit_bg dir_nlink
> extra_isize
> Block count: 5804916736
> Reserved GDT blocks: 585
>
> If the block count is greater than 2**32 (4294967296), resize_inode
> must not be set, and reserved GDT blocks should be zero. So this is
> definitely not right.
I've just tried to reproduce this on 24T->48T raid0 array (resizing from
24T to 48T), without any success.
And that's why: I don't have resize_inode in filesystem features.
Thanks for pointing on this, Ted.
Cheers,
Azat.
next prev parent reply other threads:[~2014-07-26 12:57 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
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 [this message]
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=20140726125705.GD24045@azat \
--to=a3at.mail@gmail.com \
--cc=linux-ext4@vger.kernel.org \
--cc=lists2009@fnarfbargle.com \
--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.