linux-f2fs-devel.lists.sourceforge.net archive mirror
 help / color / mirror / Atom feed
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: Wed, 31 Mar 2021 20:24:52 -0700	[thread overview]
Message-ID: <YGU9BGiHQl908xTd@google.com> (raw)
In-Reply-To: <6c50097b-4666-6218-1c87-b4a494a239d4@beroal.in.ua>

On 04/01, beroal wrote:
> On 31.03.21 18:48, Jaegeuk Kim wrote:
> > On 03/31, beroal wrote:
> > > On 31.03.21 04:41, Jaegeuk Kim wrote:
> > > > 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?
> > > The result is a log of size 270 MB. I'll send it privately to
> > > jaegeuk@kernel.org if you don't mind. It contains directory and file names.
> > Thanks.
> > 
> > segment_count_main                      [0x    9a95 : 39573]
> > -> 39573 * 2MB = 78GB as user space
> > 
> > overprov_segment_count                  [0x    4e29 : 20009]
> > -> 20009 * 2MB = 40GB as overprovisioned space which user can't see.
> > 
> > But,
> > 
> > [FSCK] valid_block_count matching with CP             [Ok..] [0xf4c070]
> > -> 0xf4c070 = 16040048
> > 
> > valid_block_count                       [0x  f4c070 : 16040048]
> > -> So, this is correct.
> > 
> > So, I suspect overprovisioned space is wrong and guess resize.f2fs assigned
> > a wrong value. May I ask from and to which capacities you resized? I may
> > need to reproduce it quickly.
> Resizing was done by Gparted. I don't remember precisely, but the previous
> partition size was around 65536 MiB, and the F2FS used the whole partition.
> The new size most likely was the current size of the partition, 79549 MiB.

Ah, you didn't call resize.f2fs, but just changed the partition size?


_______________________________________________
Linux-f2fs-devel mailing list
Linux-f2fs-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/linux-f2fs-devel

      reply	other threads:[~2021-04-01  3:25 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
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 [this message]

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=YGU9BGiHQl908xTd@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).