Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > linux.debian.kernel > #86077 > unrolled thread
| Started by | Heinz Repp <heinz.repp@arcor.de> |
|---|---|
| First post | 2025-02-22 15:00 +0100 |
| Last post | 2025-02-26 03:30 +0100 |
| Articles | 4 — 3 participants |
Back to article view | Back to linux.debian.kernel
This discussion starts older than the indexed window; earlier articles aren't shown. The article labeled Started by
below is the oldest one visible, not the original post.
Bug#1021927: Bug is still present in current kernels Heinz Repp <heinz.repp@arcor.de> - 2025-02-22 15:00 +0100
Bug#1021927: Bug is still present in current kernels Salvatore Bonaccorso <carnil@debian.org> - 2025-02-22 19:40 +0100
Bug#1021927: >= Kernel 5.19 reports corrupted f2fs without apparent actual corruption Salvatore Bonaccorso <carnil@debian.org> - 2025-02-25 19:10 +0100
Bug#1021927: >= Kernel 5.19 reports corrupted f2fs without apparent actual corruption Chao Yu <chao@kernel.org> - 2025-02-26 03:30 +0100
| From | Heinz Repp <heinz.repp@arcor.de> |
|---|---|
| Date | 2025-02-22 15:00 +0100 |
| Subject | Bug#1021927: Bug is still present in current kernels |
| Message-ID | <KiYcV-19jE-1@gated-at.bofh.it> |
Since kernel 5.19.x this bug is present in all newer kernels, up to 6.12.12. On every boot, it prints: > Info: Fix the reported corruption. > Info: [/dev/sdb4] SanDisk SDSSDHTI > Info: MKFS Version > "Linux version 4.3.0-1-amd64 (debian-kernel@lists.debian.org) (gcc version 5.3.1 20160101 (Debian 5.3.1-5) ) #1 SMP Debian 4.3.3-5 (2016-01-04)" > Info: FSCK Version > from "Linux version 4.3.0-1-amd64 (debian-kernel@lists.debian.org) (gcc version 5.3.1 20160121 (Debian 5.3.1-7) ) #1 SMP Debian 4.3.5-1 (2016-02-06)" > to "Linux version 6.12.12-amd64 (debian-kernel@lists.debian.org) (x86_64-linux-gnu-gcc 14 (Debian 14.2.0-16) 14.2.0, GNU ld (GNU Binutils for Debian) 2.43.90.20250127) #1 SMP PREEMPT_DYNAMIC Debian 6.12.12- > 1 (2025-02-02)" > Info: superblock features = 0 : > Info: superblock encrypt level = 0, salt = 00000000000000000000000000000000 > Info: Segments per section = 1 > Info: Sections per zone = 1 > Info: Total FS sectors = 233906176 (114212 MB) > Info: CKPT version = 4b0b40 > Info: checkpoint state = 42 : crc orphan_inodes sudden-power-off > Info: No error was reported > [ 10,619367] First, there is a reported corruption. But then, it says "No error was reported". That's a little bit crazy. This came up with kernel 5.19, without changing f2fs, but maybe this bug lives in f2fs? Greetings Heinz Repp
[toc] | [next] | [standalone]
| From | Salvatore Bonaccorso <carnil@debian.org> |
|---|---|
| Date | 2025-02-22 19:40 +0100 |
| Message-ID | <Kj2zT-1c9p-1@gated-at.bofh.it> |
| In reply to | #86077 |
Hi Jaegeuk, hi Chao We got the following report in Debian (cf. https://bugs.debian.org/1021927) and quoted in the following: On Sat, Feb 22, 2025 at 02:44:07PM +0100, Heinz Repp wrote: > Since kernel 5.19.x this bug is present in all newer kernels, up to 6.12.12. > On every boot, it prints: > > > Info: Fix the reported corruption. > > Info: [/dev/sdb4] SanDisk SDSSDHTI > > Info: MKFS Version > > "Linux version 4.3.0-1-amd64 (debian-kernel@lists.debian.org) (gcc version 5.3.1 20160101 (Debian 5.3.1-5) ) #1 SMP Debian 4.3.3-5 (2016-01-04)" > > Info: FSCK Version > > from "Linux version 4.3.0-1-amd64 (debian-kernel@lists.debian.org) (gcc version 5.3.1 20160121 (Debian 5.3.1-7) ) #1 SMP Debian 4.3.5-1 (2016-02-06)" > > to "Linux version 6.12.12-amd64 (debian-kernel@lists.debian.org) (x86_64-linux-gnu-gcc 14 (Debian 14.2.0-16) 14.2.0, GNU ld (GNU Binutils for Debian) 2.43.90.20250127) #1 SMP PREEMPT_DYNAMIC Debian 6.12.12- > > 1 (2025-02-02)" > > Info: superblock features = 0 : > > Info: superblock encrypt level = 0, salt = 00000000000000000000000000000000 > > Info: Segments per section = 1 > > Info: Sections per zone = 1 > > Info: Total FS sectors = 233906176 (114212 MB) > > Info: CKPT version = 4b0b40 > > Info: checkpoint state = 42 : crc orphan_inodes sudden-power-off > > Info: No error was reported > > [ 10,619367] > > First, there is a reported corruption. But then, it says "No error was > reported". That's a little bit crazy. This came up with kernel 5.19, without > changing f2fs, but maybe this bug lives in f2fs? > > Greetings > > Heinz Repp Does this ring some bells to you? Regards, Salvatore
[toc] | [prev] | [next] | [standalone]
| From | Salvatore Bonaccorso <carnil@debian.org> |
|---|---|
| Date | 2025-02-25 19:10 +0100 |
| Subject | Bug#1021927: >= Kernel 5.19 reports corrupted f2fs without apparent actual corruption |
| Message-ID | <Kk7xv-1VYZ-1@gated-at.bofh.it> |
| In reply to | #86078 |
Hi I do realize the subject was badly choosed so replying again with a better subject. The downstream Debian report can be found at https://bugs.debian.org/1021927 On Sat, Feb 22, 2025 at 07:26:30PM +0100, Salvatore Bonaccorso wrote: > Hi Jaegeuk, hi Chao > > We got the following report in Debian (cf. > https://bugs.debian.org/1021927) and quoted in the following: > > On Sat, Feb 22, 2025 at 02:44:07PM +0100, Heinz Repp wrote: > > Since kernel 5.19.x this bug is present in all newer kernels, up to 6.12.12. > > On every boot, it prints: > > > > > Info: Fix the reported corruption. > > > Info: [/dev/sdb4] SanDisk SDSSDHTI > > > Info: MKFS Version > > > "Linux version 4.3.0-1-amd64 (debian-kernel@lists.debian.org) (gcc version 5.3.1 20160101 (Debian 5.3.1-5) ) #1 SMP Debian 4.3.3-5 (2016-01-04)" > > > Info: FSCK Version > > > from "Linux version 4.3.0-1-amd64 (debian-kernel@lists.debian.org) (gcc version 5.3.1 20160121 (Debian 5.3.1-7) ) #1 SMP Debian 4.3.5-1 (2016-02-06)" > > > to "Linux version 6.12.12-amd64 (debian-kernel@lists.debian.org) (x86_64-linux-gnu-gcc 14 (Debian 14.2.0-16) 14.2.0, GNU ld (GNU Binutils for Debian) 2.43.90.20250127) #1 SMP PREEMPT_DYNAMIC Debian 6.12.12- > > > 1 (2025-02-02)" > > > Info: superblock features = 0 : > > > Info: superblock encrypt level = 0, salt = 00000000000000000000000000000000 > > > Info: Segments per section = 1 > > > Info: Sections per zone = 1 > > > Info: Total FS sectors = 233906176 (114212 MB) > > > Info: CKPT version = 4b0b40 > > > Info: checkpoint state = 42 : crc orphan_inodes sudden-power-off > > > Info: No error was reported > > > [ 10,619367] > > > > First, there is a reported corruption. But then, it says "No error was > > reported". That's a little bit crazy. This came up with kernel 5.19, without > > changing f2fs, but maybe this bug lives in f2fs? > > > > Greetings > > > > Heinz Repp > > Does this ring some bells to you? > Does this ring some bell? Regards, Salvatore
[toc] | [prev] | [next] | [standalone]
| From | Chao Yu <chao@kernel.org> |
|---|---|
| Date | 2025-02-26 03:30 +0100 |
| Subject | Bug#1021927: >= Kernel 5.19 reports corrupted f2fs without apparent actual corruption |
| Message-ID | <Kkfln-20TS-3@gated-at.bofh.it> |
| In reply to | #86141 |
On 2/26/25 01:57, Salvatore Bonaccorso wrote: > Hi > > I do realize the subject was badly choosed so replying again with a > better subject. The downstream Debian report can be found at > https://bugs.debian.org/1021927 Hi Salvatore, Please don't worry, fsck has checked your device and reported that "Info: No error was reported", it means there is no inconsistent problem in your image. Eric has uploaded a patch to replace the unclear message "Info: Fix the reported corruption." w/ "Info: Automatic fix mode enabled." [1], I guess we will see the change in f2fs-tools 1.17.0+. [1] https://git.kernel.org/pub/scm/linux/kernel/git/jaegeuk/f2fs-tools.git/commit/?h=dev-test&id=84a218572118382f73997c6411ff80c98d3f6f94 Thanks, > > On Sat, Feb 22, 2025 at 07:26:30PM +0100, Salvatore Bonaccorso wrote: >> Hi Jaegeuk, hi Chao >> >> We got the following report in Debian (cf. >> https://bugs.debian.org/1021927) and quoted in the following: >> >> On Sat, Feb 22, 2025 at 02:44:07PM +0100, Heinz Repp wrote: >>> Since kernel 5.19.x this bug is present in all newer kernels, up to 6.12.12. >>> On every boot, it prints: >>> >>>> Info: Fix the reported corruption. >>>> Info: [/dev/sdb4] SanDisk SDSSDHTI >>>> Info: MKFS Version >>>> "Linux version 4.3.0-1-amd64 (debian-kernel@lists.debian.org) (gcc version 5.3.1 20160101 (Debian 5.3.1-5) ) #1 SMP Debian 4.3.3-5 (2016-01-04)" >>>> Info: FSCK Version >>>> from "Linux version 4.3.0-1-amd64 (debian-kernel@lists.debian.org) (gcc version 5.3.1 20160121 (Debian 5.3.1-7) ) #1 SMP Debian 4.3.5-1 (2016-02-06)" >>>> to "Linux version 6.12.12-amd64 (debian-kernel@lists.debian.org) (x86_64-linux-gnu-gcc 14 (Debian 14.2.0-16) 14.2.0, GNU ld (GNU Binutils for Debian) 2.43.90.20250127) #1 SMP PREEMPT_DYNAMIC Debian 6.12.12- >>>> 1 (2025-02-02)" >>>> Info: superblock features = 0 : >>>> Info: superblock encrypt level = 0, salt = 00000000000000000000000000000000 >>>> Info: Segments per section = 1 >>>> Info: Sections per zone = 1 >>>> Info: Total FS sectors = 233906176 (114212 MB) >>>> Info: CKPT version = 4b0b40 >>>> Info: checkpoint state = 42 : crc orphan_inodes sudden-power-off >>>> Info: No error was reported >>>> [ 10,619367] >>> >>> First, there is a reported corruption. But then, it says "No error was >>> reported". That's a little bit crazy. This came up with kernel 5.19, without >>> changing f2fs, but maybe this bug lives in f2fs? >>> >>> Greetings >>> >>> Heinz Repp >> >> Does this ring some bells to you? >> > > Does this ring some bell? > > Regards, > Salvatore
[toc] | [prev] | [standalone]
Back to top | Article view | linux.debian.kernel
csiph-web