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

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On Tue, 2005-06-21 at 17:34 -0700, Badari Pulavarty wrote:
> Hi Andrew & Shaggy,
> 
> Here is the summary of 2K lun testing on 2.6.12-mm1.
> 
> When I tune dirty ratios and CFQ queue depths, things
> seems to be running fine.
> 
> 	echo 20 > /proc/sys/vm/dirty_ratio
> 	echo 20 > /proc/sys/vm/overcommit_ratio
> 	echo 4 > /sys/block/<device>/queue/nr_requests
> 	
> 
> 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?

> They all get stuck in:
> 
> (I am going to try ext3).
> 
> dd            D 0000000000000000     0 12943      1               12939
> (NOTLB)
> ffff81010612d8f8 0000000000000086 ffff81019677a380 000000000003ffff
>        00000000d5b95298 ffff81010612d918 0000000000000003
> ffff810169f63880
>        00000076d9f1ea00 0000000000000001
> Call Trace:<ffffffff802fb31f>{submit_bio+223} 
> <ffffffff8026a8e1>{txBegin+625}

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.

>        <ffffffff80130540>{default_wake_function+0}
> <ffffffff80130540>{default_wake_function+0}
>        <ffffffff80250a8b>{jfs_commit_inode+155}
> <ffffffff80250daa>{jfs_write_inode+58}
>        <ffffffff801a8857>{__writeback_single_inode+551}
> <ffffffff80250929>{jfs_get_blocks+521}
>        <ffffffff8015dd4c>{find_get_page+92}
> <ffffffff80185555>{__find_get_block_slow+85}
>        <ffffffff801a8e7c>{generic_sync_sb_inodes+524}
> <ffffffff801a91cd>{writeback_inodes+125}
>        <ffffffff80164aa4>{balance_dirty_pages_ratelimited+228}
>        <ffffffff8015eb65>{generic_file_buffered_write+1221}
>        <ffffffff8013b3a5>{current_fs_time+85}
> <ffffffff801a9254>{__mark_inode_dirty+52}
>        <ffffffff8019e4ac>{inode_update_time+188}
> <ffffffff8015effa>{__generic_file_aio_write_nolock+938}
>        <ffffffff8016efa5>{unmap_vmas+965}
> <ffffffff8015f1de>{__generic_file_write_nolock+158}
>        <ffffffff8017149e>{zeromap_page_range+990}
> <ffffffff8014d0c0>{autoremove_wake_function+0}
>        <ffffffff802941b1>{__up_read+33}
> <ffffffff8015f345>{generic_file_write+101}
>        <ffffffff80183b39>{vfs_write+233} <ffffffff80183ce3>{sys_write
> +83}
>        <ffffffff8010dc8e>{system_call+126}
> 

> Thanks,
> Badari

-- 
David Kleikamp
IBM Linux Technology Center

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

[Index of Archives]     [Kernel Newbies]     [Netfilter]     [Bugtraq]     [Photo]     [Stuff]     [Gimp]     [Yosemite News]     [MIPS Linux]     [ARM Linux]     [Linux Security]     [Linux RAID]     [Video 4 Linux]     [Linux for the blind]     [Linux Resources]
  Powered by Linux