From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S261289AbVFVNvL (ORCPT ); Wed, 22 Jun 2005 09:51:11 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S261291AbVFVNvL (ORCPT ); Wed, 22 Jun 2005 09:51:11 -0400 Received: from e31.co.us.ibm.com ([32.97.110.129]:21902 "EHLO e31.co.us.ibm.com") by vger.kernel.org with ESMTP id S261289AbVFVNu5 (ORCPT ); Wed, 22 Jun 2005 09:50:57 -0400 Subject: Re: 2.6.12-mm1 & 2K lun testing (JFS problem ?) From: Dave Kleikamp To: Badari Pulavarty Cc: Andrew Morton , linux-kernel@vger.kernel.org, linux-mm@kvack.org In-Reply-To: <1119400494.4620.33.camel@dyn9047017102.beaverton.ibm.com> References: <1118856977.4301.406.camel@dyn9047017072.beaverton.ibm.com> <20050616002451.01f7e9ed.akpm@osdl.org> <1118951458.4301.478.camel@dyn9047017072.beaverton.ibm.com> <20050616133730.1924fca3.akpm@osdl.org> <1118965381.4301.488.camel@dyn9047017072.beaverton.ibm.com> <20050616175130.22572451.akpm@osdl.org> <42B2E7D2.9080705@us.ibm.com> <20050617141331.078e5f8f.akpm@osdl.org> <1119400494.4620.33.camel@dyn9047017102.beaverton.ibm.com> Content-Type: text/plain Date: Wed, 22 Jun 2005 08:50:52 -0500 Message-Id: <1119448252.9262.12.camel@localhost> Mime-Version: 1.0 X-Mailer: Evolution 2.2.1.1 Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org 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//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:{submit_bio+223} > {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. > {default_wake_function+0} > {default_wake_function+0} > {jfs_commit_inode+155} > {jfs_write_inode+58} > {__writeback_single_inode+551} > {jfs_get_blocks+521} > {find_get_page+92} > {__find_get_block_slow+85} > {generic_sync_sb_inodes+524} > {writeback_inodes+125} > {balance_dirty_pages_ratelimited+228} > {generic_file_buffered_write+1221} > {current_fs_time+85} > {__mark_inode_dirty+52} > {inode_update_time+188} > {__generic_file_aio_write_nolock+938} > {unmap_vmas+965} > {__generic_file_write_nolock+158} > {zeromap_page_range+990} > {autoremove_wake_function+0} > {__up_read+33} > {generic_file_write+101} > {vfs_write+233} {sys_write > +83} > {system_call+126} > > Thanks, > Badari -- David Kleikamp IBM Linux Technology Center