Tracking flash IO activity?

[nick]

On 2015-05-18 03:12 PM, Richard Weinberger wrote:
> Am 18.05.2015 um 19:57 schrieb Brian Norris:
>> On Sat, May 16, 2015 at 11:22:52PM +0200, Richard Weinberger wrote:
>>> On Sat, May 16, 2015 at 10:53 PM, Brian Norris
>>> <computersforpeace at gmail.com> wrote:
>>>> I don't know of any similar IO stats for MTDs, sorry.
>>>
>>> I wonder how hard it would be to integrate mtd into our current block IO stats.
>>> It mtd is too low level we could also do it with UBI.
>>
>> I'm not sure if blk-io's iostats would be sufficiently informative for
>> MTD/UBI anyway. Wouldn't we care about at least one extra
>> non-block-device stat: the erase stats?
> 
> This coin has two sides.
> I agree that for MTD we have three interesting counters, read, write and erase
> which would deserve their own tool. Maybe something like mtdtop or mtdstat?
> But it would be nice if well known tools like iostat(1) could work too.
> 
>> Also (and this may be more like what Valent is asking for, though he
>> mentions JFFS2, not UBIFS) is there a readily-available tool for reading
>> the erase counter information from a UBI volume?
> 
> Not really. I have a very hacky tool to inspect UBI Images.
> Mainly to debug fastmap issues. If I find some spare time to
> polish it I'll happily publish it.
> 
> Thanks,
> //richard
> 

Richard,
I feel that not having a tool like this is a very bad idea, it
may be one of the major issues I or others may  have with ubifs 
as a file system choice for flash based systems. You stated that
the tool you have is hacky, does this mean in terms of bugs or 
coding standards? If the tool works and is fairly stable why not
push to the repo for mtd-tools and mark it as experimental for now.
This way the mtd developers can start working on it and allow you
time to do other more important things with your time as a maintainer.
Nick
> ______________________________________________________
> Linux MTD discussion mailing list
> http://lists.infradead.org/mailman/listinfo/linux-mtd/
>