From: Dzuy Nguyen <dzuy@infinity-studios.com>
To: linux-mtd@lists.infradead.org
Subject: jffs2: Too few erase blocks (1)
Date: Sun, 08 Feb 2009 23:52:59 -0600 [thread overview]
Message-ID: <498FC4BB.7060903@infinity-studios.com> (raw)
Hello,
I've allocated a small (64K) "user_config" partition in my flash for
persistence storage:
mtd0: 00020000 00010000 "u-boot"
mtd1: 00010000 00010000 "Config"
mtd2: 00100000 00010000 "vmlinux"
mtd3: 002a0000 00010000 "rootfs"
mtd4: 00010000 00010000 "user_config"
mtd5: 00020000 00010000 "ART"
When I tried to mount -t jffs2 /dev/mtdblock4, I get
jffs2: Too few erase blocks (1)
I understand that my erasesize is 64K, which gives me only 1 block,
and jffs2 needs more than 1 block, but the kernel defaults the erasesize
to 64K.
If I made a jffs2 file with eraseblock=8, would this work or would I have
to set it at the kernel?
Dzuy
next reply other threads:[~2009-02-09 5:51 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-02-09 5:52 Dzuy Nguyen [this message]
2009-02-09 8:50 ` jffs2: Too few erase blocks (1) Ricard Wanderlof
2009-02-09 15:39 ` Dzuy Nguyen
2009-02-09 16:32 ` Ricard Wanderlof
2009-02-10 4:16 ` Dzuy Nguyen
2009-02-10 12:41 ` Jamie Lokier
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=498FC4BB.7060903@infinity-studios.com \
--to=dzuy@infinity-studios.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