All of lore.kernel.org
 help / color / mirror / Atom feed
From: Richard Weinberger <richard.weinberger@gmail.com>
To: "Ильяс Гасанов" <torso.nafi@gmail.com>
Cc: "linux-mtd@lists.infradead.org" <linux-mtd@lists.infradead.org>
Subject: Re: ubifs: nand flash wear profiling for userspace application file i/o
Date: Fri, 7 Aug 2015 14:30:56 +0200	[thread overview]
Message-ID: <CAFLxGvxjKVLRQ1Jrjw-hTLq8k1jMTeWVOYwdgHzg=_dQfFsnRg@mail.gmail.com> (raw)
In-Reply-To: <CAEo2pzuPdN56QQbvoao_oo9oppr1CNmBMhq7d0BSGQXraBZYOA@mail.gmail.com>

On Fri, Aug 7, 2015 at 1:47 PM, Ильяс Гасанов <torso.nafi@gmail.com> wrote:
> Hello.
>
> We are developing a GNU/Linux-based appliance, and our customers are
> concerned that the defining application, which runs on it, wears out
> its flash storage too quickly under certain circumstances. The h/w
> supplier guarantees at least 10 000 rewrite cycles for its nand flash
> blocks before wear out.

10000 is not much, is this MLC?

> Is there a suitable method to count (or accurately estimate) the
> distribution of rewrite cycles for ubifs flash blocks during a certain
> period of application work cycle, e. g. for three days? The power is
> not guaranteed to be 100% time on, without a single outage, so it
> would be preferred if persistent data is used, like ubifs journal or
> ubi wear-leveling peb contents, rather than volatile kernelspace
> counters and such.

ubinfo prints the maximum erase counter value, does this help?
This info is also available via /sys/class/ubi/ubi0/max_ec.

If you want the distribution you have to write a small script which
reads the EC header of all blocks.
But as UBI does wear leveling for you, the distribution should not
matter. Please keep in mind that you need to define a sane
WL threshold.

-- 
Thanks,
//richard

  reply	other threads:[~2015-08-07 12:31 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-08-07 11:47 ubifs: nand flash wear profiling for userspace application file i/o Ильяс Гасанов
2015-08-07 12:30 ` Richard Weinberger [this message]
2015-08-07 12:53   ` Michal Suchanek
2015-08-07 12:55   ` Ильяс Гасанов

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to='CAFLxGvxjKVLRQ1Jrjw-hTLq8k1jMTeWVOYwdgHzg=_dQfFsnRg@mail.gmail.com' \
    --to=richard.weinberger@gmail.com \
    --cc=linux-mtd@lists.infradead.org \
    --cc=torso.nafi@gmail.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.