Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S932622AbXAWPl3 (ORCPT ); Tue, 23 Jan 2007 10:41:29 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S932865AbXAWPl3 (ORCPT ); Tue, 23 Jan 2007 10:41:29 -0500 Received: from mail.alkar.net ([195.248.191.95]:54783 "EHLO mail.alkar.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S932622AbXAWPl1 convert rfc822-to-8bit (ORCPT ); Tue, 23 Jan 2007 10:41:27 -0500 From: "Vladimir V. Saveliev" To: Laurent Riffard Subject: Re: 2.6.20-rc3-mm1: umount reiser4 FS stuck in D state Date: Tue, 23 Jan 2007 19:40:57 +0300 User-Agent: KMail/1.8.2 Cc: reiserfs-list@namesys.com, Kernel development list , Jens Axboe References: <20070104220200.ae4e9a46.akpm@osdl.org> <200701062158.06329.vs@namesys.com> <45A81231.6040104@free.fr> In-Reply-To: <45A81231.6040104@free.fr> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 8BIT Content-Disposition: inline Message-Id: <200701231940.58053.vs@namesys.com> Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 2881 Lines: 67 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. - 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/