[f2fs-dev] [Bug 218471] New: F2FS fails to mount rw at boot with "invalid zstd compress level: 6"
Brought to you by:
kjgkr
|
From: <bug...@ke...> - 2024-02-08 09:09:35
|
https://bugzilla.kernel.org/show_bug.cgi?id=218471 Bug ID: 218471 Summary: F2FS fails to mount rw at boot with "invalid zstd compress level: 6" Product: File System Version: 2.5 Hardware: All OS: Linux Status: NEW Severity: high Priority: P3 Component: f2fs Assignee: fil...@ke... Reporter: dh...@pi... Regression: No Using Debian 12.5 "Bookworm" and updated to most-recent stable release kernel "linux-image-6.1.0-18-amd64" which changelog says: linux-signed-amd64 (6.1.76+1) bookworm; urgency=medium * Sign kernel from linux 6.1.76-1 When it boots the f2fs filesystem fails to mount read-write and the boot journal shows: kernel: F2FS-fs (nvme0n1p6): invalid zstd compress level: 6 This is the fstab entry for the corresponding partition: UUID=XXXXXXXXXXX / f2fs compress_algorithm=zstd:6,compress_chksum,atgc,gc_merge,lazytime 0 1 Under the previous kernel the partition correctly mounts and the 'mount' command shows: /dev/nvme0n1p6 on / type f2fs (rw,relatime,lazytime,background_gc=on,gc_merge,discard,no_heap,user_xattr,inline_xattr,acl,inline_data,inline_dentry,flush_merge,extent_cache,mode=adaptive,active_logs=6,alloc_mode=default,checkpoint_merge,fsync_mode=posix,compress_algorithm=zstd:6,compress_log_size=2,compress_chksum,compress_mode=fs,atgc,discard_unit=block,memory=normal) I was able to remount the filesystem read-write with: sudo mount -o remount,rw,relatime,lazytime,background_gc=on,discard,no_heap,user_xattr,inline_xattr,acl,inline_data,inline_dentry,extent_cache,mode=adaptive,active_logs=6,alloc_mode=default,checkpoint_merge,fsync_mode=posix,compress_algorithm=lz4,compress_log_size=2,compress_mode=fs,atgc,discard_unit=block,memory=normal /dev/nvme0n1p6 / and from there was able to update /etc/default/grub to boot the previous kernel: GRUB_DEFAULT="Advanced options for Debian GNU/Linux>Debian GNU/Linux, with Linux 6.1.0-17-amd64" I believe this bug may have been introduced with this patch: https://www.spinics.net/lists/stable-commits/msg329957.html -- You may reply to this email to add a comment. You are receiving this mail because: You are watching the assignee of the bug. |