From: Richard Weinberger <richard@nod.at>
To: "Мясоедов А.Ю." <myasoedovau@ircoc.vrn.ru>,
linux-mtd@lists.infradead.org
Cc: "David Oberhollenzer (david.oberhollenzer@sigma-star.at)"
<david.oberhollenzer@sigma-star.at>
Subject: Re: How to organize UBI volumes and power crash
Date: Tue, 02 Oct 2018 10:56:23 +0200 [thread overview]
Message-ID: <10059393.qm9dNCvvdv@blindfold> (raw)
In-Reply-To: <5BB331EC.60204@ircoc.vrn.ru>
Am Dienstag, 2. Oktober 2018, 10:53:00 CEST schrieb Мясоедов А.Ю.:
> Thank ypu, Richard.
>
> > Both UBI and UBIFS must not corrupt upon a powercut, if you face such an
> issue, please report. This could be a bug or a hardware problem.
>
> But http://www.linux-mtd.infradead.org/doc/ubifs.html#L_unstable_bits
> says about such possible problems (unstable bits).
This problem is highly theoretical and so far I have never seen it.
So far anyone that claimed to suffer from that was wrong and it turned out that
it was some other issue.
It is time to remove that paragraph from the website since it confuses user
over and over.
David, can you please file and merge a patch?
> > The general recommendation is having the MTD partition and therefore
> the UBI device as large as possible such that the wear leveling large.
> 02.10.2018 11:41, Richard Weinberger написал:
>
> Do you mean one MTD partition for first UBI volume, and second MTD
> partition for another one?
No, just one UBI device on one MTD partition with multiple UBI volumes.
Thanks,
//richard
next prev parent reply other threads:[~2018-10-02 8:56 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-10-02 7:42 How to organize UBI volumes and power crash "Мясоедов А.Ю."
2018-10-02 8:41 ` Richard Weinberger
2018-10-02 8:53 ` "Мясоедов А.Ю."
2018-10-02 8:56 ` Richard Weinberger [this message]
2018-10-02 9:13 ` "Мясоедов А.Ю."
2018-10-02 9:17 ` Richard Weinberger
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=10059393.qm9dNCvvdv@blindfold \
--to=richard@nod.at \
--cc=david.oberhollenzer@sigma-star.at \
--cc=linux-mtd@lists.infradead.org \
--cc=myasoedovau@ircoc.vrn.ru \
/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).