* [f2fs-dev] `mount` reports an error, but `fsck.f2fs` does not
@ 2021-03-19 22:46 beroal
2021-03-27 13:27 ` beroal
0 siblings, 1 reply; 7+ messages in thread
From: beroal @ 2021-03-19 22:46 UTC (permalink / raw)
To: linux-f2fs-devel
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
```
```
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
^ permalink raw reply [flat|nested] 7+ messages in thread
* Re: [f2fs-dev] `mount` reports an error, but `fsck.f2fs` does not
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
0 siblings, 1 reply; 7+ messages in thread
From: beroal @ 2021-03-27 13:27 UTC (permalink / raw)
To: linux-f2fs-devel
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
> ```
>
> ```
> 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
^ permalink raw reply [flat|nested] 7+ messages in thread
* Re: [f2fs-dev] `mount` reports an error, but `fsck.f2fs` does not
2021-03-27 13:27 ` beroal
@ 2021-03-31 1:41 ` Jaegeuk Kim
2021-03-31 5:38 ` beroal
0 siblings, 1 reply; 7+ messages in thread
From: Jaegeuk Kim @ 2021-03-31 1:41 UTC (permalink / raw)
To: beroal; +Cc: linux-f2fs-devel
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
^ permalink raw reply [flat|nested] 7+ messages in thread
* Re: [f2fs-dev] `mount` reports an error, but `fsck.f2fs` does not
2021-03-31 1:41 ` Jaegeuk Kim
@ 2021-03-31 5:38 ` beroal
2021-03-31 15:48 ` Jaegeuk Kim
0 siblings, 1 reply; 7+ messages in thread
From: beroal @ 2021-03-31 5:38 UTC (permalink / raw)
To: Jaegeuk Kim; +Cc: linux-f2fs-devel
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.
_______________________________________________
Linux-f2fs-devel mailing list
Linux-f2fs-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/linux-f2fs-devel
^ permalink raw reply [flat|nested] 7+ messages in thread
* Re: [f2fs-dev] `mount` reports an error, but `fsck.f2fs` does not
2021-03-31 5:38 ` beroal
@ 2021-03-31 15:48 ` Jaegeuk Kim
2021-04-01 0:19 ` beroal
0 siblings, 1 reply; 7+ messages in thread
From: Jaegeuk Kim @ 2021-03-31 15:48 UTC (permalink / raw)
To: beroal; +Cc: linux-f2fs-devel
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.
>
>
> _______________________________________________
> 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
^ permalink raw reply [flat|nested] 7+ messages in thread
* Re: [f2fs-dev] `mount` reports an error, but `fsck.f2fs` does not
2021-03-31 15:48 ` Jaegeuk Kim
@ 2021-04-01 0:19 ` beroal
2021-04-01 3:24 ` Jaegeuk Kim
0 siblings, 1 reply; 7+ messages in thread
From: beroal @ 2021-04-01 0:19 UTC (permalink / raw)
To: Jaegeuk Kim; +Cc: linux-f2fs-devel
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.
_______________________________________________
Linux-f2fs-devel mailing list
Linux-f2fs-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/linux-f2fs-devel
^ permalink raw reply [flat|nested] 7+ messages in thread
* Re: [f2fs-dev] `mount` reports an error, but `fsck.f2fs` does not
2021-04-01 0:19 ` beroal
@ 2021-04-01 3:24 ` Jaegeuk Kim
0 siblings, 0 replies; 7+ messages in thread
From: Jaegeuk Kim @ 2021-04-01 3:24 UTC (permalink / raw)
To: beroal; +Cc: linux-f2fs-devel
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
^ permalink raw reply [flat|nested] 7+ messages in thread
end of thread, other threads:[~2021-04-01 3:25 UTC | newest]
Thread overview: 7+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
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 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).