Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S933101AbXAWSVr (ORCPT ); Tue, 23 Jan 2007 13:21:47 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S933102AbXAWSVr (ORCPT ); Tue, 23 Jan 2007 13:21:47 -0500 Received: from smtp24.orange.fr ([193.252.22.28]:18982 "EHLO smtp24.orange.fr" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S933101AbXAWSVq (ORCPT ); Tue, 23 Jan 2007 13:21:46 -0500 X-ME-UUID: 20070123182143589.8FEB61C0009A@mwinf2403.orange.fr Message-ID: <45B65234.4000203@free.fr> Date: Tue, 23 Jan 2007 19:21:40 +0100 From: Laurent Riffard User-Agent: Mozilla/5.0 (X11; U; Linux i686; fr-FR; rv:1.8.0.7) Gecko/20060405 SeaMonkey/1.0.5 MIME-Version: 1.0 To: Jens Axboe Cc: "Vladimir V. Saveliev" , reiserfs-list@namesys.com, Kernel development list Subject: Re: 2.6.20-rc3-mm1: umount reiser4 FS stuck in D state References: <20070104220200.ae4e9a46.akpm@osdl.org> <200701062158.06329.vs@namesys.com> <45A81231.6040104@free.fr> <200701231940.58053.vs@namesys.com> <20070123154617.GE11995@kernel.dk> In-Reply-To: <20070123154617.GE11995@kernel.dk> X-Enigmail-Version: 0.94.0.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 8bit Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 3611 Lines: 88 Le 23.01.2007 16:46, Jens Axboe a ?crit : > On Tue, Jan 23 2007, Vladimir V. Saveliev wrote: >> Hello >> >> On Saturday 13 January 2007 01:56, Laurent Riffard wrote: >>> Le 06.01.2007 19:58, Vladimir V. Saveliev a ?crit : >>>> Hello >>>> >>>> On Saturday 06 January 2007 13:58, Laurent Riffard wrote: >>>>> Hello, >>>>> >>>>> got this with 2.6.20-rc3-mm1: >>>>> >>>>> ======================= >>>>> SysRq : Show Blocked State >>>>> >>>>> free sibling >>>>> task PC stack pid father child younger older >>>>> umount D C013135E 6044 1168 1150 (NOTLB) >>>>> de591ae4 00000086 de591abc c013135e dff979c8 c012a6fe 00000046 00000007 >>>>> dfd94ac0 128d3000 00000026 00000000 dfd94bcc dff979c8 de591ae4 dffda038 >>>>> 00000002 dff979c0 dff979bc dff979c8 de591b10 c012d600 dff979f8 00000000 >>>>> Call Trace: >>>>> [] synchronize_qrcu+0x70/0x8c >>>>> [] __make_request+0x4c/0x29b >>>>> [] generic_make_request+0x1b0/0x1de >>>>> [] submit_bio+0xda/0xe2 >>>>> [] write_jnodes_to_disk_extent+0x920/0x974 [reiser4] >>>>> [] update_journal_footer+0x29f/0x2b7 [reiser4] >>>>> [] write_tx_back+0x149/0x185 [reiser4] >>>>> [] reiser4_write_logs+0xea4/0xfd2 [reiser4] >>>>> [] try_commit_txnh+0x7e6/0xa4f [reiser4] >>>>> [] reiser4_txn_end+0x148/0x3cf [reiser4] >>>>> [] reiser4_txn_restart+0xb/0x1a [reiser4] >>>>> [] reiser4_txn_restart_current+0x73/0x75 [reiser4] >>>>> [] force_commit_atom+0x258/0x261 [reiser4] >>>>> [] txnmgr_force_commit_all+0x406/0x697 [reiser4] >>>>> [] release_format40+0x10c/0x193 [reiser4] >>>>> [] reiser4_put_super+0x134/0x16a [reiser4] >>>>> [] generic_shutdown_super+0x55/0xd8 >>>>> [] kill_block_super+0x20/0x32 >>>>> [] deactivate_super+0x3f/0x51 >>>>> [] mntput_no_expire+0x42/0x5f >>>>> [] path_release_on_umount+0x15/0x18 >>>>> [] sys_umount+0x1a3/0x1cb >>>>> [] sys_oldumount+0x19/0x1b >>>>> [] sysenter_past_esp+0x5f/0x99 >>>>> ======================= >>>>> >>>>> Scenario: >>>>> - umount a reiser4 FS (no need to write something before) >>>> Hmm, I can not reproduce this with 2.6.20-rc3-mm1. Probably I need to config the kernel more close to your system. >>>> >>>>> Earlier kernels were OK. >>> This still happens with 2.6.20-rc4-mm1... >>> >>> Should I open a bug report at http://bugzilla.kernel.org? >>> >> Which device with reiser4 did you try to umount? Jens wrote that it >> could be a barrier related. If there are no multidevices involved - >> please report to bugzilla. > > Make sure that your kernel contains this fix: > > http://git.kernel.dk/?p=linux-2.6-block.git;a=commitdiff;h=4af09c42ee1af70356471f51c1f40c1ff7881b68;hp=036f6008f43b5b4dd8c825365f15434d75005c6d > > I think it missed 2.6.20-rc3-mm1. Again, that assumes you are using md > or dm. I've got 2 reiser4 FS: - one with /dev/sdb6 - the other with /dev/vglinux1/ccache (vglinux1 is built on /dev/sda4 and /dev/sdb7). There is no md here, only dm. I applied the above patch on top of 2.6.20-rc4-mm1, but the problem still happens with the two devices. thanks -- laurent - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/