From: "\"Мясоедов А.Ю.\"" <myasoedovau@ircoc.vrn.ru>
To: linux-mtd@lists.infradead.org
Subject: How to organize UBI volumes and power crash
Date: Tue, 02 Oct 2018 10:42:31 +0300 [thread overview]
Message-ID: <5BB32167.1040902@ircoc.vrn.ru> (raw)
I use UBIFS at my device. I'd like 2 UBIFS volumes, first volume for
work purposes, and second volume for logs omly. RootFS is in RAM.
Both volumes are R/W, but the first volume is not intended for permanent
writing. The second volume is intended for permanent writing (logs and
some data tables).
The second volume may be failured in casual power crash. But the first
volume would work.
Will it be safe to have only 1 mfd device, and 2 UBI volume on the mtd
device? Or I must to have 2 separate mtd devices with one UBI volume on
each? The second approach is not suitable because of device tree
modifications when I want to change volume sizes/
--
Andrey
next reply other threads:[~2018-10-02 7:43 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-10-02 7:42 "Мясоедов А.Ю." [this message]
2018-10-02 8:41 ` How to organize UBI volumes and power crash Richard Weinberger
2018-10-02 8:53 ` "Мясоедов А.Ю."
2018-10-02 8:56 ` Richard Weinberger
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=5BB32167.1040902@ircoc.vrn.ru \
--to=myasoedovau@ircoc.vrn.ru \
--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 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).