Re: 2.6.12-mm1 & 2K lun testing (JFS problem ?)

[Badari Pulavarty]

On Wed, 2005-06-22 at 08:50 -0500, Dave Kleikamp wrote:

> > But, I am running into JFS problem. I can't kill my
> > "dd" process.
> 
> Assuming you built the kernel with CONFIG_JFS_STATISTICS, can you send
> me the contents of /proc/fs/jfs/txstats?

Reproduced the problem. Here are the stats..

JFS TxStats
===========
calls to txBegin = 26783
txBegin blocked by sync barrier = 0
txBegin blocked by tlocks low = 0
txBegin blocked by no free tid = 930528
calls to txBeginAnon = 8700659
txBeginAnon blocked by sync barrier = 0
txBeginAnon blocked by tlocks low = 0
calls to txLockAlloc = 50601
tLockAlloc blocked by no free lock = 0


> Looks like txBegin is the problem.  Probably ran out of txBlocks.  Maybe
> a stack trace of jfsCommit, jfsIO, and jfsSync threads might be useful
> too.

I don't see the stacks for these jfs threads in the sysrq-t
output. I wonder why sysrq-t is skipping them. Any Idea ?

elm3b29:/proc/sys/fs # ps -aef | grep -i jfs
root       174     1  0 02:11 ?        00:00:00 [jfsIO]
root       175     1  0 02:11 ?        00:00:01 [jfsCommit]
root       176     1  0 02:11 ?        00:00:01 [jfsCommit]
root       177     1  0 02:11 ?        00:00:02 [jfsCommit]
root       178     1  0 02:11 ?        00:00:02 [jfsCommit]
root       179     1  0 02:11 ?        00:00:00 [jfsSync]
root      7200  7759  0 05:54 pts/1    00:00:00 grep -i jfs

Thanks,
Badari

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