All of lore.kernel.org
 help / color / mirror / Atom feed
From: Richard Weinberger <richard.weinberger@gmail.com>
To: Stelling Carsten <Carsten.Stelling@goerlitz.com>
Cc: "linux-mtd@lists.infradead.org" <linux-mtd@lists.infradead.org>
Subject: Re: UBI bitrot checking and scrubbing
Date: Tue, 27 Jun 2017 13:39:57 +0200	[thread overview]
Message-ID: <CAFLxGvwa9psUt-Xy2R5Whwc+oF46USdMDekKqGWPEavb4d4DCg@mail.gmail.com> (raw)
In-Reply-To: <AE0F02A50174E945B94BE6AC0B7199D81A593D0E@GOEMAIL-Server2.goerlitz.int>

Carsten,

On Tue, Jun 27, 2017 at 12:59 PM, Stelling Carsten
<Carsten.Stelling@goerlitz.com> wrote:
> Hi,
>
> I found Richard’s patches http://lists.infradead.org/pipermail/linux-mtd/2015-April/058677.html or
> http://lists.infradead.org/pipermail/linux-mtd/2015-November/063122.html, but can't identify any
> of the code in newer kernel versions (e.g. 4.9 or 4.11).
> I wonder, if ubihealthd http://lists.infradead.org/pipermail/linux-mtd/2015-November/063128.html
> was never released with mtd-utils (actually 1.5.2). Possibly, I have missed some information on
> this topic.
> Is there actually a comparable mechanism in UBI, I haven’t found yet?
> Like wear levelling, reading and scrubbing (if necessary) *all* PEB’s from time to time is an
> essential task to ensure durability of information. Especially, for PEB’s which are not accessed
> frequently. With Fastmap enabled, one can't rely on cyclic reboots, because not all UBI
> VID/EC headers are read at boot time.
> Regarding bitrot checking, a lot of effort was made by several contributors, but I can't find
> their work in mainline kernel driver code. Have I overlooked something?
> Any hints or suggestions are greatly appreciated.

Since the MLC topic kind of faded away I had no chance to work on the
bitrot stuff.
But you are right we should revive ubihealthd and the needed kernel
interface because for Fastmap
this is a topic.

Would you volunteer to forward port the patches?

-- 
Thanks,
//richard

  reply	other threads:[~2017-06-27 11:40 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-06-27 10:59 UBI bitrot checking and scrubbing Stelling Carsten
2017-06-27 11:39 ` Richard Weinberger [this message]
2017-06-27 13:36   ` AW: " Stelling Carsten
2017-06-27 13:40     ` Richard Weinberger
2017-06-27 14:49       ` AW: " Stelling Carsten

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=CAFLxGvwa9psUt-Xy2R5Whwc+oF46USdMDekKqGWPEavb4d4DCg@mail.gmail.com \
    --to=richard.weinberger@gmail.com \
    --cc=Carsten.Stelling@goerlitz.com \
    --cc=linux-mtd@lists.infradead.org \
    /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.