From: "Vladimir V. Saveliev" <vs@namesys.com>
To: Laurent Riffard <laurent.riffard@free.fr>
Cc: reiserfs-list@namesys.com,
Kernel development list <linux-kernel@vger.kernel.org>,
Jens Axboe <axboe@suse.de>
Subject: Re: 2.6.20-rc3-mm1: umount reiser4 FS stuck in D state
Date: Tue, 23 Jan 2007 19:40:57 +0300 [thread overview]
Message-ID: <200701231940.58053.vs@namesys.com> (raw)
In-Reply-To: <45A81231.6040104@free.fr>
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:
> >> [<c012d600>] synchronize_qrcu+0x70/0x8c
> >> [<c01bede4>] __make_request+0x4c/0x29b
> >> [<c01bd24b>] generic_make_request+0x1b0/0x1de
> >> [<c01bf354>] submit_bio+0xda/0xe2
> >> [<e12674bd>] write_jnodes_to_disk_extent+0x920/0x974 [reiser4]
> >> [<e12678dd>] update_journal_footer+0x29f/0x2b7 [reiser4]
> >> [<e1268b65>] write_tx_back+0x149/0x185 [reiser4]
> >> [<e126a8e7>] reiser4_write_logs+0xea4/0xfd2 [reiser4]
> >> [<e125626a>] try_commit_txnh+0x7e6/0xa4f [reiser4]
> >> [<e125661b>] reiser4_txn_end+0x148/0x3cf [reiser4]
> >> [<e12568ad>] reiser4_txn_restart+0xb/0x1a [reiser4]
> >> [<e125692f>] reiser4_txn_restart_current+0x73/0x75 [reiser4]
> >> [<e1256b89>] force_commit_atom+0x258/0x261 [reiser4]
> >> [<e1257703>] txnmgr_force_commit_all+0x406/0x697 [reiser4]
> >> [<e12e5e08>] release_format40+0x10c/0x193 [reiser4]
> >> [<e1279922>] reiser4_put_super+0x134/0x16a [reiser4]
> >> [<c015c930>] generic_shutdown_super+0x55/0xd8
> >> [<c015c9d3>] kill_block_super+0x20/0x32
> >> [<c015ca75>] deactivate_super+0x3f/0x51
> >> [<c016d903>] mntput_no_expire+0x42/0x5f
> >> [<c0160f37>] path_release_on_umount+0x15/0x18
> >> [<c016df77>] sys_umount+0x1a3/0x1cb
> >> [<c016dfb8>] sys_oldumount+0x19/0x1b
> >> [<c0103ed2>] 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.
next prev parent reply other threads:[~2007-01-23 15:41 UTC|newest]
Thread overview: 43+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-01-05 6:02 2.6.20-rc3-mm1 Andrew Morton
2007-01-05 9:44 ` [-mm patch] lockdep: unbalance at generic_sync_sb_inodes Frederik Deweerdt
2007-01-05 12:16 ` [-mm patch] lockdep: possible deadlock in sysfs Frederik Deweerdt
2007-01-05 12:48 ` Oliver Neukum
2007-01-05 15:13 ` Oliver Neukum
2007-01-05 16:42 ` Frederik Deweerdt
2007-01-05 16:53 ` Oliver Neukum
2007-01-05 16:23 ` 2.6.20-rc3-mm1 Mariusz Kozlowski
2007-01-05 18:45 ` 2.6.20-rc3-mm1 Tim Schmielau
2007-01-08 12:36 ` 2.6.20-rc3-mm1 Mariusz Kozlowski
2007-01-05 20:55 ` 2.6.20-rc3-mm1 Benjamin Herrenschmidt
2007-01-05 21:15 ` 2.6.20-rc3-mm1 Andrew Morton
2007-01-05 21:24 ` 2.6.20-rc3-mm1 Benjamin Herrenschmidt
2007-01-08 19:32 ` 2.6.20-rc3-mm1 Cornelia Huck
2007-01-08 21:19 ` 2.6.20-rc3-mm1 Benjamin Herrenschmidt
2007-01-06 1:07 ` [-mm patch] make proc_dointvec_taint() static Adrian Bunk
2007-01-06 10:58 ` 2.6.20-rc3-mm1: umount reiser4 FS stuck in D state Laurent Riffard
2007-01-06 14:12 ` Laurent Riffard
2007-01-06 16:37 ` Jens Axboe
2007-01-06 18:58 ` Vladimir V. Saveliev
2007-01-12 22:56 ` Laurent Riffard
2007-01-23 16:40 ` Vladimir V. Saveliev [this message]
2007-01-23 15:46 ` Jens Axboe
2007-01-23 18:21 ` Laurent Riffard
2007-02-01 20:04 ` Edward Shishkin
2007-02-01 20:42 ` Laurent Riffard
2007-02-01 21:52 ` Edward Shishkin
2007-02-02 21:13 ` Laurent Riffard
2007-01-06 12:55 ` 2.6.20-rc3-mm1 - git-block.patch causes hard lockups Valdis.Kletnieks
2007-01-08 8:55 ` Jens Axboe
2007-01-09 18:03 ` Valdis.Kletnieks
2007-01-06 13:44 ` 2.6.20-rc3-mm1 - rewrite-lock-in-cpufreq-to-eliminate-cpufreq-hotplug-related-issues.patch Valdis.Kletnieks
2007-01-06 16:59 ` Mattia Dongili
2007-01-07 0:29 ` Valdis.Kletnieks
2007-01-06 15:20 ` 2.6.20-rc3-mm1 - reiser4-sb_sync_inodes.patch causes boot hang Valdis.Kletnieks
2007-01-06 19:14 ` Andrew Morton
2007-01-07 0:28 ` Valdis.Kletnieks
2007-01-09 14:40 ` [Re: 2.6.20-rc3-mm1] BUG: at kernel/sched.c:3415 sub_preempt_count() Maciej Rutecki
2007-01-09 15:28 ` Frederik Deweerdt
2007-01-09 20:50 ` Maciej Rutecki
2007-01-09 21:06 ` Frederik Deweerdt
2007-01-10 16:54 ` Maciej Rutecki
2007-01-11 18:28 ` [-mm patch] remove tcp header from tcp_v4_check Frederik Deweerdt
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=200701231940.58053.vs@namesys.com \
--to=vs@namesys.com \
--cc=axboe@suse.de \
--cc=laurent.riffard@free.fr \
--cc=linux-kernel@vger.kernel.org \
--cc=reiserfs-list@namesys.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).