Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > linux.debian.kernel > #81123 > unrolled thread
| Started by | Salvatore Bonaccorso <carnil@debian.org> |
|---|---|
| First post | 2023-12-09 15:10 +0100 |
| Last post | 2023-12-29 14:20 +0100 |
| Articles | 7 — 6 participants |
Back to article view | Back to linux.debian.kernel
Bug#1057843: linux: ext4 data corruption in 6.1.64-1 Salvatore Bonaccorso <carnil@debian.org> - 2023-12-09 15:10 +0100
Bug#1057843: linux: ext4 data corruption in 6.1.64-1 Salvatore Bonaccorso <carnil@debian.org> - 2023-12-09 15:40 +0100
Bug#1057843: Guidelines for affected users Stephan Verbücheln <verbuecheln@posteo.de> - 2023-12-10 09:10 +0100
Bug#1057843: Guidelines for affected users which use etx4 Umberto Zappi <uzappi@gmail.com> - 2023-12-10 11:10 +0100
Bug#1057843: linux: ext4 data corruption in 6.1.64-1 helios.solaris@gmx.ch - 2023-12-12 11:40 +0100
Bug#1057843: linux: ext4 data corruption in 6.1.64-1 BW <m40636067@gmail.com> - 2023-12-12 13:00 +0100
Bug#1057843: Jamirais Ismail <redmiabiru94@gmail.com> - 2023-12-29 14:20 +0100
| From | Salvatore Bonaccorso <carnil@debian.org> |
|---|---|
| Date | 2023-12-09 15:10 +0100 |
| Subject | Bug#1057843: linux: ext4 data corruption in 6.1.64-1 |
| Message-ID | <HJ6bL-coO8-1@gated-at.bofh.it> |
Source: linux Version: 6.1.64-1 Severity: grave Tags: upstream Justification: causes non-serious data loss X-Debbugs-Cc: debian-release@lists.debian.org, carnil@debian.org, adsb@debian.org Hi I'm filling this for visibility. There might be a ext4 data corruption issue with the kernel released in the 12.3 bookworm point release (which is addressed in 6.1.66 upstream already). The report about the regression and some details: https://lore.kernel.org/stable/20231205122122.dfhhoaswsfscuhc3@quack3/ Regards, Salvatore
[toc] | [next] | [standalone]
| From | Salvatore Bonaccorso <carnil@debian.org> |
|---|---|
| Date | 2023-12-09 15:40 +0100 |
| Message-ID | <HJ6EO-coXM-15@gated-at.bofh.it> |
| In reply to | #81123 |
Running the single test with ext4: # LTP_SINGLE_FS_TYPE=ext4 LTP_DEV_FS_TYPE=ext4 ./preadv03_64 tst_device.c:96: TINFO: Found free device 0 '/dev/loop0' tst_test.c:1690: TINFO: LTP version: 20230929-194-g5c096b2cf tst_test.c:1574: TINFO: Timeout per run is 0h 00m 30s tst_supported_fs_types.c:149: TINFO: WARNING: testing only ext4 tst_supported_fs_types.c:90: TINFO: Kernel supports ext4 tst_supported_fs_types.c:55: TINFO: mkfs.ext4 does exist tst_test.c:1650: TINFO: === Testing on ext4 === tst_test.c:1105: TINFO: Formatting /dev/loop0 with ext4 opts='' extra opts='' mke2fs 1.47.0 (5-Feb-2023) tst_test.c:1119: TINFO: Mounting /dev/loop0 to /tmp/LTP_preWBHd7l/mntpoint fstyp=ext4 flags=0 preadv03.c:102: TINFO: Using block size 512 preadv03.c:77: TFAIL: Buffer wrong at 0 have 62 expected 61 preadv03.c:77: TFAIL: Buffer wrong at 0 have 62 expected 61 preadv03.c:66: TFAIL: preadv(O_DIRECT) read 0 bytes, expected 512 Summary: passed 0 failed 3 broken 0 skipped 0 warnings 0
[toc] | [prev] | [next] | [standalone]
| From | Stephan Verbücheln <verbuecheln@posteo.de> |
|---|---|
| Date | 2023-12-10 09:10 +0100 |
| Subject | Bug#1057843: Guidelines for affected users |
| Message-ID | <HJn2V-czqz-1@gated-at.bofh.it> |
| In reply to | #81123 |
Are there any guidelines for affected users who already updated before they got the warning? Interesting questions for affected users: - Is it safe to assume that other filesystems (like BTRFS) are not affected? - Does this cause filesystem corruption or only file corruption? - Does this affect metadata or only file contents? - Is there a way to detect corrupted files? - If metadata is not affected, is it safe to assume that all files with a modification date older than the update are fine? - Does it help to shut down services (such as Apache) or the whole machine until the fix is available?
[toc] | [prev] | [next] | [standalone]
| From | Umberto Zappi <uzappi@gmail.com> |
|---|---|
| Date | 2023-12-10 11:10 +0100 |
| Subject | Bug#1057843: Guidelines for affected users which use etx4 |
| Message-ID | <HJoV3-cANo-7@gated-at.bofh.it> |
| In reply to | #81123 |
[Multipart message — attachments visible in raw view] — view raw
Are there any guidelines for affected users who already updated before they got the warning? For example, is it fine to start with the previous kernel 6.1.0-13-amd64 (version 6.1.55-1) ? Thanks UmbertoZ.
[toc] | [prev] | [next] | [standalone]
| From | helios.solaris@gmx.ch |
|---|---|
| Date | 2023-12-12 11:40 +0100 |
| Message-ID | <HK8lb-d2EU-1@gated-at.bofh.it> |
| In reply to | #81123 |
Will a file system check detect the corruptions? Can it be done online? Thank you.
[toc] | [prev] | [next] | [standalone]
| From | BW <m40636067@gmail.com> |
|---|---|
| Date | 2023-12-12 13:00 +0100 |
| Message-ID | <HK9AB-d3kv-11@gated-at.bofh.it> |
| In reply to | #81123 |
[Multipart message — attachments visible in raw view] — view raw
Online check of ext4: If your filesystem is located on a logical volume (LVM) then I assume you can make a snapshot and do a check of that. Make SS: lvcreate --snapshot --size 1G --name lv_root_SS --chunksize 4k /dev/VG1/lv_root EXT4 check: e2fsck -f /dev/dm-3 Remove SS: lvremove --yes VG1/lv_root_SS
[toc] | [prev] | [next] | [standalone]
| From | Jamirais Ismail <redmiabiru94@gmail.com> |
|---|---|
| Date | 2023-12-29 14:20 +0100 |
| Subject | Bug#1057843: |
| Message-ID | <HQkWl-gTTc-1@gated-at.bofh.it> |
| In reply to | #81123 |
[Multipart message — attachments visible in raw view] — view raw
Feedback Jamirais Bin Ismail
[toc] | [prev] | [standalone]
Back to top | Article view | linux.debian.kernel
csiph-web