All of lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla-daemon@kernel.org
To: linux-f2fs-devel@lists.sourceforge.net
Subject: [f2fs-dev] [Bug 218471] F2FS fails to mount rw at boot with "invalid zstd compress level: 6"
Date: Tue, 13 Feb 2024 13:52:56 +0000	[thread overview]
Message-ID: <bug-218471-202145-5G1dVugPci@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-218471-202145@https.bugzilla.kernel.org/>

https://bugzilla.kernel.org/show_bug.cgi?id=218471

Chao Yu (chao@kernel.org) changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |chao@kernel.org

--- Comment #4 from Chao Yu (chao@kernel.org) ---
(In reply to Dhya Pacifica from comment #0)
> 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

Can you please try below fixes:

[PATCH 6.1] f2fs: add helper to check compression level
https://lore.kernel.org/linux-f2fs-devel/20240212160530.1017205-1-chao@kernel.org/T/#u

[PATCH] f2fs: compress: fix to check zstd compress level correctly in mount
option
https://lore.kernel.org/linux-f2fs-devel/20240212160818.1020903-1-chao@kernel.org/T/#u

-- 
You may reply to this email to add a comment.

You are receiving this mail because:
You are watching the assignee of the bug.

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

      parent reply	other threads:[~2024-02-13 13:53 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-02-08  9:09 [f2fs-dev] [Bug 218471] New: F2FS fails to mount rw at boot with "invalid zstd compress level: 6" bugzilla-daemon
2024-02-08  9:11 ` [f2fs-dev] [Bug 218471] " bugzilla-daemon
2024-02-08 16:41 ` bugzilla-daemon
2024-02-08 20:58 ` bugzilla-daemon
2024-02-09  1:42 ` bugzilla-daemon
2024-02-13 13:52 ` bugzilla-daemon [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=bug-218471-202145-5G1dVugPci@https.bugzilla.kernel.org/ \
    --to=bugzilla-daemon@kernel.org \
    --cc=linux-f2fs-devel@lists.sourceforge.net \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.