On Sat, Dec 18, 2004 at 02:47:27PM -0600, Jon Nelson wrote: > > > On Sat, 18 Dec 2004, Jon Nelson wrote: > > >On Sat, 18 Dec 2004, Sonny Rao wrote: > ... > >>>Well, I'm not really sure what I'm looking for, but I did this: > >>> > >>>fstest -n 50 -f 10000 -s 2048 > >>> > >>>Then, in another terminal, I ran this > >>> > >>>find . | wc -l > > Boom! disk light goes out, can't do ANYTHING with that filesystem, > instantly. > > >>>I got fstest (I'm pretty sure mine is old) at: > >>> > >>>http://samba.org/ftp/unpacked/junkcode/ > > Also, from slabtop at the current moment: > > 10696 10695 99% 0.81K 2674 4 10696K jfs_ip > > In this order: the contents of the files after boot, after cleaning the > FS (due to the hanging), and then just a few seconds after it's hung (I > can hang it almost instantly, 100% reproduceable). <snip>
Hmm, okay I had thought it might be caused by a lack of available transaction blocks or locks, but that doesn't seem to be the case based on the data you provided. I am able to reproduce the problem on a laptop I have with me as well, I'm running a 2.6.8.1 kernel. It looks like all of the processes are stuck waiting on a semaphore somewhere in namei (.text.lock.namei) and upon reboot i have a bit of filesystem corruption. Shaggy will have to look into this some more, thanks for the report. Sonny _______________________________________________ Jfs-discussion mailing list [EMAIL PROTECTED] http://www-124.ibm.com/developerworks/oss/mailman/listinfo/jfs-discussion
