You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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!
The text was updated successfully, but these errors were encountered:
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:
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!
The text was updated successfully, but these errors were encountered: