All of lore.kernel.org
 help / color / mirror / Atom feed
From: Richard Weinberger <richard@nod.at>
To: Martin Townsend <mtownsend1973@gmail.com>,
	Boris Brezillon <boris.brezillon@free-electrons.com>
Cc: Ricard Wanderlof <ricard.wanderlof@axis.com>,
	"linux-mtd@lists.infradead.org" <linux-mtd@lists.infradead.org>
Subject: Re: UBIFS question
Date: Thu, 17 Mar 2016 16:59:07 +0100	[thread overview]
Message-ID: <56EAD44B.3000908@nod.at> (raw)
In-Reply-To: <CABatt_woB8fGT0xK_UkvE73XwX=z5sqX3dwR7j2U4R6-350OGg@mail.gmail.com>

Am 17.03.2016 um 16:39 schrieb Martin Townsend:
>> I guess you're more worried about bitflips than blocks becoming bad
>> (which, AFAIK, can only happen when writing or erasing a block, not
>> when reading it).
>> If bitflips detection/prevention is what your looking for, I guess
>> ubihealthd (developed by Richard) could help.
>>
>> [1]https://lwn.net/Articles/663751/
>> [2]https://lkml.org/lkml/2015/3/29/31
>>
>>
> 
> Looks very promising, thank you for the links.  Bitflip detection is
> definitely something I am looking for.  If I could get some metrics on
> bitflips detected even better :) I will take a closer look.

To clarify, UBI does already bitflip detection and then
"tortures" a block to figure whether it is good or not.
But only upon read. So, if you very seldom read from a
page read disturb may hit you.
This is why I did the ubi-healthd, it allows you to trigger
read of all data (UBI meta and payload) to detect read disturb
soonish.

Thanks,
//richard

  reply	other threads:[~2016-03-17 15:59 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-03-16  9:54 UBIFS question Martin Townsend
2016-03-16 23:12 ` Richard Weinberger
2016-03-17  8:33   ` Martin Townsend
2016-03-17  8:56     ` Richard Weinberger
2016-03-17 11:16       ` Martin Townsend
2016-03-17 11:25         ` Richard Weinberger
2016-03-17 11:43           ` Ricard Wanderlof
2016-03-17 12:54             ` Martin Townsend
2016-03-17 14:55               ` Boris Brezillon
2016-03-17 15:39                 ` Martin Townsend
2016-03-17 15:59                   ` Richard Weinberger [this message]
  -- strict thread matches above, loose matches on Subject: below --
2009-07-10 18:43 UBIFS Question Laurent .
2009-07-10 20:01 ` Corentin Chary
2009-07-11 14:55 ` Artem Bityutskiy
2009-07-14  6:11   ` Laurent .
2009-07-14  7:22     ` Artem Bityutskiy
2009-07-11 15:54 ` Vitaly Wool

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=56EAD44B.3000908@nod.at \
    --to=richard@nod.at \
    --cc=boris.brezillon@free-electrons.com \
    --cc=linux-mtd@lists.infradead.org \
    --cc=mtownsend1973@gmail.com \
    --cc=ricard.wanderlof@axis.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.