From: Cam Mayor <cmayor@iders.ca>
To: a-linux-mtd <linux-mtd@lists.infradead.org>
Subject: mtd filesystem across different sector sizes in the same part
Date: Mon, 6 Oct 2003 14:33:16 -0500 [thread overview]
Message-ID: <03100614331605.30787@kilauea.iders.ca> (raw)
After doing a flash storage map for one of our devices and based on reading a
recent question to this list, i thought of another question.
In my flash part (intel 28f320c3) there are 8 x 8kB blocks and 63 x 64 kB
blocks. I believe that [1] MTD can span the two block sizes effectively for
it to be recognized as a single MTD device. JFFS2, IIRC, uses 5 flash blocks
for flash filesystem overhead. Do those blocks have to be any specific size
relative to the rest of the filesystem blocks? Will it use the first five
blocks, or does it move around for wear levelling? Will JFFS2 get confused
by different block sizes, or is that already handled in the MTD layer?
If the 5 blocks move around, is there any way to predict how much space will
be available in the filesystem? (eg. one moment you have 5 overhead blocks
in the 8kB area and have 70kB free. the next moment you have 4 overhead
blocks in the 8kB area, and one in the 64kB area, leaving you with 14kB free
space)
thanks,
cam
[1] please correct me if i'm wrong
--
Cameron Mayor
Iders Incorporated
next reply other threads:[~2003-10-06 19:33 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-10-06 19:33 Cam Mayor [this message]
2003-10-06 19:36 ` mtd filesystem across different sector sizes in the same part David Woodhouse
2003-10-06 20:45 ` Cam Mayor
2003-10-06 21:08 ` David Woodhouse
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=03100614331605.30787@kilauea.iders.ca \
--to=cmayor@iders.ca \
--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