From: tglx@linutronix.de (Thomas Gleixner)
To: linux-mtd@lists.infradead.org
Subject: jffs2 occasionally locking up?
Date: Fri, 14 Feb 2003 10:29:23 +0100 [thread overview]
Message-ID: <200302141029.23689.tglx@linutronix.de> (raw)
In-Reply-To: <0019C845.3E4BC54E@mail.auerswald.de>
On Thursday 13 February 2003 16:18, kai-uwe.bloem at auerswald.de wrote:
> - mount an empty partition as jffs2 on an Intel 28f128K3 flash.
> - copy a large directory tree to it
> - *immediately* overwrite that tree with itself
> - *immediately* copy another large oversized (too big for this partition)
> tree
> Sometimes the last copy doesn't produce a "no space" error message. Rather,
> it does not return for at least half an hour, which is the longest time I
> waited for completion.
> Moreover, if I stop copying by ctrl-c, and try to unmount the partition,
> the unmount locks up as well.
> I have put some code into the cfi driver to observe sector erasing. I
> noticed that after I have interrupted the copy, sectors are still erased
> every other second or such. This keeps going on and on. Looks to me like
> the garbage collector is in a kind of endless loop here.
If you copy too much data to the partition, it tries to garbage collect to
give you more space on the device. The endless loop seems true.
Could you please set JFFS2_DEBUG=1 and provide a log-output.
Don't forget to echo 9 >/proc/sys/kernel/printk before starting your copy
session. Please compress the log and mail it to me in private (will be some
MB) or provide it any location for download
--
Thomas
________________________________________________________________________
linutronix - competence in embedded & realtime linux
http://www.linutronix.de
mail: tglx at linutronix.de
next prev parent reply other threads:[~2003-02-14 9:29 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-02-13 15:18 jffs2 occasionally locking up? kai-uwe.bloem at auerswald.de
2003-02-14 9:29 ` Thomas Gleixner [this message]
[not found] <2702075D4DE2B043BF5EB82E9CFAD45B0BD456@mail1.mediatrix.com>
2003-02-14 13:49 ` 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=200302141029.23689.tglx@linutronix.de \
--to=tglx@linutronix.de \
--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