On 02/12/2014 02:04 PM, Clemens Eisserer wrote:
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, ...).
Ok. good news to me.
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.
What patch? Can you give some additional info? I am running kernel
3.12.2 vanilla.
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.
can you explain better?
Regards,
--
,,,
(o o)
======oOO==(_)==OOo======
Gianluca Renzi
R&D
phone: +39.0542.609120
fax: +39.0542.609212
.oooO Oooo.
======( )==( )=======
\ ( ) /
\_) (_/
===================
| I would like to |
| fix the world, |
| but they're not |
| giving me the |
\ source code! /
---------------
¯\_(".)_/¯
--
To unsubscribe from this list: send the line "unsubscribe linux-nilfs" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
