public inbox for linux-mtd@lists.infradead.org
 help / color / mirror / Atom feed
From: Artem Bityutskiy <dedekind1@gmail.com>
To: Ricard Wanderlof <ricard.wanderlof@axis.com>
Cc: "Ricard Wanderlöf" <ricardw@axis.com>,
	"linux-mtd@lists.infradead.org" <linux-mtd@lists.infradead.org>
Subject: Re: Static UBI volumes and ubiupdatevol ?
Date: Fri, 17 Dec 2010 14:26:57 +0200	[thread overview]
Message-ID: <1292588817.2412.7.camel@localhost> (raw)
In-Reply-To: <Pine.LNX.4.64.1012170946190.7024@lnxricardw.se.axis.com>

On Fri, 2010-12-17 at 10:33 +0100, Ricard Wanderlof wrote:
> > The same with UBIFS - we never write when we are mounted R/O. There are
> > many ubifs_assert()s to check this as well.
> 
> ... but UBI might still do writes during the course of scrubbing I guess, 
> unless ...

Yes, you are right.

> > >  so it is possible to use a 
> > > simple checksum to verify data integrity.
> > 
> > You can do this with UBIFS I think, did not try though.
> 
> What I meant was 'a simple checksum on the raw mtd partition', which can't 
> work with UBIFS as the UBI erase counters etc can change over time as a 
> result of scrubbing.

Ah, yes, you see, you know the things quite well yourself :-)

> I guess I could read from the /dev/ubix_y device to just get the raw UBIFS 
> data which shouldn't change even in the event of scrubbing? Or should I 
> use gluebi to get both a raw mtd partition corresponding to the raw UBIFS 
> data, as well as using UBIFS (on /dev/ubix_y) for the file system?

No, gluebi is not needed, it would just give you an /dev/mtdZ device
with contents equivalent to /dev/ubiX_Y

-- 
Best Regards,
Artem Bityutskiy (Артём Битюцкий)

  reply	other threads:[~2010-12-17 12:27 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-12-15  8:06 Static UBI volumes and ubiupdatevol ? Ricard Wanderlof
2010-12-15 10:43 ` Ricard Wanderlof
2010-12-16 16:26   ` Artem Bityutskiy
2010-12-17  9:39     ` Ricard Wanderlof
2010-12-17 13:04       ` Artem Bityutskiy
2010-12-17 15:02         ` Ricard Wanderlof
2010-12-17 17:05           ` Artem Bityutskiy
2010-12-29 20:26           ` Russ Dill
2010-12-16 16:19 ` Artem Bityutskiy
2010-12-17  9:33   ` Ricard Wanderlof
2010-12-17 12:26     ` Artem Bityutskiy [this message]
2010-12-17 12:31       ` Ricard Wanderlof
2010-12-17 12:40         ` Artem Bityutskiy

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=1292588817.2412.7.camel@localhost \
    --to=dedekind1@gmail.com \
    --cc=linux-mtd@lists.infradead.org \
    --cc=ricard.wanderlof@axis.com \
    --cc=ricardw@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox