From: Artem Bityutskiy <dedekind@infradead.org>
To: Hamish Moffatt <hamish@cloud.net.au>
Cc: linux-mtd@lists.infradead.org
Subject: Re: corrupted ubi after reboot while busy
Date: Fri, 28 Mar 2008 08:21:10 +0200 [thread overview]
Message-ID: <1206685270.3856.44.camel@sauron> (raw)
In-Reply-To: <20080328000551.GA23610@cloud.net.au>
On Fri, 2008-03-28 at 11:05 +1100, Hamish Moffatt wrote:
> On Thu, Mar 27, 2008 at 03:39:38PM +0200, Artem Bityutskiy wrote:
> > On Thu, 2008-03-27 at 18:05 +1100, Hamish Moffatt wrote:
> > > I'm trying UBI for the first time; I have the kernel 2.6.24 with UBI
> > > backported from 2.6.25-rc7.
> > >
> > > I created a static volume (on NAND) and wrote a JFFS2 image to it with
> > > ubiupdatevol. mount succeeded, but the image was built wrongly so the
> > > jffs2 garbage collector thread to fix it.
> > Strange, the volume should be read-only, what could the GC thread do to
> > it?
>
> That's what I thought.
Actually, static volumes are protected by CRC checksums on the UBI
level, so UBI checks CRC of whole volume when you open it for the first
time, which may take time. What is the size of your static volume?
JFFS2 has its own data integrity checksums, so static volumes are not
really necessary. I'd suggest using a dynamic volume instead.
--
Best regards,
Artem Bityutskiy (Битюцкий Артём)
prev parent reply other threads:[~2008-03-28 6:24 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-03-27 7:05 corrupted ubi after reboot while busy Hamish Moffatt
2008-03-27 13:39 ` Artem Bityutskiy
2008-03-28 0:05 ` Hamish Moffatt
2008-03-28 6:21 ` Artem Bityutskiy [this message]
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=1206685270.3856.44.camel@sauron \
--to=dedekind@infradead.org \
--cc=hamish@cloud.net.au \
--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