From: Richard Weinberger <richard.weinberger@gmail.com>
To: Boris Brezillon <boris.brezillon@collabora.com>
Cc: Sascha Hauer <s.hauer@pengutronix.de>,
linux-mtd@lists.infradead.org, kernel@pengutronix.de
Subject: Re: Prevent Nand page writes on Power failure
Date: Thu, 21 Feb 2019 13:17:35 +0100 [thread overview]
Message-ID: <CAFLxGvwdFoJCYOeXMHDKgL_Eyd8JtYCNs=Et8qFp5K+991uPjg@mail.gmail.com> (raw)
In-Reply-To: <20190221123709.000aa79d@collabora.com>
On Thu, Feb 21, 2019 at 12:51 PM Boris Brezillon
<boris.brezillon@collabora.com> wrote:
> Other than that, yes, tracking which block was written last so that you
> can move the data somewhere else in case of an unclean detach/unmount
> is an option. Don't know if UBIFS has this information (UBI doesn't,
> that's for sure).
Yes, neither UBI nor UBIFS have this information.
With reasonable effort we might compute this information using the
seqeuence numbers.
--
Thanks,
//richard
______________________________________________________
Linux MTD discussion mailing list
http://lists.infradead.org/mailman/listinfo/linux-mtd/
next prev parent reply other threads:[~2019-02-21 12:17 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-02-20 13:58 Prevent Nand page writes on Power failure Sascha Hauer
2019-02-21 0:05 ` Richard Weinberger
2019-02-21 8:39 ` Sascha Hauer
2019-02-21 9:28 ` Richard Weinberger
2019-02-21 8:10 ` Boris Brezillon
2019-02-21 10:17 ` Sascha Hauer
2019-02-21 10:36 ` Boris Brezillon
2019-02-21 11:21 ` Sascha Hauer
2019-02-21 11:37 ` Boris Brezillon
2019-02-21 12:17 ` Richard Weinberger [this message]
2019-02-21 13:27 ` Sascha Hauer
2019-02-25 8:56 ` Sascha Hauer
2019-02-25 11:28 ` Richard Weinberger
2019-02-26 9:10 ` Sascha Hauer
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='CAFLxGvwdFoJCYOeXMHDKgL_Eyd8JtYCNs=Et8qFp5K+991uPjg@mail.gmail.com' \
--to=richard.weinberger@gmail.com \
--cc=boris.brezillon@collabora.com \
--cc=kernel@pengutronix.de \
--cc=linux-mtd@lists.infradead.org \
--cc=s.hauer@pengutronix.de \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).