From: Dave Kleikamp <shaggy@austin.ibm.com>
To: Badari Pulavarty <pbadari@us.ibm.com>
Cc: Andrew Morton <akpm@osdl.org>,
linux-kernel@vger.kernel.org, linux-mm@kvack.org
Subject: Re: 2.6.12-mm1 & 2K lun testing (JFS problem ?)
Date: Wed, 22 Jun 2005 08:50:52 -0500 [thread overview]
Message-ID: <1119448252.9262.12.camel@localhost> (raw)
In-Reply-To: <1119400494.4620.33.camel@dyn9047017102.beaverton.ibm.com>
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
next prev parent reply other threads:[~2005-06-22 13:51 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-06-15 17:36 2.6.12-rc6-mm1 & 2K lun testing Badari Pulavarty
2005-06-15 18:30 ` Nick Piggin
2005-06-15 18:30 ` Badari Pulavarty
2005-06-15 19:02 ` Nick Piggin
2005-06-15 20:56 ` Badari Pulavarty
2005-06-16 1:48 ` Nick Piggin
2005-06-15 23:23 ` Dave Chinner
2005-06-15 21:39 ` Chen, Kenneth W
2005-06-15 22:35 ` Badari Pulavarty
2005-06-16 7:24 ` Andrew Morton
2005-06-16 19:50 ` Badari Pulavarty
2005-06-16 20:37 ` Andrew Morton
2005-06-16 23:43 ` Badari Pulavarty
2005-06-17 0:51 ` Andrew Morton
2005-06-17 15:10 ` Badari Pulavarty
2005-06-17 21:13 ` Andrew Morton
2005-06-22 0:34 ` 2.6.12-mm1 & 2K lun testing (JFS problem ?) Badari Pulavarty
2005-06-22 1:41 ` William Lee Irwin III
2005-06-22 16:23 ` Badari Pulavarty
2005-06-22 13:50 ` Dave Kleikamp [this message]
2005-06-22 16:56 ` Badari Pulavarty
2005-06-22 21:02 ` Badari Pulavarty
2005-06-16 22:42 ` 2.6.12-rc6-mm1 & 2K lun testing William Lee Irwin III
2005-06-16 22:25 ` Badari Pulavarty
2005-06-16 22:58 ` William Lee Irwin III
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=1119448252.9262.12.camel@localhost \
--to=shaggy@austin.ibm.com \
--cc=akpm@osdl.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=pbadari@us.ibm.com \
/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;
as well as URLs for NNTP newsgroup(s).