3 ms·
I've used F2FS before and ran into similar problems mentioned. My partition became unusable and fsck.f2fs didn't help. I lost the files, but thankfully had back
by 22c 5y ago
I've used F2FS before and ran into similar problems mentioned. My partition became unusable and fsck.f2fs didn't help. I lost the files, but thankfully had backups.
Since then, I have found that exFAT was better suited to my use case.
This was a few years ago now, I came away from the experience thinking the ideas are nice but it needs more time to mature.
Obviously this is all anecdotal, I've lost partitions to plenty of filesystems before, but the fact that little to no data recovery software existed for F2FS at the time was really the concerning factor.
- supermatou 5y ago> My partition became unusable and fsck.f2fs didn't help. How long ago was that? I read that some distributions were unable to mount/repair f2fs filesystems if they were created with newer f2fs-utils (I infer that the filesystem evolved and their kernel didn't keep up with the developments - but that must have been a long time ago, as f2fs is officially supported in the kernel now, no module necessary)
- 22c 5y ago> I read that some distributions were unable to mount/repair f2fs filesystems if they were created with newer f2fs-utils That was definitely the case. The f2fs-utils on the distro I was using was woefully out of date, but I built the latest from source and still had no luck. Obviously YMMV and I know several prominent phone manufacturers are using F2FS now. I'm not exactly sure when it was but it was probably 3-4 years ago. My use case was a Raspberry Pi, it's possible that Raspbian support was more of a problem than anything. I didn't use it for very long before switching to exFAT, I'm fully open to the possibility that I got particularly unlucky and my issues were no fault of F2FS.