Date: Wed, 7 Apr 2004 04:21:29 +0200
From: Han Boetes <han@mijncomputer.nl>
To: linux-kernel@vger.kernel.org
Subject: With recent kernels find gets stuck at nothing.
Message-ID: <20040407022151.GA8445@boetes.org>
Mail-Followup-To: linux-kernel@vger.kernel.org
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
User-Agent: Mutt/1.5.6i
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 1183
Lines: 31

Hi,

To debug why the locate cronjob got stuck I tracked down is going on:

So I run this little script:

#!/bin/sh
find / ! \( -fstype jfs -or -fstype reiserfs -or -fstype ext2 -or -fstype ext3 -or -fstype afs -or -fstype xfs \) -prune -or -path /tmp -prune -or -path /var/tmp -prune -or -path /var/spool -prune -or -path /usr/tmp -prune -or -path /mnt -prune -or -print

Now the odd thing happens quite frequently: It's gets stuck just in the
middle of some directory. When this happens I can not start any new
applications. It stays this way until I go to the firebird window which
gets itself back from swap memory (it seems) and then the find command
continues.

I run kernel-2.6.5 with jfs as filesystem and I do not use
preempting. I have an athlon 1700+ and 256mb memory.


I hope this is sufficient information to be able to repeat this
problem. Otherwise please let me know what additional information you
want to know.


# Han
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/