From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org Received: from lists.sourceforge.net (lists.sourceforge.net [216.105.38.7]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by smtp.lore.kernel.org (Postfix) with ESMTPS id 967FFC3601E for ; Mon, 14 Apr 2025 02:38:54 +0000 (UTC) Received: from [127.0.0.1] (helo=sfs-ml-4.v29.lw.sourceforge.com) by sfs-ml-4.v29.lw.sourceforge.com with esmtp (Exim 4.95) (envelope-from ) id 1u49im-0007Pa-Ne; Mon, 14 Apr 2025 02:38:52 +0000 Received: from [172.30.29.66] (helo=mx.sourceforge.net) by sfs-ml-4.v29.lw.sourceforge.com with esmtps (TLS1.2) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.95) (envelope-from ) id 1u49ij-0007PT-Kw for linux-f2fs-devel@lists.sourceforge.net; Mon, 14 Apr 2025 02:38:49 +0000 DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=sourceforge.net; s=x; h=Content-Transfer-Encoding:MIME-Version:Message-ID: Date:Subject:Cc:To:From:Sender:Reply-To:Content-Type:Content-ID: Content-Description:Resent-Date:Resent-From:Resent-Sender:Resent-To:Resent-Cc :Resent-Message-ID:In-Reply-To:References:List-Id:List-Help:List-Unsubscribe: List-Subscribe:List-Post:List-Owner:List-Archive; bh=JfXetmoPRQbTTLON/R2nGujcfRTBz2yeiP3ncw16N30=; b=RzdiAfUqVF40gTcXBiLwmrm1e0 JXGFF4Dbf9XatZ4WxRGC9COwaUQB3+bnvMJMKJhnP1FllHuwSIT2gOqYPSe/s0jvEKbkp5T20xGvk +TnOOIaFrdHji+FWAX5o70lbt63seP6N5ADxHjV6ymu2A4o12dNBURCrFqGu9AoaAuZ0=; DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=sf.net; s=x ; h=Content-Transfer-Encoding:MIME-Version:Message-ID:Date:Subject:Cc:To:From :Sender:Reply-To:Content-Type:Content-ID:Content-Description:Resent-Date: Resent-From:Resent-Sender:Resent-To:Resent-Cc:Resent-Message-ID:In-Reply-To: References:List-Id:List-Help:List-Unsubscribe:List-Subscribe:List-Post: List-Owner:List-Archive; bh=JfXetmoPRQbTTLON/R2nGujcfRTBz2yeiP3ncw16N30=; b=R 3Mz6Z5nmacHiljSuj/eM/LMyar+CxP5UzA3OaRwF7lud8QWKNZJrthD2h5sFecY2J0YKkmvl3+2zj K13dOeYi+OXJEM09uUlpANatDmFEljB4JlCo7oPoaw1pxt0uLDNwSY/NTNM3i70IX7QIjOPGDL18Q MjwZPLjGXVWZxE8s=; Received: from tor.source.kernel.org ([172.105.4.254]) by sfi-mx-2.v28.lw.sourceforge.com with esmtps (TLS1.2:ECDHE-RSA-AES256-GCM-SHA384:256) (Exim 4.95) id 1u49iT-0000QB-QM for linux-f2fs-devel@lists.sourceforge.net; Mon, 14 Apr 2025 02:38:49 +0000 Received: from smtp.kernel.org (transwarp.subspace.kernel.org [100.75.92.58]) by tor.source.kernel.org (Postfix) with ESMTP id EB85F61145; Mon, 14 Apr 2025 02:38:13 +0000 (UTC) Received: by smtp.kernel.org (Postfix) with ESMTPSA id 919F6C4CEDD; Mon, 14 Apr 2025 02:38:26 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org; s=k20201202; t=1744598307; bh=QTnFH4Kmdg4S9W0Y4dkn7md9ITPZGCuQ6Cyt+8xqIS8=; h=From:To:Cc:Subject:Date:From; b=TR++G5fSIogZwOatZCdzi0uiBT4DWA2Yy8uCpqkYzOc2gg018ZidljGJkEkDPy9oO TKeVUDBs2K9N8JxjW9UxjLwRfEn2wgkzv13cFvuQfMMDiHr5NlFO/opx3XItUrES+9 TktW5pYmpwA6JTfmMVG4/6NcyV9y+jk7Zn8352g+0wy1zqBemjJ+VOSHe39bsyPaP5 js9hcpqQDzNxFA8uy0AuPv83CDPj0NQOpp/dMYSnBj2CrwXiP100tfedqYD1gKDnDG C5PdbmEjxjazOoz5A0gAMbZ3viP58l2No2ep/cCMKUhUWyYu5Z6iN7/jyL6rRLuqfE dXf6ucOIzhRMA== To: jaegeuk@kernel.org Date: Mon, 14 Apr 2025 10:38:18 +0800 Message-ID: <20250414023819.581303-1-chao@kernel.org> X-Mailer: git-send-email 2.49.0.604.gff1f9ca942-goog MIME-Version: 1.0 X-Headers-End: 1u49iT-0000QB-QM Subject: [f2fs-dev] [PATCH v4 1/2] Revert "resize.f2fs: add option for large_nat_bitmap feature" X-BeenThere: linux-f2fs-devel@lists.sourceforge.net X-Mailman-Version: 2.1.21 Precedence: list List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , From: Chao Yu via Linux-f2fs-devel Reply-To: Chao Yu Cc: linux-f2fs-devel@lists.sourceforge.net Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Errors-To: linux-f2fs-devel-bounces@lists.sourceforge.net This reverts commit daa0f8b9e9b1eea6c85e5c169b809254d9d7074e. As Juhyung reported in [1]: Here's what I did: 1. Remounted to checkpoint=disable 2. Create a dm-snapshot of the current root device 3. Mount snapshot to replay the log 4. Unmount 5. Resize sector 487248896 to 486539264 // ./resize.f2fs -d 3 -s -i /dev/mapper/snap -t 486539264 Latest f2fs-tools was used: 33c5b9539af2 f2fs_io: add fragread command to evaluate fragmented buffer for reads This reproduced the mount and fsck failure. Mount log: [442431.020594] F2FS-fs (dm-2): invalid crc_offset: 0 [442431.130055] F2FS-fs (dm-2): SIT is corrupted node# 13615201 vs 13616290 [442431.139684] F2FS-fs (dm-2): Failed to initialize F2FS segment manager (-117) I checked below testcases: truncate -s $((512*1024*1024*1024)) img mkfs.f2fs -f img $((256*1024*1024)) Description Test command FSCK output a) shrink w/ -s resize.f2fs -s -i img -t $((128*1024*1024)) Fine b) expand w/ -s resize.f2fs -s -i img -t $((1024*1024*1024)) Corrupted c) shrink w/o -s resize.f2fs -i img -t $((128*1024*1024)) No run d) expand w/o -s resize.f2fs -i img -t $((1024*1024*1024)) Fine Output from b): [ASSERT] (check_block_count:2299) --> Wrong SIT valid blocks: segno=0x29400, 0 vs. 13 The root cause is: safe mode (-s option) is conflict w/ large nat bitmap feature (-i option), since once we enable large nat bitmap, layout of checkpoint will be changed [2], we must relocate nat/sit_bitmap to the end of new location of cp_checksum, however in safe mode, we won't change metadata of checkpoint, so we need to keep nat/sit_bitmap as it is, which includes checksum data in its old location. Let's revert -i support for resize.f2fs first, and then reenable it after fix and well tested. Thanks a lot for the help from Juhyung, including providing reproducer and hints. [1] https://lore.kernel.org/linux-f2fs-devel/CAD14+f3D6iPOBxEgkZxxTsXCfwRKb9ph68JtUk3H9cn8ovLt9w@mail.gmail.com/ [2] https://lore.kernel.org/linux-f2fs-devel/20190514093340.40217-2-yuchao0@huawei.com/ Fixes: daa0f8b ("resize.f2fs: add option for large_nat_bitmap feature") Reported-by: Juhyung Park Signed-off-by: Chao Yu --- v4: - no changes fsck/main.c | 6 +----- fsck/resize.c | 3 --- man/resize.f2fs.8 | 6 ------ 3 files changed, 1 insertion(+), 14 deletions(-) diff --git a/fsck/main.c b/fsck/main.c index 524dbb1..af40613 100644 --- a/fsck/main.c +++ b/fsck/main.c @@ -141,7 +141,6 @@ void resize_usage() MSG(0, "[options]:\n"); MSG(0, " -d debug level [default:0]\n"); MSG(0, " -H support write hint\n"); - MSG(0, " -i extended node bitmap, node ratio is 20%% by default\n"); MSG(0, " -o overprovision percentage [default:auto]\n"); MSG(0, " -s safe resize (Does not resize metadata)\n"); MSG(0, " -t target sectors [default: device size]\n"); @@ -602,7 +601,7 @@ void f2fs_parse_options(int argc, char *argv[]) #endif } else if (!strcmp("resize.f2fs", prog)) { #ifdef WITH_RESIZE - const char *option_string = "d:fHst:io:V"; + const char *option_string = "d:fHst:o:V"; c.func = RESIZE; while ((option = getopt(argc, argv, option_string)) != EOF) { @@ -637,9 +636,6 @@ void f2fs_parse_options(int argc, char *argv[]) ret = sscanf(optarg, "%"PRIx64"", &c.target_sectors); break; - case 'i': - c.large_nat_bitmap = 1; - break; case 'o': c.new_overprovision = atof(optarg); break; diff --git a/fsck/resize.c b/fsck/resize.c index 9b3b071..2681b9f 100644 --- a/fsck/resize.c +++ b/fsck/resize.c @@ -531,9 +531,6 @@ static void rebuild_checkpoint(struct f2fs_sb_info *sbi, /* update nat_bits flag */ flags = update_nat_bits_flags(new_sb, cp, get_cp(ckpt_flags)); - if (c.large_nat_bitmap) - flags |= CP_LARGE_NAT_BITMAP_FLAG; - if (flags & CP_COMPACT_SUM_FLAG) flags &= ~CP_COMPACT_SUM_FLAG; if (flags & CP_LARGE_NAT_BITMAP_FLAG) diff --git a/man/resize.f2fs.8 b/man/resize.f2fs.8 index d41ad79..02ff245 100644 --- a/man/resize.f2fs.8 +++ b/man/resize.f2fs.8 @@ -21,9 +21,6 @@ resize.f2fs \- resize filesystem size .B \-H ] [ -.B \-i -] -[ .B \-s ] [ @@ -59,9 +56,6 @@ best number will be assigned automatically according to the partition size. .BI \-H Specify support write hint. .TP -.BI \-i -Enable extended node bitmap. -.TP .BI \-s Enable safe resize. .TP -- 2.49.0 _______________________________________________ Linux-f2fs-devel mailing list Linux-f2fs-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/linux-f2fs-devel