From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1756626AbZEBS7n (ORCPT ); Sat, 2 May 2009 14:59:43 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1754644AbZEBS7f (ORCPT ); Sat, 2 May 2009 14:59:35 -0400 Received: from mail-bw0-f163.google.com ([209.85.218.163]:55033 "EHLO mail-bw0-f163.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1754141AbZEBS7e convert rfc822-to-8bit (ORCPT ); Sat, 2 May 2009 14:59:34 -0400 DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type:content-transfer-encoding; b=cMOIyYhGDlgMQYabL2GFAhQdnVcAm0gLghe6doQPX1VpBCHwUdfxIzOvs9dtOlbJIn ExXBs/6Fsfty/PAprrWvJlUx0VcersoMG9dL4ks6Zzs0vvdFtQBf3bgGnz85cRQH2et5 NP9z5cRh2/PLxCXNfMjak30oS991Me5f/rRT4= MIME-Version: 1.0 In-Reply-To: <49FC9762.6010109@sandeen.net> References: <20090502101405.GA6145@fancy-poultry.org> <49FC9762.6010109@sandeen.net> Date: Sat, 2 May 2009 22:59:33 +0400 Message-ID: Subject: Re: 2.6.30-rc4: xfs_fsr hangs From: Alexander Beregalov To: Eric Sandeen Cc: linux-kernel@vger.kernel.org, Heinz Diehl , Kernel Testers List , xfs@oss.sgi.com Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8BIT Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org 2009/5/2 Eric Sandeen : > Alexander Beregalov wrote: >> 2009/5/2 Heinz Diehl : >>> On 01.05.2009, Alexander Beregalov wrote: >>> >>>> # xfs_db -r /dev/sdc1 >>>> xfs_db> frag >>>> actual 23805, ideal 22890, fragmentation factor 3.84% >>>> # xfs_fsr -v /dev/sdc1 >>>> /mnt/c start inode=0 >>>> ino=158 >>>> extents before:3 after:1 DONE ino=158 >>>> >>>>  then it hangs >>> I can't confirm this here on my systems: >>> >>> liesel:~ # uname -a >>> Linux liesel 2.6.30-rc4 #1 SMP PREEMPT Sat May 2 11:49:13 CEST 2009 x86_64 x86_64 x86_64 GNU/Linux >> >> I have this problem on two x86_32 hosts. >> It runs for about a minute and then hangs. > > echo w > /proc/sysrq-trigger > dmesg > > would show all the sleeping processes... It is the same as I posted already: SysRq : Show Blocked State task PC stack pid father xfs_fsr D 00000000 5304 3393 1 ef479dec 00000046 00000001 00000000 ef479de8 f2a58000 f2a58280 f3123830 f2a58000 00000001 f3123830 f312382c ffffffff f312382c f2a58000 ef479df4 c0447892 ef479e20 c04498ad ef479e28 f3123830 f3123854 ef479e44 00000246 Call Trace: [] schedule+0x12/0x30 [] rwsem_down_failed_common+0x6d/0x180 [] rwsem_down_write_failed+0x1d/0x30 [] call_rwsem_down_write_failed+0x6/0x8 [] ? xfs_ilock+0xee/0x100 [] ? down_write_nested+0x76/0x90 [] ? xfs_ilock+0xee/0x100 [] xfs_ilock+0xee/0x100 [] xfs_inactive+0x334/0x540 [] ? inotify_inode_is_dead+0x1b/0x80 [] xfs_fs_clear_inode+0x1f/0x30 [] clear_inode+0x8b/0x110 [] generic_delete_inode+0xe6/0x120 [] ? _spin_lock+0x66/0x70 [] generic_drop_inode+0x15f/0x230 [] ? _atomic_dec_and_lock+0x18/0x40 [] iput+0x47/0x50 [] dentry_iput+0x6f/0xc0 [] d_kill+0x24/0x50 [] dput+0x5b/0x120 [] __fput+0x162/0x240 [] fput+0x1f/0x30 [] filp_close+0x47/0x70 [] sys_close+0x6c/0xd0 [] sysenter_do_call+0x12/0x36