Re: 2.6.20-rc3-mm1: umount reiser4 FS stuck in D state
Le 01.02.2007 22:52, Edward Shishkin a écrit : Laurent Riffard wrote: Le 01.02.2007 21:04, Edward Shishkin a écrit : Laurent, would you please try 2.6.20-rc6-mm3 + this patch: http://lkml.org/lkml/diff/2007/2/1/195/1 Reiser4 works fine with 2.6.20-rc6-mm2 or 2.6.20-rc6-mm3 without any additional patch (it was broken in rc6-mm1). FWIW, Andrew removed git-block.patch from 2.6.20-rc6-mm2, and he restored git-block.patch without some problematic CFQ updates in 2.6.20-rc6-mm3. In this case, does this patch need testing in rc6-mm3 ? Yes. This is against git-block patch to prevent endless waiting for IO completion. I have reproduced it by ./iozone -B -a -n 524288 -f /mnt/foo on x86 box with 512M RAM available. OK, applied yesterday. I have been using it a few hours with a normal workload and I didn't notice any problem. Thanks -- laurent - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: 2.6.20-rc3-mm1: umount reiser4 FS stuck in D state
Le 01.02.2007 22:52, Edward Shishkin a écrit : Laurent Riffard wrote: Le 01.02.2007 21:04, Edward Shishkin a écrit : Laurent, would you please try 2.6.20-rc6-mm3 + this patch: http://lkml.org/lkml/diff/2007/2/1/195/1 Reiser4 works fine with 2.6.20-rc6-mm2 or 2.6.20-rc6-mm3 without any additional patch (it was broken in rc6-mm1). FWIW, Andrew removed git-block.patch from 2.6.20-rc6-mm2, and he restored git-block.patch without some problematic CFQ updates in 2.6.20-rc6-mm3. In this case, does this patch need testing in rc6-mm3 ? Yes. This is against git-block patch to prevent endless waiting for IO completion. I have reproduced it by ./iozone -B -a -n 524288 -f /mnt/foo on x86 box with 512M RAM available. OK, applied yesterday. I have been using it a few hours with a normal workload and I didn't notice any problem. Thanks -- laurent - To unsubscribe from this list: send the line unsubscribe linux-kernel in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: 2.6.20-rc3-mm1: umount reiser4 FS stuck in D state
Laurent Riffard wrote: Le 01.02.2007 21:04, Edward Shishkin a écrit : Laurent Riffard wrote: 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 freesibling task PCstack pid father child younger older umountD C013135E 6044 1168 1150 (NOTLB) de591ae4 0086 de591abc c013135e dff979c8 c012a6fe 0046 0007dfd94ac0 128d3000 0026 dfd94bcc dff979c8 de591ae4 dffda0380002 dff979c0 dff979bc dff979c8 de591b10 c012d600 dff979f8 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, would you please try 2.6.20-rc6-mm3 + this patch: http://lkml.org/lkml/diff/2007/2/1/195/1 Reiser4 works fine with 2.6.20-rc6-mm2 or 2.6.20-rc6-mm3 without any additional patch (it was broken in rc6-mm1). FWIW, Andrew removed git-block.patch from 2.6.20-rc6-mm2, and he restored git-block.patch without some problematic CFQ updates in 2.6.20-rc6-mm3. In this case, does this patch need testing in rc6-mm3 ? Yes. This is against git-block patch to prevent endless waiting for IO completion. I have reproduced it by ./iozone -B -a -n 524288 -f /mnt/foo on x86 box with 512M RAM available. - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: 2.6.20-rc3-mm1: umount reiser4 FS stuck in D state
Le 01.02.2007 21:04, Edward Shishkin a écrit : Laurent Riffard wrote: 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 freesibling task PCstack pid father child younger older umountD C013135E 6044 1168 1150 (NOTLB) de591ae4 0086 de591abc c013135e dff979c8 c012a6fe 0046 0007dfd94ac0 128d3000 0026 dfd94bcc dff979c8 de591ae4 dffda0380002 dff979c0 dff979bc dff979c8 de591b10 c012d600 dff979f8 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, would you please try 2.6.20-rc6-mm3 + this patch: http://lkml.org/lkml/diff/2007/2/1/195/1 Reiser4 works fine with 2.6.20-rc6-mm2 or 2.6.20-rc6-mm3 without any additional patch (it was broken in rc6-mm1). FWIW, Andrew removed git-block.patch from 2.6.20-rc6-mm2, and he restored git-block.patch without some problematic CFQ updates in 2.6.20-rc6-mm3. In this case, does this patch need testing in rc6-mm3 ? -- laurent - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: 2.6.20-rc3-mm1: umount reiser4 FS stuck in D state
Laurent Riffard wrote: 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 freesibling task PCstack pid father child younger older umountD C013135E 6044 1168 1150 (NOTLB) de591ae4 0086 de591abc c013135e dff979c8 c012a6fe 0046 0007dfd94ac0 128d3000 0026 dfd94bcc dff979c8 de591ae4 dffda0380002 dff979c0 dff979bc dff979c8 de591b10 c012d600 dff979f8 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, would you please try 2.6.20-rc6-mm3 + this patch: http://lkml.org/lkml/diff/2007/2/1/195/1 Thanks, Edward. - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: 2.6.20-rc3-mm1: umount reiser4 FS stuck in D state
Laurent Riffard wrote: 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 freesibling task PCstack pid father child younger older umountD C013135E 6044 1168 1150 (NOTLB) de591ae4 0086 de591abc c013135e dff979c8 c012a6fe 0046 0007dfd94ac0 128d3000 0026 dfd94bcc dff979c8 de591ae4 dffda0380002 dff979c0 dff979bc dff979c8 de591b10 c012d600 dff979f8 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. 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, would you please try 2.6.20-rc6-mm3 + this patch: http://lkml.org/lkml/diff/2007/2/1/195/1 Thanks, Edward. - To unsubscribe from this list: send the line unsubscribe linux-kernel in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: 2.6.20-rc3-mm1: umount reiser4 FS stuck in D state
Le 01.02.2007 21:04, Edward Shishkin a écrit : Laurent Riffard wrote: 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 freesibling task PCstack pid father child younger older umountD C013135E 6044 1168 1150 (NOTLB) de591ae4 0086 de591abc c013135e dff979c8 c012a6fe 0046 0007dfd94ac0 128d3000 0026 dfd94bcc dff979c8 de591ae4 dffda0380002 dff979c0 dff979bc dff979c8 de591b10 c012d600 dff979f8 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. 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, would you please try 2.6.20-rc6-mm3 + this patch: http://lkml.org/lkml/diff/2007/2/1/195/1 Reiser4 works fine with 2.6.20-rc6-mm2 or 2.6.20-rc6-mm3 without any additional patch (it was broken in rc6-mm1). FWIW, Andrew removed git-block.patch from 2.6.20-rc6-mm2, and he restored git-block.patch without some problematic CFQ updates in 2.6.20-rc6-mm3. In this case, does this patch need testing in rc6-mm3 ? -- laurent - To unsubscribe from this list: send the line unsubscribe linux-kernel in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: 2.6.20-rc3-mm1: umount reiser4 FS stuck in D state
Laurent Riffard wrote: Le 01.02.2007 21:04, Edward Shishkin a écrit : Laurent Riffard wrote: 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 freesibling task PCstack pid father child younger older umountD C013135E 6044 1168 1150 (NOTLB) de591ae4 0086 de591abc c013135e dff979c8 c012a6fe 0046 0007dfd94ac0 128d3000 0026 dfd94bcc dff979c8 de591ae4 dffda0380002 dff979c0 dff979bc dff979c8 de591b10 c012d600 dff979f8 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. 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, would you please try 2.6.20-rc6-mm3 + this patch: http://lkml.org/lkml/diff/2007/2/1/195/1 Reiser4 works fine with 2.6.20-rc6-mm2 or 2.6.20-rc6-mm3 without any additional patch (it was broken in rc6-mm1). FWIW, Andrew removed git-block.patch from 2.6.20-rc6-mm2, and he restored git-block.patch without some problematic CFQ updates in 2.6.20-rc6-mm3. In this case, does this patch need testing in rc6-mm3 ? Yes. This is against git-block patch to prevent endless waiting for IO completion. I have reproduced it by ./iozone -B -a -n 524288 -f /mnt/foo on x86 box with 512M RAM available. - To unsubscribe from this list: send the line unsubscribe linux-kernel in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: 2.6.20-rc3-mm1: umount reiser4 FS stuck in D state
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 freesibling task PCstack pid father child younger older umountD C013135E 6044 1168 1150 (NOTLB) de591ae4 0086 de591abc c013135e dff979c8 c012a6fe 0046 0007 dfd94ac0 128d3000 0026 dfd94bcc dff979c8 de591ae4 dffda038 0002 dff979c0 dff979bc dff979c8 de591b10 c012d600 dff979f8 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 [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: 2.6.20-rc3-mm1: umount reiser4 FS stuck in D state
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 > > >> > > >> freesibling > > >> task PCstack pid father child younger older > > >> umountD C013135E 6044 1168 1150 (NOTLB) > > >>de591ae4 0086 de591abc c013135e dff979c8 c012a6fe 0046 > > >> 0007 > > >>dfd94ac0 128d3000 0026 dfd94bcc dff979c8 de591ae4 > > >> dffda038 > > >>0002 dff979c0 dff979bc dff979c8 de591b10 c012d600 dff979f8 > > >> > > >> 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. -- Jens Axboe - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: 2.6.20-rc3-mm1: umount reiser4 FS stuck in D state
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 > >> > >> freesibling > >> task PCstack pid father child younger older > >> umountD C013135E 6044 1168 1150 (NOTLB) > >>de591ae4 0086 de591abc c013135e dff979c8 c012a6fe 0046 > >> 0007 > >>dfd94ac0 128d3000 0026 dfd94bcc dff979c8 de591ae4 > >> dffda038 > >>0002 dff979c0 dff979bc dff979c8 de591b10 c012d600 dff979f8 > >> > >> 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 [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: 2.6.20-rc3-mm1: umount reiser4 FS stuck in D state
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 freesibling task PCstack pid father child younger older umountD C013135E 6044 1168 1150 (NOTLB) de591ae4 0086 de591abc c013135e dff979c8 c012a6fe 0046 0007 dfd94ac0 128d3000 0026 dfd94bcc dff979c8 de591ae4 dffda038 0002 dff979c0 dff979bc dff979c8 de591b10 c012d600 dff979f8 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. - To unsubscribe from this list: send the line unsubscribe linux-kernel in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: 2.6.20-rc3-mm1: umount reiser4 FS stuck in D state
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
freesibling
task PCstack pid father child younger older
umountD C013135E 6044 1168 1150 (NOTLB)
de591ae4 0086 de591abc c013135e dff979c8 c012a6fe 0046
0007
dfd94ac0 128d3000 0026 dfd94bcc dff979c8 de591ae4
dffda038
0002 dff979c0 dff979bc dff979c8 de591b10 c012d600 dff979f8
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.
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.
--
Jens Axboe
-
To unsubscribe from this list: send the line unsubscribe linux-kernel in
the body of a message to [EMAIL PROTECTED]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Re: 2.6.20-rc3-mm1: umount reiser4 FS stuck in D state
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 freesibling task PCstack pid father child younger older umountD C013135E 6044 1168 1150 (NOTLB) de591ae4 0086 de591abc c013135e dff979c8 c012a6fe 0046 0007 dfd94ac0 128d3000 0026 dfd94bcc dff979c8 de591ae4 dffda038 0002 dff979c0 dff979bc dff979c8 de591b10 c012d600 dff979f8 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. 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 [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: 2.6.20-rc3-mm1: umount reiser4 FS stuck in D state
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 freesibling task PCstack pid father child younger older umountD C013135E 6044 1168 1150 (NOTLB) de591ae4 0086 de591abc c013135e dff979c8 c012a6fe 0046 0007 dfd94ac0 128d3000 0026 dfd94bcc dff979c8 de591ae4 dffda038 0002 dff979c0 dff979bc dff979c8 de591b10 c012d600 dff979f8 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? -- laurent - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: 2.6.20-rc3-mm1: umount reiser4 FS stuck in D state
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 freesibling task PCstack pid father child younger older umountD C013135E 6044 1168 1150 (NOTLB) de591ae4 0086 de591abc c013135e dff979c8 c012a6fe 0046 0007 dfd94ac0 128d3000 0026 dfd94bcc dff979c8 de591ae4 dffda038 0002 dff979c0 dff979bc dff979c8 de591b10 c012d600 dff979f8 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? -- laurent - To unsubscribe from this list: send the line unsubscribe linux-kernel in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: 2.6.20-rc3-mm1: umount reiser4 FS stuck in D state
Hello On Saturday 06 January 2007 13:58, Laurent Riffard wrote: > Le 05.01.2007 07:02, Andrew Morton a écrit : > > Temporarily at > > > > http://userweb.kernel.org/~akpm/2.6.20-rc3-mm1/ > > > > will appear later at > > > > > > ftp://ftp.kernel.org/pub/linux/kernel/people/akpm/patches/2.6/2.6.20-rc3/2.6.20-rc3-mm1/ > > Hello, > > got this with 2.6.20-rc3-mm1: > > === > SysRq : Show Blocked State > > freesibling > task PCstack pid father child younger older > umountD C013135E 6044 1168 1150 (NOTLB) >de591ae4 0086 de591abc c013135e dff979c8 c012a6fe 0046 > 0007 >dfd94ac0 128d3000 0026 dfd94bcc dff979c8 de591ae4 > dffda038 >0002 dff979c0 dff979bc dff979c8 de591b10 c012d600 dff979f8 > > 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. > > I tested Frederik Deweerdt's patch for "lockdep: unbalance at > generic_sync_sb_inodes", it did not help. > > I think I'll a give a try to > http://userweb.kernel.org/~akpm/2.6.20-rc3-mm1x.bz2 (basically > 2.6.20-rc3-mm1, minus git-block.patch). > > .config attached > > ~~ > laurent > > > - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: 2.6.20-rc3-mm1: umount reiser4 FS stuck in D state
On Sat, Jan 06 2007, Laurent Riffard wrote: > Le 05.01.2007 07:02, Andrew Morton a écrit : > >Temporarily at > > > > http://userweb.kernel.org/~akpm/2.6.20-rc3-mm1/ > > > >will appear later at > > > > > > ftp://ftp.kernel.org/pub/linux/kernel/people/akpm/patches/2.6/2.6.20-rc3/2.6.20-rc3-mm1/ > > Hello, > > got this with 2.6.20-rc3-mm1: > > === > SysRq : Show Blocked State > > freesibling > task PCstack pid father child younger older > umountD C013135E 6044 1168 1150 (NOTLB) > de591ae4 0086 de591abc c013135e dff979c8 c012a6fe 0046 > 0007 dfd94ac0 128d3000 0026 dfd94bcc dff979c8 > de591ae4 dffda038 0002 dff979c0 dff979bc dff979c8 de591b10 > c012d600 dff979f8 Call Trace: > [] synchronize_qrcu+0x70/0x8c > [] __make_request+0x4c/0x29b > [] generic_make_request+0x1b0/0x1de > [] submit_bio+0xda/0xe2 That's certainly a barrier related hang. Since raid and XFS both hang as well, it might be the same problem. I'll get it fixed up, don't expect anything before monday though. -- Jens Axboe - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: 2.6.20-rc3-mm1: umount reiser4 FS stuck in D state
Le 06.01.2007 11:58, Laurent Riffard a écrit : Le 05.01.2007 07:02, Andrew Morton a écrit : Temporarily at http://userweb.kernel.org/~akpm/2.6.20-rc3-mm1/ will appear later at ftp://ftp.kernel.org/pub/linux/kernel/people/akpm/patches/2.6/2.6.20-rc3/2.6.20-rc3-mm1/ Hello, got this with 2.6.20-rc3-mm1: === SysRq : Show Blocked State freesibling task PCstack pid father child younger older umountD C013135E 6044 1168 1150 (NOTLB) de591ae4 0086 de591abc c013135e dff979c8 c012a6fe 0046 0007 dfd94ac0 128d3000 0026 dfd94bcc dff979c8 de591ae4 dffda038 0002 dff979c0 dff979bc dff979c8 de591b10 c012d600 dff979f8 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) Earlier kernels were OK. I tested Frederik Deweerdt's patch for "lockdep: unbalance at generic_sync_sb_inodes", it did not help. I think I'll a give a try to http://userweb.kernel.org/~akpm/2.6.20-rc3-mm1x.bz2 (basically 2.6.20-rc3-mm1, minus git-block.patch). Ok, 2.6.20-rc3-mm1 minus git-block.patch does work for me, ie I can safely use reiser4 FS, there is no more lockups. -- laurent - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: 2.6.20-rc3-mm1: umount reiser4 FS stuck in D state
Le 05.01.2007 07:02, Andrew Morton a écrit : Temporarily at http://userweb.kernel.org/~akpm/2.6.20-rc3-mm1/ will appear later at ftp://ftp.kernel.org/pub/linux/kernel/people/akpm/patches/2.6/2.6.20-rc3/2.6.20-rc3-mm1/ Hello, got this with 2.6.20-rc3-mm1: === SysRq : Show Blocked State freesibling task PCstack pid father child younger older umountD C013135E 6044 1168 1150 (NOTLB) de591ae4 0086 de591abc c013135e dff979c8 c012a6fe 0046 0007 dfd94ac0 128d3000 0026 dfd94bcc dff979c8 de591ae4 dffda038 0002 dff979c0 dff979bc dff979c8 de591b10 c012d600 dff979f8 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) Earlier kernels were OK. I tested Frederik Deweerdt's patch for "lockdep: unbalance at generic_sync_sb_inodes", it did not help. I think I'll a give a try to http://userweb.kernel.org/~akpm/2.6.20-rc3-mm1x.bz2 (basically 2.6.20-rc3-mm1, minus git-block.patch). .config attached ~~ laurent # # Automatically generated make config: don't edit # Linux kernel version: 2.6.20-rc3-mm1 # Sat Jan 6 09:34:05 2007 # CONFIG_X86_32=y CONFIG_GENERIC_TIME=y CONFIG_GENERIC_CLOCKEVENTS=y CONFIG_GENERIC_CLOCKEVENTS_BROADCAST=y CONFIG_LOCKDEP_SUPPORT=y CONFIG_STACKTRACE_SUPPORT=y CONFIG_SEMAPHORE_SLEEPERS=y CONFIG_X86=y CONFIG_MMU=y CONFIG_ZONE_DMA=y CONFIG_GENERIC_ISA_DMA=y CONFIG_GENERIC_IOMAP=y CONFIG_GENERIC_BUG=y CONFIG_GENERIC_HWEIGHT=y CONFIG_ARCH_MAY_HAVE_PC_FDC=y CONFIG_DMI=y CONFIG_DEFCONFIG_LIST="/lib/modules/$UNAME_RELEASE/.config" # # Code maturity level options # CONFIG_EXPERIMENTAL=y CONFIG_BROKEN_ON_SMP=y CONFIG_LOCK_KERNEL=y CONFIG_INIT_ENV_ARG_LIMIT=32 # # General setup # CONFIG_LOCALVERSION="" CONFIG_LOCALVERSION_AUTO=y CONFIG_SWAP=y CONFIG_SWAP_PREFETCH=y CONFIG_SYSVIPC=y # CONFIG_IPC_NS is not set CONFIG_POSIX_MQUEUE=y # CONFIG_BSD_PROCESS_ACCT is not set # CONFIG_TASKSTATS is not set # CONFIG_UTS_NS is not set CONFIG_USER_NS=y # CONFIG_AUDIT is not set # CONFIG_IKCONFIG is not set CONFIG_SYSFS_DEPRECATED=y # CONFIG_RELAY is not set CONFIG_INITRAMFS_SOURCE="" CONFIG_CC_OPTIMIZE_FOR_SIZE=y CONFIG_SYSCTL=y CONFIG_EMBEDDED=y CONFIG_UID16=y CONFIG_SYSCTL_SYSCALL=y CONFIG_KALLSYMS=y CONFIG_KALLSYMS_ALL=y # CONFIG_KALLSYMS_EXTRA_PASS is not set CONFIG_HOTPLUG=y CONFIG_PRINTK=y CONFIG_BUG=y CONFIG_ELF_CORE=y CONFIG_BASE_FULL=y CONFIG_FUTEX=y CONFIG_EPOLL=y CONFIG_SHMEM=y CONFIG_SLAB=y CONFIG_VM_EVENT_COUNTERS=y CONFIG_RT_MUTEXES=y # CONFIG_TINY_SHMEM is not set CONFIG_BASE_SMALL=0 # CONFIG_SLOB is not set # # Loadable module support # CONFIG_MODULES=y CONFIG_MODULE_UNLOAD=y CONFIG_MODULE_FORCE_UNLOAD=y # CONFIG_MODVERSIONS is not set # CONFIG_MODULE_SRCVERSION_ALL is not set CONFIG_KMOD=y # # Block layer # CONFIG_BLOCK=y # CONFIG_LBD is not set # CONFIG_BLK_DEV_IO_TRACE is not set # CONFIG_LSF is not set # # IO Schedulers # CONFIG_IOSCHED_NOOP=y CONFIG_IOSCHED_AS=y CONFIG_IOSCHED_DEADLINE=y CONFIG_IOSCHED_CFQ=y # CONFIG_DEFAULT_AS is not set # CONFIG_DEFAULT_DEADLINE is not set CONFIG_DEFAULT_CFQ=y # CONFIG_DEFAULT_NOOP is not set CONFIG_DEFAULT_IOSCHED="cfq" # # Processor type and features # # CONFIG_HIGH_RES_TIMERS is not set # CONFIG_SMP is not set CONFIG_X86_PC=y # CONFIG_X86_ELAN is not set # CONFIG_X86_VOYAGER is not set # CONFIG_X86_NUMAQ is not set # CONFIG_X86_SUMMIT is not set # CONFIG_X86_BIGSMP is not set # CONFIG_X86_VISWS is not set # CONFIG_X86_GENERICARCH is not set # CONFIG_X86_ES7000 is not set # CONFIG_PARAVIRT is not set # CONFIG_M386 is not set # CONFIG_M486 is not set # CONFIG_M586 is not set # CONFIG_M586TSC is not set # CONFIG_M586MMX is not set # CONFIG_M686 is not set # CONFIG_MPENTIUMII is not set # CONFIG_MPENTIUMIII is not set # CONFIG_MPENTIUMM is not set # CONFIG_MCORE2 is not set # CONFIG_MPENTIUM4 is not set # CONFIG_MK6 is not set CONFIG_MK7=y # CONFIG_MK8 is not set # CONFIG_MCRUSOE is not set # CONFIG_MEFFICEON is not
Re: 2.6.20-rc3-mm1: umount reiser4 FS stuck in D state
Le 05.01.2007 07:02, Andrew Morton a écrit : Temporarily at http://userweb.kernel.org/~akpm/2.6.20-rc3-mm1/ will appear later at ftp://ftp.kernel.org/pub/linux/kernel/people/akpm/patches/2.6/2.6.20-rc3/2.6.20-rc3-mm1/ Hello, got this with 2.6.20-rc3-mm1: === SysRq : Show Blocked State freesibling task PCstack pid father child younger older umountD C013135E 6044 1168 1150 (NOTLB) de591ae4 0086 de591abc c013135e dff979c8 c012a6fe 0046 0007 dfd94ac0 128d3000 0026 dfd94bcc dff979c8 de591ae4 dffda038 0002 dff979c0 dff979bc dff979c8 de591b10 c012d600 dff979f8 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) Earlier kernels were OK. I tested Frederik Deweerdt's patch for lockdep: unbalance at generic_sync_sb_inodes, it did not help. I think I'll a give a try to http://userweb.kernel.org/~akpm/2.6.20-rc3-mm1x.bz2 (basically 2.6.20-rc3-mm1, minus git-block.patch). .config attached ~~ laurent # # Automatically generated make config: don't edit # Linux kernel version: 2.6.20-rc3-mm1 # Sat Jan 6 09:34:05 2007 # CONFIG_X86_32=y CONFIG_GENERIC_TIME=y CONFIG_GENERIC_CLOCKEVENTS=y CONFIG_GENERIC_CLOCKEVENTS_BROADCAST=y CONFIG_LOCKDEP_SUPPORT=y CONFIG_STACKTRACE_SUPPORT=y CONFIG_SEMAPHORE_SLEEPERS=y CONFIG_X86=y CONFIG_MMU=y CONFIG_ZONE_DMA=y CONFIG_GENERIC_ISA_DMA=y CONFIG_GENERIC_IOMAP=y CONFIG_GENERIC_BUG=y CONFIG_GENERIC_HWEIGHT=y CONFIG_ARCH_MAY_HAVE_PC_FDC=y CONFIG_DMI=y CONFIG_DEFCONFIG_LIST=/lib/modules/$UNAME_RELEASE/.config # # Code maturity level options # CONFIG_EXPERIMENTAL=y CONFIG_BROKEN_ON_SMP=y CONFIG_LOCK_KERNEL=y CONFIG_INIT_ENV_ARG_LIMIT=32 # # General setup # CONFIG_LOCALVERSION= CONFIG_LOCALVERSION_AUTO=y CONFIG_SWAP=y CONFIG_SWAP_PREFETCH=y CONFIG_SYSVIPC=y # CONFIG_IPC_NS is not set CONFIG_POSIX_MQUEUE=y # CONFIG_BSD_PROCESS_ACCT is not set # CONFIG_TASKSTATS is not set # CONFIG_UTS_NS is not set CONFIG_USER_NS=y # CONFIG_AUDIT is not set # CONFIG_IKCONFIG is not set CONFIG_SYSFS_DEPRECATED=y # CONFIG_RELAY is not set CONFIG_INITRAMFS_SOURCE= CONFIG_CC_OPTIMIZE_FOR_SIZE=y CONFIG_SYSCTL=y CONFIG_EMBEDDED=y CONFIG_UID16=y CONFIG_SYSCTL_SYSCALL=y CONFIG_KALLSYMS=y CONFIG_KALLSYMS_ALL=y # CONFIG_KALLSYMS_EXTRA_PASS is not set CONFIG_HOTPLUG=y CONFIG_PRINTK=y CONFIG_BUG=y CONFIG_ELF_CORE=y CONFIG_BASE_FULL=y CONFIG_FUTEX=y CONFIG_EPOLL=y CONFIG_SHMEM=y CONFIG_SLAB=y CONFIG_VM_EVENT_COUNTERS=y CONFIG_RT_MUTEXES=y # CONFIG_TINY_SHMEM is not set CONFIG_BASE_SMALL=0 # CONFIG_SLOB is not set # # Loadable module support # CONFIG_MODULES=y CONFIG_MODULE_UNLOAD=y CONFIG_MODULE_FORCE_UNLOAD=y # CONFIG_MODVERSIONS is not set # CONFIG_MODULE_SRCVERSION_ALL is not set CONFIG_KMOD=y # # Block layer # CONFIG_BLOCK=y # CONFIG_LBD is not set # CONFIG_BLK_DEV_IO_TRACE is not set # CONFIG_LSF is not set # # IO Schedulers # CONFIG_IOSCHED_NOOP=y CONFIG_IOSCHED_AS=y CONFIG_IOSCHED_DEADLINE=y CONFIG_IOSCHED_CFQ=y # CONFIG_DEFAULT_AS is not set # CONFIG_DEFAULT_DEADLINE is not set CONFIG_DEFAULT_CFQ=y # CONFIG_DEFAULT_NOOP is not set CONFIG_DEFAULT_IOSCHED=cfq # # Processor type and features # # CONFIG_HIGH_RES_TIMERS is not set # CONFIG_SMP is not set CONFIG_X86_PC=y # CONFIG_X86_ELAN is not set # CONFIG_X86_VOYAGER is not set # CONFIG_X86_NUMAQ is not set # CONFIG_X86_SUMMIT is not set # CONFIG_X86_BIGSMP is not set # CONFIG_X86_VISWS is not set # CONFIG_X86_GENERICARCH is not set # CONFIG_X86_ES7000 is not set # CONFIG_PARAVIRT is not set # CONFIG_M386 is not set # CONFIG_M486 is not set # CONFIG_M586 is not set # CONFIG_M586TSC is not set # CONFIG_M586MMX is not set # CONFIG_M686 is not set # CONFIG_MPENTIUMII is not set # CONFIG_MPENTIUMIII is not set # CONFIG_MPENTIUMM is
Re: 2.6.20-rc3-mm1: umount reiser4 FS stuck in D state
Le 06.01.2007 11:58, Laurent Riffard a écrit : Le 05.01.2007 07:02, Andrew Morton a écrit : Temporarily at http://userweb.kernel.org/~akpm/2.6.20-rc3-mm1/ will appear later at ftp://ftp.kernel.org/pub/linux/kernel/people/akpm/patches/2.6/2.6.20-rc3/2.6.20-rc3-mm1/ Hello, got this with 2.6.20-rc3-mm1: === SysRq : Show Blocked State freesibling task PCstack pid father child younger older umountD C013135E 6044 1168 1150 (NOTLB) de591ae4 0086 de591abc c013135e dff979c8 c012a6fe 0046 0007 dfd94ac0 128d3000 0026 dfd94bcc dff979c8 de591ae4 dffda038 0002 dff979c0 dff979bc dff979c8 de591b10 c012d600 dff979f8 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) Earlier kernels were OK. I tested Frederik Deweerdt's patch for lockdep: unbalance at generic_sync_sb_inodes, it did not help. I think I'll a give a try to http://userweb.kernel.org/~akpm/2.6.20-rc3-mm1x.bz2 (basically 2.6.20-rc3-mm1, minus git-block.patch). Ok, 2.6.20-rc3-mm1 minus git-block.patch does work for me, ie I can safely use reiser4 FS, there is no more lockups. -- laurent - To unsubscribe from this list: send the line unsubscribe linux-kernel in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: 2.6.20-rc3-mm1: umount reiser4 FS stuck in D state
On Sat, Jan 06 2007, Laurent Riffard wrote: Le 05.01.2007 07:02, Andrew Morton a écrit : Temporarily at http://userweb.kernel.org/~akpm/2.6.20-rc3-mm1/ will appear later at ftp://ftp.kernel.org/pub/linux/kernel/people/akpm/patches/2.6/2.6.20-rc3/2.6.20-rc3-mm1/ Hello, got this with 2.6.20-rc3-mm1: === SysRq : Show Blocked State freesibling task PCstack pid father child younger older umountD C013135E 6044 1168 1150 (NOTLB) de591ae4 0086 de591abc c013135e dff979c8 c012a6fe 0046 0007 dfd94ac0 128d3000 0026 dfd94bcc dff979c8 de591ae4 dffda038 0002 dff979c0 dff979bc dff979c8 de591b10 c012d600 dff979f8 Call Trace: [c012d600] synchronize_qrcu+0x70/0x8c [c01bede4] __make_request+0x4c/0x29b [c01bd24b] generic_make_request+0x1b0/0x1de [c01bf354] submit_bio+0xda/0xe2 That's certainly a barrier related hang. Since raid and XFS both hang as well, it might be the same problem. I'll get it fixed up, don't expect anything before monday though. -- Jens Axboe - To unsubscribe from this list: send the line unsubscribe linux-kernel in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: 2.6.20-rc3-mm1: umount reiser4 FS stuck in D state
Hello On Saturday 06 January 2007 13:58, Laurent Riffard wrote: Le 05.01.2007 07:02, Andrew Morton a écrit : Temporarily at http://userweb.kernel.org/~akpm/2.6.20-rc3-mm1/ will appear later at ftp://ftp.kernel.org/pub/linux/kernel/people/akpm/patches/2.6/2.6.20-rc3/2.6.20-rc3-mm1/ Hello, got this with 2.6.20-rc3-mm1: === SysRq : Show Blocked State freesibling task PCstack pid father child younger older umountD C013135E 6044 1168 1150 (NOTLB) de591ae4 0086 de591abc c013135e dff979c8 c012a6fe 0046 0007 dfd94ac0 128d3000 0026 dfd94bcc dff979c8 de591ae4 dffda038 0002 dff979c0 dff979bc dff979c8 de591b10 c012d600 dff979f8 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. I tested Frederik Deweerdt's patch for lockdep: unbalance at generic_sync_sb_inodes, it did not help. I think I'll a give a try to http://userweb.kernel.org/~akpm/2.6.20-rc3-mm1x.bz2 (basically 2.6.20-rc3-mm1, minus git-block.patch). .config attached ~~ laurent - To unsubscribe from this list: send the line unsubscribe linux-kernel in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
