From: Peter Menzebach <pm-mtd@mw-itcon.de>
To: "Artem B. Bityutskiy" <dedekind@yandex.ru>
Cc: Linux MTD <linux-mtd@lists.infradead.org>
Subject: Re: data loss on jffs2 filesystem on dataflash
Date: Tue, 20 Sep 2005 15:38:32 +0200 [thread overview]
Message-ID: <433010D8.7000209@mw-itcon.de> (raw)
In-Reply-To: <43300C08.80005@yandex.ru>
Artem B. Bityutskiy wrote:
>> Artem B. Bityutskiy wrote:
>> I glanced at the manual. Uhh, DataFlash is very specific beast. It
>> suppoers page program with built-in erase command... So DataFlash
>> effectively may be considered as a block device. Then you may use any
>> FS on it providing you have wrote proper driver? Why do you need JFFS2
>> then :-) ?
I do need some wear leveling (and a filesystem which supports block
sizes of 1056 bytes ;) )
>> JFFS2 orients to "classical" flashes. They have no "write page with
>> built-in erase" operation.
>>
>> Didn't read the manual carefully, what do they refer by "Main memory
>> array"?
The main memory array is the flash itself with pages of 1056 bytes
>> BTW, having 8*1056 write buffer is not perfect ides, better make it as
>> small as possible, i.e., 1056 bytes.
At the moment, the write buffer = reported erase block size. Is this
neccessary that this is equal?
my reasons for setting erase block size to 8(16)*1056:
1. my lazyness -> I have to patch the mkfs.jff2 every time, since it
makes a guess, that -e 1056 is not a very good idea (at lest the
versions some times ago)
2. It seemed to me, that jffs2 boots faster, if the number of blocks is
smaller.
3. A guess without proof: jffs2 likes blocks which are not too small
Best regards
Peter
--
Peter Menzebach
Menzebach und Wolff IT-Consulting GbR
Phone +49 751 355 387 1
next prev parent reply other threads:[~2005-09-20 13:39 UTC|newest]
Thread overview: 51+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-09-14 12:09 data loss on jffs2 filesystem on dataflash Peter Menzebach
2005-09-14 12:30 ` Artem B. Bityuckiy
2005-09-14 13:43 ` Peter Menzebach
2005-09-15 7:48 ` Artem B. Bityuckiy
2005-09-15 7:39 ` Peter Menzebach
2005-09-15 7:49 ` Artem B. Bityuckiy
2005-09-15 7:53 ` Artem B. Bityuckiy
[not found] ` <43292AC6.40809@mw-itcon.de>
[not found] ` <43292E16.70401@yandex.ru>
[not found] ` <43292F91.9010302@mw-itcon.de>
2005-09-20 10:18 ` Artem B. Bityutskiy
[not found] ` <432FEF55.5090700@mw-itcon.de>
2005-09-20 11:21 ` Artem B. Bityutskiy
2005-09-20 13:16 ` Artem B. Bityutskiy
[not found] ` <433006D8.4010502@yandex.ru>
2005-09-20 13:18 ` Artem B. Bityutskiy
2005-09-20 13:38 ` Peter Menzebach [this message]
2005-09-20 14:18 ` Artem B. Bityutskiy
2005-09-20 15:01 ` Peter Menzebach
2005-09-20 15:11 ` Andrew Victor
2005-09-20 15:22 ` Jörn Engel
2005-09-20 16:31 ` Artem B. Bityutskiy
2005-09-21 7:21 ` Andrew Victor
2005-09-21 9:25 ` Artem B. Bityutskiy
2005-09-21 10:27 ` Peter Menzebach
2005-09-21 13:36 ` Artem B. Bityutskiy
2005-09-21 13:41 ` Artem B. Bityutskiy
2005-09-21 15:44 ` Peter Menzebach
2005-09-21 15:59 ` Artem B. Bityutskiy
2005-09-21 16:10 ` Peter Menzebach
2005-09-21 16:19 ` Artem B. Bityutskiy
2005-09-21 17:10 ` Peter Menzebach
2005-09-22 10:38 ` Peter Menzebach
2005-09-22 10:51 ` Artem B. Bityutskiy
2005-09-20 15:11 ` Artem B. Bityutskiy
2005-09-20 15:45 ` Peter Menzebach
[not found] ` <20050920133244.GC4634@wohnheim.fh-wedel.de>
[not found] ` <43301877.3040306@yandex.ru>
2005-09-20 14:36 ` Jörn Engel
2005-09-20 14:48 ` Artem B. Bityutskiy
2005-09-15 8:02 ` Artem B. Bityuckiy
[not found] ` <43292E94.4020702@mw-itcon.de>
2005-09-15 8:26 ` Artem B. Bityuckiy
2005-09-15 8:33 ` Peter Menzebach
2005-09-15 8:47 ` Artem B. Bityuckiy
2005-09-15 9:14 ` Peter Menzebach
2005-09-15 9:25 ` Artem B. Bityuckiy
2005-09-21 13:55 ` Peter Menzebach
2005-09-21 13:59 ` Artem B. Bityutskiy
2005-09-15 10:32 ` Artem B. Bityuckiy
2005-09-22 12:30 ` Peter Menzebach
2005-09-22 12:44 ` Artem B. Bityutskiy
2005-09-22 13:31 ` Peter Menzebach
2005-09-22 14:06 ` Artem B. Bityutskiy
2005-09-22 14:32 ` Andrew Victor
2005-09-22 14:45 ` Artem B. Bityutskiy
2005-09-22 14:59 ` Peter Menzebach
2005-09-22 16:14 ` Peter Menzebach
2005-09-22 17:09 ` Peter Menzebach
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=433010D8.7000209@mw-itcon.de \
--to=pm-mtd@mw-itcon.de \
--cc=dedekind@yandex.ru \
--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