From: Artem Bityutskiy <dedekind1@gmail.com>
To: Iwo <Iwo.Mergler@netcomm.com.au>
Cc: "linux-mtd@lists.infradead.org" <linux-mtd@lists.infradead.org>
Subject: Re: UBIFS fails to mount on second boot
Date: Wed, 27 Jun 2012 17:10:19 +0300 [thread overview]
Message-ID: <1340806219.3070.23.camel@sauron.fi.intel.com> (raw)
In-Reply-To: <CAEZtdFU1cET8=kViUsR0Oq3q0ckcFLuKsd_Hc5WHo_uhFiKVBw@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1764 bytes --]
Hi,
On Mon, 2012-06-25 at 15:23 +1000, Iwo wrote:
> I'm trying to use a UBIFS partition as the linux root filesystem.
> After flashing the
> UBI image, the system boots successfully and is functional.
>
> On the second boot, however, mounting of the UBIFS fails and the kernel panics.
So this is reproducible? Can you provide me the ubifs image?
> It is possible to avoid the failure by performing a large number of filesystem
> operations (i.e. file system benchmark) during the first session.
Hmm, sounds strange.
> Has anyone seen this before? Suggestions?
Similar issue was reported once and the reported disappeared:
http://lists.infradead.org/pipermail/linux-mtd/2012-June/042046.html
> The hardware is a TI am335x processor with a 256MB, 2K pages, 128K erase block
> NAND flash.
SLC flash?
Did you validate your flash with MTD tests?
> As is all too common, the flash supports sub-pages, the driver does
> not. Thus, I'm
> forcing the VID header offset to 2048.
This means the driver is buggy: it does not support sub-pages but still
reports that it does. Just fix it instead.
> The kernel is a 3.1.0 with TI patches and UBI+UBIFS patches from
> git://git.infradead.org/~dedekind/ubifs-v3.1.git today. I had to change
> IS_ENABLED(DEBUG_FS) to IS_ENABLED(CONFIG_DEBUG_FS)
> to make that compile. The original v3.1.0 UBI/UBIFS code exhibited
> the same behaviour though.
I'll fix the IS_ENABLED stuff, sorry for that.
> The image is generated like so (using the latest MTD tools GIT):
>
> mkfs.ubifs -d staging -F -o root.ubifs -m 0x800 -e 126976 -c 511
Did you try to mount an empty volume and let UBIFS auto-format it, and
then reproduce the issue?
--
Best Regards,
Artem Bityutskiy
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 836 bytes --]
next prev parent reply other threads:[~2012-06-27 14:06 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-06-25 5:23 UBIFS fails to mount on second boot Iwo
2012-06-27 14:10 ` Artem Bityutskiy [this message]
2012-06-29 6:05 ` Iwo Mergler
2012-06-29 13:46 ` Artem Bityutskiy
2012-07-02 7:49 ` Iwo Mergler
2012-07-03 1:16 ` Iwo Mergler
2012-07-14 4:39 ` Artem Bityutskiy
2012-07-18 7:05 ` Iwo Mergler
2012-07-18 7:21 ` Artem Bityutskiy
2012-07-19 1:06 ` Iwo Mergler
2012-07-15 8:25 ` 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=1340806219.3070.23.camel@sauron.fi.intel.com \
--to=dedekind1@gmail.com \
--cc=Iwo.Mergler@netcomm.com.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