From: "Artem B. Bityuckiy" <dedekind@yandex.ru>
To: Konstantin Kletschke <lists@ku-gbr.de>
Cc: linux-mtd@lists.infradead.org
Subject: Re: jffs2 with sync burst mode
Date: Fri, 11 Mar 2005 14:15:35 +0300 [thread overview]
Message-ID: <42317DD7.3090205@yandex.ru> (raw)
In-Reply-To: <20050311104457.GB11203@synertronixx3>
Konstantin Kletschke wrote:
> The "Name CRC failed on node at ..." is away. I populated the root-fs
Good.
> root-fs. No problems. But mounting takes ages :)
How much time does "ages" mean ?
Do you stand that it was faster before?
How large is your flash?
Do you have directories with huge files number in it (say, ~ 10000)?
> Whats next? :D
Profiling might help.
Try to put fewver files to your flash and test how quck is it mounted.
P.S. :
> I erased /dev/mtdblock3 with bootloader and
If you erase your flash with flash_eraseall -j it might work a bit faster.
Q: What's -j ?
A: This means that flash_eraseall ought to write special node called
cleanmarker at the beginning of each block.
Q: Why is this better then to erase using my bootloader?
A: your bootloader probably doesn't write cleanmarkers.
Q: What happens if there are no cleanmarkers?
A: Nothing critical. JFFS2 will just re-erase such blocks and put
cleanmarkers itself. This is just time wasting.
Q: Why does JFFS2 re-erase blocks which have no cleanmarkers but contain
all FF (i.e., are erased)?
A: Because it was observed that if the power loss occurs when block is
almost completely erased, there might be "unstable" bits in it. I.e.,
they are read sometimes as "1" and sometimes as "0" (This effect is
described in David Woodhouse's page). Cleanmarker does guarantee that
the block was successfully erased. All FFs don't.
Q: Does this affect mount time?
A: It might, but I guess not very much. The difference is that if there
is clean marker at the beginning of the block, JFFS2 quickly detects
that it is free. Otherwise, JFFS2 scans it trying to find some data,
thus, wasting time.
P.P.S:
JFFS2 has problems with mount time but it should be noticable when you
work with relatively large partitions, which isn't very typical for NOR.
If you are sure that the problem is not your slow flash driver, you
might try Ferenc's "summary" patch.
--
Best Regards,
Artem B. Bityuckiy,
St.-Petersburg, Russia.
next prev parent reply other threads:[~2005-03-11 11:16 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-03-11 10:44 jffs2 with sync burst mode Konstantin Kletschke
2005-03-11 11:15 ` Artem B. Bityuckiy [this message]
2005-03-11 11:27 ` Konstantin Kletschke
2005-03-11 11:59 ` Artem B. Bityuckiy
2005-03-11 11:57 ` Konstantin Kletschke
-- strict thread matches above, loose matches on Subject: below --
2005-03-09 13:14 Konstantin Kletschke
2005-03-10 13:15 ` Artem B. Bityuckiy
2005-03-10 15:22 ` Konstantin Kletschke
2005-03-10 15:54 ` Artem B. Bityuckiy
2005-03-10 16:40 ` Konstantin Kletschke
2005-03-10 19:25 ` Steve Wahl
2005-03-10 23:24 ` Konstantin Kletschke
2005-03-10 15:46 ` Konstantin Kletschke
2005-03-10 16:21 ` Artem B. Bityuckiy
2005-03-10 16:48 ` Konstantin Kletschke
2005-03-10 17:08 ` Artem B. Bityuckiy
[not found] ` <JPEALJAFNGDDLOPNDIEECEJFDBAA.joakim.tjernlund@lumentis.se>
2005-03-10 23:18 ` Konstantin Kletschke
[not found] ` <BCEFJBPJCGFCNMMMIDBHEEPKCKAA.Joakim.Tjernlund@lumentis.se>
2005-03-11 0:03 ` Konstantin Kletschke
2005-03-10 17:02 ` Konstantin Kletschke
2005-03-10 17:17 ` Artem B. Bityuckiy
2005-03-10 18:27 ` Konstantin Kletschke
2005-03-10 18:53 ` Konstantin Kletschke
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=42317DD7.3090205@yandex.ru \
--to=dedekind@yandex.ru \
--cc=linux-mtd@lists.infradead.org \
--cc=lists@ku-gbr.de \
/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