public inbox for linux-mtd@lists.infradead.org
 help / color / mirror / Atom feed
From: David Woodhouse <dwmw2@infradead.org>
To: Jeff Smith <jsmith@vhbtech.com>
Cc: linux-mtd@lists.infradead.org
Subject: Re: JFFS2 Problem
Date: Thu, 03 May 2001 22:55:09 +0100	[thread overview]
Message-ID: <17429.988926909@redhat.com> (raw)
In-Reply-To: <3AEDE11C.94AC9A22@vhbtech.com>


jsmith@vhbtech.com said:
>  I'm running jffs2 on a PPC/855T board. I mount the jffs2 and have two
> (2) test scripts that "dd" various sized files to the jffs2 flash. I
> seem to be running into a race condition or something.

> My 2 scripts just "dd" a bunch of files to the jffs2/flash, "ls -l "
> them, "rm *" them and then "ls -l" the dir/mnt point again in a loop.
> I'm running 2 of these and they always reach contention fairly
> quickly, ie. they lock up after 5 to 10 iterations. ps shows the
> processes sleeping. If I remove the "ls"portion of the scripts. That
> is I just "dd" and "rm" - everything "seems" ok.Anybody seen this? 

Sorry for the delayed response.

I've seen similar, and I thought I'd fixed it. You may have found a code 
path which I hadn't considered, and which still has locking problems. Or 
you may just be using the code from before I fixed it :)

What's the output of 'grep Id: fs/jffs2/*.[ch]'?

If it's still happening with the latest code, can you make sure you have 
SysRq enabled in your kernel and show me the backtraces of the offending 
processes? (SysRq-T and ksymoops for decoding)

--
dwmw2

  reply	other threads:[~2001-05-03 21:54 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-04-30 22:03 JFFS2 Problem Jeff Smith
2001-05-03 21:55 ` David Woodhouse [this message]
  -- strict thread matches above, loose matches on Subject: below --
2006-08-10  8:29 JFFS2 problem Amit Kumar Sharma
2006-08-10  9:32 ` Artem B. Bityutskiy
2005-07-19 10:11 jffs2 problem Hinko Kocevar
2005-07-19 10:32 ` Artem B. Bityuckiy
2005-07-19 10:58   ` Hinko Kocevar
2005-07-19 11:05     ` Artem B. Bityuckiy
2005-07-19 11:45       ` Hinko Kocevar
2005-07-19 12:05         ` Artem B. Bityuckiy
2005-07-19 12:09           ` Steven Scholz
2005-07-19 12:21             ` Artem B. Bityuckiy
2005-07-19 12:19           ` Hinko Kocevar
2005-07-19 12:30             ` Hinko Kocevar
2004-06-09  6:57 zhang hao
2004-06-09  9:41 ` David Woodhouse
2004-03-22 16:18 JFFS2 problem Michael Palme
2003-07-30  2:37 Vikram Mehta
2002-07-11 13:29 JFFS2 Problem Frederic Giasson
2002-07-10 21:52 Snehaprabha
2002-07-11  7:05 ` David Woodhouse
2002-07-11 19:18   ` Snehaprabha
2002-07-11 19:32     ` Russ Dill
2001-09-03  8:49 jffs2 problem Wojciech Kromer
2001-03-23  2:02 Douglas S. J. De Couto
2001-03-23  8:37 ` David Woodhouse
2001-03-23 14:25   ` Douglas S. J. De Couto
2001-03-23 14:31     ` David Woodhouse

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=17429.988926909@redhat.com \
    --to=dwmw2@infradead.org \
    --cc=jsmith@vhbtech.com \
    --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