From: "Rudi Engelbertink" <rudi@unsec.nl>
To: linux-mtd@lists.infradead.org
Subject: jffs2_get_inode_nodes() very very slow
Date: Tue, 1 Feb 2005 16:32:23 +0100 [thread overview]
Message-ID: <20050201150810.M93647@unsec.nl> (raw)
Hello,
On a 64 MiB NAND Flash I created a jffs2 file system. After several tests
especially power fail tests resulting in a lot off CRC and Data CRC errors.
This appears not to be a problem except it takes a very long time to check
the file system.
The initial check (scanning for erased blocks) is done in aproximatly 10
seconds, but after that the jffs2_get_inode_nodes check is running.
This process takes up to 8 minutes.
During this time the file-system is inaccessible which in oure case a
watchdog decides to reboot the system, making it even worse.
It appears that the check is done with a stepsize of 16 bytes. On an 64MiB
NAND flash it does this check +/- 4 million times.
Is there a way to reduce the time to check the file-system and/or how
can I recover from these errors.
Kind Regards,
Rudi.
--
They that can give up essential liberty to obtain a little temporary
safety deserve neither liberty nor safety.
Benjamin Franklin (1706-1790), Letter to Josiah Quincy, Sept. 11, 1773.
GnuPG Key fingerprint = 706C E2AC 7AE2 BCEE 04EB A962 0A75 7F9B 07A1 83E8
next reply other threads:[~2005-02-01 15:32 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-02-01 15:32 Rudi Engelbertink [this message]
2005-02-01 16:03 ` jffs2_get_inode_nodes() very very slow Artem B. Bityuckiy
2005-02-02 9:05 ` Rudi Engelbertink
2005-02-02 10:26 ` Thomas Gleixner
2005-02-02 10:35 ` David Woodhouse
2005-02-02 11:23 ` Artem B. Bityuckiy
2005-02-02 12:26 ` Rudi Engelbertink
2005-02-02 12:41 ` Thomas Gleixner
2005-02-01 16:10 ` Thomas Gleixner
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=20050201150810.M93647@unsec.nl \
--to=rudi@unsec.nl \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.