Received-SPF: pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) client-ip=209.132.180.67;
Subject: Re: [PATCH V2 2/2] f2fs: Add a new CP flag to help fsck fix resize
 SPO issues
To:     Sahitya Tummala <stummala@codeaurora.org>,
        Jaegeuk Kim <jaegeuk@kernel.org>,
        <linux-f2fs-devel@lists.sourceforge.net>
CC:     <linux-kernel@vger.kernel.org>
References: <1583245766-3351-1-git-send-email-stummala@codeaurora.org>
 <1583245766-3351-2-git-send-email-stummala@codeaurora.org>
From:   Chao Yu <yuchao0@huawei.com>
Message-ID: <e164f166-5c3f-a2ce-aec6-ff01ecb902e8@huawei.com>
Date:   Fri, 6 Mar 2020 09:19:39 +0800
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:52.0) Gecko/20100101
 Thunderbird/52.9.1
MIME-Version: 1.0
In-Reply-To: <1583245766-3351-2-git-send-email-stummala@codeaurora.org>
Content-Type: text/plain; charset="windows-1252"
Content-Language: en-US
Content-Transfer-Encoding: 7bit
Sender: linux-kernel-owner@vger.kernel.org
Precedence: bulk

On 2020/3/3 22:29, Sahitya Tummala wrote:
> Add and set a new CP flag CP_RESIZEFS_FLAG during
> online resize FS to help fsck fix the metadata mismatch
> that may happen due to SPO during resize, where SB
> got updated but CP data couldn't be written yet.
> 
> fsck errors -
> Info: CKPT version = 6ed7bccb
>         Wrong user_block_count(2233856)
> [f2fs_do_mount:3365] Checkpoint is polluted

I'm not against this patch, however without this change, could
fsck have any chance to repair old image?

> 
> Signed-off-by: Sahitya Tummala <stummala@codeaurora.org>

Reviewed-by: Chao Yu <yuchao0@huawei.com>