From: Jaegeuk Kim <jaegeuk@kernel.org>
To: beroal <me@beroal.in.ua>
Cc: linux-f2fs-devel@lists.sourceforge.net
Subject: Re: [f2fs-dev] `mount` reports an error, but `fsck.f2fs` does not
Date: Tue, 30 Mar 2021 18:41:46 -0700 [thread overview]
Message-ID: <YGPTWqUtHqEyRLMv@google.com> (raw)
In-Reply-To: <bc3759b9-c606-5e77-40f0-c590bbc53bfb@beroal.in.ua>
Hi,
On 03/27, beroal wrote:
> Ping.
>
> On 20.03.21 00:46, beroal wrote:
> > Hi. After I extended a partition containing F2FS with a recent version
> > of Gparted, the partition no longer mounts. `mount` reports an error,
> > but `fsck.f2fs` does not see any problem (well, except for `Invalid CP
> > CRC offset: 0`) and does not fix the file system.
> >
> > ```
> > losetup /dev/loop0 arch-os.img
> > mount -t f2fs -o ro /dev/loop0 /root/mnt/temp
> > ```
> >
> > ```
> > [ 6890.647749] F2FS-fs (loop0): Wrong valid_user_blocks: 16040048,
> > user_block_count: 10016768
> > [ 6890.647808] F2FS-fs (loop0): Failed to get valid F2FS checkpoint
> > ```
> >
> > ```
> > losetup -d /dev/loop0
> > fsck.f2fs arch-os.img
May I ask run this?
# fsck.f2fs -d 3 arch-os.img?
Thanks,
> > ```
> >
> > ```
> > Info: Segments per section = 1
> > Info: Sections per zone = 1
> > Info: sector size = 512
> > Info: total sectors = 162916352 (79549 MB)
> > Info: MKFS version
> > "Linux version 4.4.1-2-ARCH (builduser@foutrelis) (gcc version 5.3.0
> > (GCC) ) #1 SMP PREEMPT Wed Feb 3 13:12:33 UTC 2016"
> > Info: FSCK version
> > from "Linux version 5.7.12-arch1-1 (linux@archlinux) (gcc version
> > 10.1.0 (GCC), GNU ld (GNU Binutils) 2.34.0) #1 SMP PREEMPT Fri, 31 Jul
> > 2020 17:38:22 +0000"
> > to "Linux version 5.11.7-arch1-1 (linux@archlinux) (gcc (GCC)
> > 10.2.0, GNU ld (GNU Binutils) 2.36.1) #1 SMP PREEMPT Wed, 17 Mar 2021
> > 16:59:58 +0000"
> > Info: superblock features = 0 :
> > Info: superblock encrypt level = 0, salt =
> > 00000000000000000000000000000000
> > Info: total FS sectors = 162916352 (79549 MB)
> > Invalid CP CRC offset: 0
> > Info: CKPT version = a14d4c
> > Info: Checked valid nat_bits in checkpoint
> > Info: checkpoint state = 81 : nat_bits unmount
> >
> > [FSCK] Unreachable nat entries [Ok..] [0x0]
> > [FSCK] SIT valid block bitmap checking [Ok..]
> > [FSCK] Hard link checking for regular file [Ok..] [0x719]
> > [FSCK] valid_block_count matching with CP [Ok..] [0xf4c070]
> > [FSCK] valid_node_count matching with CP (de lookup) [Ok..] [0xe242a]
> > [FSCK] valid_node_count matching with CP (nat lookup) [Ok..] [0xe242a]
> > [FSCK] valid_inode_count matched with CP [Ok..] [0xe0470]
> > [FSCK] free segment_count matched with CP [Ok..] [0x1d6b]
> > [FSCK] next block offset is free [Ok..]
> > [FSCK] fixing SIT types
> > [FSCK] other corrupted bugs [Ok..]
> >
> > Done: 14.100000 secs
> > ```
> >
> > Can I fix this file system and how?
> >
> > f2fs-tools 1.14.0
> >
> >
> >
> > _______________________________________________
> > Linux-f2fs-devel mailing list
> > Linux-f2fs-devel@lists.sourceforge.net
> > https://lists.sourceforge.net/lists/listinfo/linux-f2fs-devel
>
>
> _______________________________________________
> Linux-f2fs-devel mailing list
> Linux-f2fs-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/linux-f2fs-devel
_______________________________________________
Linux-f2fs-devel mailing list
Linux-f2fs-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/linux-f2fs-devel
next prev parent reply other threads:[~2021-03-31 1:42 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-19 22:46 [f2fs-dev] `mount` reports an error, but `fsck.f2fs` does not beroal
2021-03-27 13:27 ` beroal
2021-03-31 1:41 ` Jaegeuk Kim [this message]
2021-03-31 5:38 ` beroal
2021-03-31 15:48 ` Jaegeuk Kim
2021-04-01 0:19 ` beroal
2021-04-01 3:24 ` Jaegeuk Kim
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=YGPTWqUtHqEyRLMv@google.com \
--to=jaegeuk@kernel.org \
--cc=linux-f2fs-devel@lists.sourceforge.net \
--cc=me@beroal.in.ua \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).