As the storage of these devices is MicroSD or eMMC, using F2FS for the rootfs would make sense as it is a purpose specific tool for this scope versus the currently used general purpose ext4.
Setting the block size to 4K makes sense to me, but my deeper understanding of flash storage there fails to grasp why set the stride and stripe-width? These are usually set to match up the filesystem to the underlying geometry in a RAID array - is there a parallel of such sorts in flash storage?
If so, how to replicate for F2FS?
mkfs.f2fs -h
F2FS-tools: mkfs.f2fs Ver: 1.4.0 (2014-09-18)
mkfs.f2fs: invalid option -- 'h'
Error: Unknown option ?
Usage: mkfs.f2fs [options] device [sectors]
[options]:
-a heap-based allocation [default:1]
-d debug level [default:0]
-e [extension list] e.g. "mp3,gif,mov"
-l label
-o overprovision ratio [default:5]
-s # of segments per section [default:1]
-z # of sections per zone [default:1]
-t 0: nodiscard, 1: discard [default:1]
sectors: number of sectors. [default: determined by device size]
http://en.wikipedia.org/wiki/F2FS
As the storage of these devices is MicroSD or eMMC, using F2FS for the rootfs would make sense as it is a purpose specific tool for this scope versus the currently used general purpose ext4.
https://github.com/tomuta/debian-mini-odroid-c1/blob/98c04708a35182daedbcf67c66b632b987231318/createimg#L130
Setting the block size to 4K makes sense to me, but my deeper understanding of flash storage there fails to grasp why set the stride and stripe-width? These are usually set to match up the filesystem to the underlying geometry in a RAID array - is there a parallel of such sorts in flash storage?
If so, how to replicate for F2FS?