From: Philby John <pjohn@mvista.com>
To: dedekind1@gmail.com
Cc: linux-mtd@lists.infradead.org
Subject: Re: UBIFS mount failure on NOR flash
Date: Tue, 15 Jun 2010 19:35:07 +0530 [thread overview]
Message-ID: <4C178893.9010204@mvista.com> (raw)
In-Reply-To: <1276609047.19028.270.camel@localhost>
On 06/15/2010 07:07 PM, Artem Bityutskiy wrote:
> On Tue, 2010-06-15 at 18:29 +0530, Philby John wrote:
>> Hello,
>>
>> Platform: Cavium CN5020
>> Filesystem: UBIFS
>> Flash Type: NOR
>> Flash Size: 8MB
>> Partition Details Kernel Log:
>> Creating 2 MTD partitions on "phys_mapped_flash":
>> 0x000000000000-0x000000700000 : "Octeon BOOT partition"
>> 0x000000700000-0x000000800000 : "Octeon test partition"
>>
>>
>> $mount -t ubifs ubi1:test /mnt/nor
>> UBIFS error (pid 851): init_constants_early: too few LEBs (12), min. is 17
>> mount: wrong fs type, bad option, bad superblock on ubi1:test,
>> missing codepage or helper program, or other error
>> (for several filesystems (e.g. nfs, cifs) you might
>> need a /sbin/mount.<type> helper program)
>> In some cases useful info is found in syslog - try
>> dmesg | tail or so
>>
>>
>> But JFFS2 is able to mount the same partition flawlessly. Shouldn't
>> UBIFS be able to do the same? What I would like to know is, is this the
>> expected behavior or a bug? If its a bug I would like to look into it.
>
> Yes, this is expected. For such a tiny flash partition you should rather
> use JFFS2. I've just created a FAQ entry for you:
>
> http://www.linux-mtd.infradead.org/faq/ubifs.html#L_few_lebs
>
Okay, thanks for the clarification.
Regards,
Philby
prev parent reply other threads:[~2010-06-15 14:04 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-06-15 12:59 UBIFS mount failure on NOR flash Philby John
2010-06-15 13:37 ` Artem Bityutskiy
2010-06-15 14:05 ` Philby John [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=4C178893.9010204@mvista.com \
--to=pjohn@mvista.com \
--cc=dedekind1@gmail.com \
--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).