Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

btrfs does not know norecovery since 6.8 #197

Open
jirislaby opened this issue Mar 19, 2024 · 1 comment
Open

btrfs does not know norecovery since 6.8 #197

jirislaby opened this issue Mar 19, 2024 · 1 comment

Comments

@jirislaby
Copy link

NORECOVERY_FS = [:btrfs, :ext3, :ext4, :xfs].freeze

norecovery was deprecated in torvalds/linux@74ef001 (5.9) and finally removed in torvalds/linux@a1912f7 (6.8). Due to that, btrfs cannot be probed by yast now:

btrfs: Unknown parameter norecovery

It used to warn between 5.9 and 6.8:

'nologreplay' is deprecated, use 'rescue=nologreplay' instead

Yast should adopt, but I don't know how to do it in a generic way...

suse-kernel pushed a commit to SUSE/kernel-source that referenced this issue Mar 19, 2024
suse-kernel pushed a commit to SUSE/kernel that referenced this issue Mar 19, 2024
options" (yast/yast-update#197).

suse-commit: d922afa2ed7e029a09447a9cdd3a52de7fa2fef8
@jirislaby
Copy link
Author

Due to inactivity, I created https://bugzilla.suse.com/show_bug.cgi?id=1222429 too.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant