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

A question about F2FS on RAIZN #5

Open
NeverMore2744 opened this issue Nov 8, 2023 · 0 comments
Open

A question about F2FS on RAIZN #5

NeverMore2744 opened this issue Nov 8, 2023 · 0 comments

Comments

@NeverMore2744
Copy link

Hi, I am deploying RAIZN on ZN540 which has 1077MiB zone capacity and 2GiB zone sizes. I want to call mkfs.f2fs on RAIZN, but it says that the command has been killed by SIGKILL signal:

$ sudo mkfs.f2fs /dev/mapper/my_raizn -f
F2FS-tools: mkfs.f2fs Ver: 1.14.0 (2020-08-24)

Info: Disable heap-based policy
Info: Debug level = 0
Info: Trim is enabled
fish: Job 1, 'sudo mkfs.f2fs /dev/mapper/my_r…' terminated by signal SIGKILL (Forced quit)

Will it be related to the zone size larger than 2GiB? In the paper, the authors mentioned that they "modified the Linux kernel 5.15 and mkfs.f2fs to remove hard-coded constraints that prevent the creation of (logical) devices with zone sizes larger than 2 GB". But currently I have no idea whether the problem is related, and whether it is easy to modify that.

Looking forward to your reply!

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