Hi Gianluca, > What about the wear-leveling of this configuration of the eMMC device?
Actually nilfs2 is by design as friendly to flash devices with a weak controller as possible. It only performs sequential writes, yielding a perfectly equal distribution of writes across the device. Nilfs2 even overwrites static data which won't be written to when using other filesystems - which is great for devices supporting only dynamic wear leveling (usually SD, mmc, emmc, ...). However, there is one issue left - the (two) superblocks are written to periodically in short intervals. There is currently an ongoing discussion about this and Andreas has posted an experimental patch which works well on my raspberry pi. > Can you point me on some tools, utilities to check out this issue? What I did to observe the write-patterns of various file-systems was to create a ram-disk using BUSE: https://github.com/acozzette/BUSE It delivers an example-program which can be modified to log each write-access, which I imported as CSV into LibreOffice for visualization. Regards, Clemens -- To unsubscribe from this list: send the line "unsubscribe linux-nilfs" in the body of a message to [email protected] More majordomo info at http://vger.kernel.org/majordomo-info.html
