Received-SPF: pass (google.com: domain of linux-ext4-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) client-ip=2620:137:e000::1:20;
From:   "Theodore Ts'o" <tytso@mit.edu>
To:     jerrylee@qnap.com, linux-ext4@vger.kernel.org
Cc:     "Theodore Ts'o" <tytso@mit.edu>
Subject: Re: [PATCH] ext4: continue to expand file system when the target size doesn't reach
Date:   Tue, 27 Sep 2022 17:53:33 -0400
Message-Id: <166431556704.3511882.8729097617255264599.b4-ty@mit.edu>
In-Reply-To: <PU1PR04MB22635E739BD21150DC182AC6A18C9@PU1PR04MB2263.apcprd04.prod.outlook.com>
References: <PU1PR04MB22635E739BD21150DC182AC6A18C9@PU1PR04MB2263.apcprd04.prod.outlook.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 8bit
Precedence: bulk

On Mon, 18 Jul 2022 10:25:19 +0000, Jerry Lee 李修賢 wrote:
> When expanding a file system from (16TiB-2MiB) to 18TiB, the operation
> exits early which leads to result inconsistency between resize2fs and
> Ext4 kernel driver.
> 
> === before ===
> ○ → resize2fs /dev/mapper/thin
> resize2fs 1.45.5 (07-Jan-2020)
> Filesystem at /dev/mapper/thin is mounted on /mnt/test; on-line resizing required
> old_desc_blocks = 2048, new_desc_blocks = 2304
> The filesystem on /dev/mapper/thin is now 4831837696 (4k) blocks long.
> 
> [...]

Applied, thanks!

[1/1] ext4: continue to expand file system when the target size doesn't reach
      commit: df3cb754d13d2cd5490db9b8d536311f8413a92e

Best regards,
-- 
Theodore Ts'o <tytso@mit.edu>