can't convert ext4 to f2fs #120
Comments
|
any logs？ |
|
sorry for before i not send log |
|
product:[1023970458] F2FS-tools: mkfs.f2fs Ver: 1.16.0 (2023-04-11) Info: Disable heap-based policy [FIX] (move_one_curseg_info:2858) --> Move curseg[1] 121 -> 17a after 1600 [FIX] (move_one_curseg_info:2858) --> Move curseg[2] 90 -> 121 after 1600 [FIX] (move_one_curseg_info:2858) --> Move curseg[3] 0 -> 5 after 1600 [FIX] (move_one_curseg_info:2858) --> Move curseg[4] 1 -> a after 1600 [FIX] (move_one_curseg_info:2858) --> Move curseg[5] 2 -> 1 after 1600 Info: Write valid nat_bits in checkpoint [FSCK] Max image size: 778 MB, Free space: 124 MB Done: 0.000000 secs i will set 1987362816bytes but file generated product.img 1242682597 |
|
i flashed and normally but size not same :) |
|
yep, bcz we dont know how to calc size for f2fs image. |
Here's how you can approach the size calculation: Estimate the amount of data that should be in the /product section. These can be system applications, libraries, resources, etc. Look at the size of the /product folder in your current system or in the source files that you are going to package. Add a margin. F2FS requires some space for metadata and for efficient operation (for example, for garbage collection). It is recommended to add at least 10-20% of the stock to the estimated amount of data. If you expect the data in /product to grow over time, add more stock. Round the size to a multiple of megabytes (MB) or gigabytes (GB). This will simplify the size management and make them more understandable. Calculation example: Let's say you estimated that the data in /product takes up about 1 GB (1024 MB). 20% margin: 1024 MB * 0.20 = 204.8 MB (rounded up to 205 MB) Total size: 1024 MB + 205 MB = 1229 MB Round it up to 1250 MB or 1.25 GB. In this case, you can try to set the size to 1250 MB (1250 * 1024 * 1024 bytes) when creating the F2FS image. |
hello can you convert ext4 to f2fs
The text was updated successfully, but these errors were encountered: