From: Thomas Gleixner <tglx@linutronix.de>
To: Rudi Engelbertink <rudi@unsec.nl>
Cc: linux-mtd@lists.infradead.org
Subject: Re: jffs2_get_inode_nodes() very very slow
Date: Tue, 01 Feb 2005 17:10:31 +0100 [thread overview]
Message-ID: <1107274232.21196.433.camel@tglx.tec.linutronix.de> (raw)
In-Reply-To: <20050201150810.M93647@unsec.nl>
On Tue, 2005-02-01 at 16:32 +0100, Rudi Engelbertink wrote:
> 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.
Hmm, which kernel version ?
Can you switch on JFFS2 debugging (debuglevel 1), log the output on a
serial line and send me the log, please ?
tglx
prev parent reply other threads:[~2005-02-01 16:11 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-02-01 15:32 jffs2_get_inode_nodes() very very slow Rudi Engelbertink
2005-02-01 16:03 ` 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 [this message]
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=1107274232.21196.433.camel@tglx.tec.linutronix.de \
--to=tglx@linutronix.de \
--cc=linux-mtd@lists.infradead.org \
--cc=rudi@unsec.nl \
/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