Re: linux-2.6.20-rc4-mm1 Reiser4 filesystem freeze and corruption
On Thu, 2007-02-01 at 18:54 +0300, Edward Shishkin wrote: [snip] > Thanks for the dump. > > >[ 3138.456588] [] current_atom_finish_all_fq+0x12e/0x280 > >[ 3138.456661] [] autoremove_wake_function+0x0/0x30 > >[ 3138.456674] [] submit_wb_list+0x11c/0x130 > >[ 3138.456690] [] reiser4_txn_end+0x349/0x530 > >[ 3138.456710] [] reiser4_txn_restart+0x9/0x20 > >[ 3138.456781] [] force_commit_atom+0x50/0x60 > >[ 3138.456793] [] writepages_unix_file+0x671/0x780 > >[ 3138.456824] [] do_writepages+0x43/0x80 > >[ 3138.456838] [] __filemap_fdatawrite_range+0x58/0x70 > >[ 3138.456914] [] do_fsync+0x3d/0xe0 > >[ 3138.456930] [] sys_msync+0x143/0x1f0 > >[ 3138.456945] [] system_call+0x7e/0x83 > > > > > > This is waiting for IO completion, and no success because of new plugging > policy introduced by block layer folks. The attached patch should help. > Andrew, please apply. OK, I have been using it with your patch for many hours and it has not frozen up yet. I believe that the patch did indeed fix it. Thank you. -- Zan Lynx <[EMAIL PROTECTED]> signature.asc Description: This is a digitally signed message part
Re: linux-2.6.20-rc4-mm1 Reiser4 filesystem freeze and corruption
Zan Lynx wrote:
On Sat, 2007-01-20 at 03:34 +0300, Vladimir V. Saveliev wrote:
Hello
On Friday 19 January 2007 20:58, Zan Lynx wrote:
I have been running 2.6.20-rc2-mm1 without problems, but both rc3-mm1
and rc4-mm1 have been giving me these freezes. They were happening
inside X and without external console it was impossible to get anything,
plus I was reluctant to test it since the freeze sometimes requires a
full fsck.reiser4 --build-fs to recover the filesystem.
But I finally got some output in a console session. I wasn't able to
get it all, I made some notes of what I think the problem is. I may try
again later once I get netconsole working (netconsole fails as a
built-in, I'll try it as a module next).
[snip]
yes, please provide more information. Full kernel output at time of freeze is
very desirable.
Here comes a full sized bug report, as best as I can do it. This is
kernel 2.6.20-rc6-mm3 instead of rc4-mm1. Still has the problem.
Thanks for the dump.
[ 3138.456588] [] current_atom_finish_all_fq+0x12e/0x280
[ 3138.456661] [] autoremove_wake_function+0x0/0x30
[ 3138.456674] [] submit_wb_list+0x11c/0x130
[ 3138.456690] [] reiser4_txn_end+0x349/0x530
[ 3138.456710] [] reiser4_txn_restart+0x9/0x20
[ 3138.456781] [] force_commit_atom+0x50/0x60
[ 3138.456793] [] writepages_unix_file+0x671/0x780
[ 3138.456824] [] do_writepages+0x43/0x80
[ 3138.456838] [] __filemap_fdatawrite_range+0x58/0x70
[ 3138.456914] [] do_fsync+0x3d/0xe0
[ 3138.456930] [] sys_msync+0x143/0x1f0
[ 3138.456945] [] system_call+0x7e/0x83
This is waiting for IO completion, and no success because of new plugging
policy introduced by block layer folks. The attached patch should help.
Andrew, please apply.
Thanks,
Edward.
Signed-off-by: Edward Shishkin <[EMAIL PROTECTED]>
---
linux-2.6.20-rc6-mm3/fs/reiser4/status_flags.c |2 ++
linux-2.6.20-rc6-mm3/fs/reiser4/wander.c | 18 +++---
2 files changed, 13 insertions(+), 7 deletions(-)
--- linux-2.6.20-rc6-mm3/fs/reiser4/status_flags.c.orig
+++ linux-2.6.20-rc6-mm3/fs/reiser4/status_flags.c
@@ -63,6 +63,7 @@
}
lock_page(page);
submit_bio(READ, bio);
+ blk_replug_current_nested();
wait_on_page_locked(page);
if (!PageUptodate(page)) {
warning("green-2007",
@@ -157,6 +158,7 @@
lock_page(get_super_private(sb)->status_page); // Safe as nobody should touch our page.
/* We can block now, but we have no other choice anyway */
submit_bio(WRITE, bio);
+ blk_replug_current_nested();
return 0; // We do not wait for io to finish.
}
--- linux-2.6.20-rc6-mm3/fs/reiser4/wander.c.orig
+++ linux-2.6.20-rc6-mm3/fs/reiser4/wander.c
@@ -718,6 +718,7 @@
jnode *first, int nr, const reiser4_block_nr *block_p,
flush_queue_t *fq, int flags)
{
+ int ret = 0;
struct super_block *super = reiser4_get_current_sb();
int write_op = ( flags & WRITEOUT_BARRIER ) ? WRITE_BARRIER : WRITE;
int max_blocks;
@@ -738,9 +739,10 @@
int nr_used;
bio = bio_alloc(GFP_NOIO, nr_blocks);
- if (!bio)
- return RETERR(-ENOMEM);
-
+ if (!bio) {
+ ret = RETERR(-ENOMEM);
+ break;
+ }
bio->bi_bdev = super->s_bdev;
bio->bi_sector = block * (super->s_blocksize >> 9);
for (nr_used = 0, i = 0; i < nr_blocks; i++) {
@@ -843,8 +845,10 @@
reiser4_submit_bio(write_op, bio);
not_supported = bio_flagged(bio, BIO_EOPNOTSUPP);
bio_put(bio);
-if (not_supported)
- return -EOPNOTSUPP;
+if (not_supported) {
+ ret = -EOPNOTSUPP;
+ break;
+}
}
block += nr_used - 1;
@@ -855,8 +859,8 @@
}
nr -= nr_used;
}
-
- return 0;
+ blk_replug_current_nested();
+ return ret;
}
/* This is a procedure which recovers a contiguous sequences of disk block
Re: linux-2.6.20-rc4-mm1 Reiser4 filesystem freeze and corruption
Zan Lynx wrote:
On Sat, 2007-01-20 at 03:34 +0300, Vladimir V. Saveliev wrote:
Hello
On Friday 19 January 2007 20:58, Zan Lynx wrote:
I have been running 2.6.20-rc2-mm1 without problems, but both rc3-mm1
and rc4-mm1 have been giving me these freezes. They were happening
inside X and without external console it was impossible to get anything,
plus I was reluctant to test it since the freeze sometimes requires a
full fsck.reiser4 --build-fs to recover the filesystem.
But I finally got some output in a console session. I wasn't able to
get it all, I made some notes of what I think the problem is. I may try
again later once I get netconsole working (netconsole fails as a
built-in, I'll try it as a module next).
[snip]
yes, please provide more information. Full kernel output at time of freeze is
very desirable.
Here comes a full sized bug report, as best as I can do it. This is
kernel 2.6.20-rc6-mm3 instead of rc4-mm1. Still has the problem.
Thanks for the dump.
[ 3138.456588] [8033f5de] current_atom_finish_all_fq+0x12e/0x280
[ 3138.456661] [80296510] autoremove_wake_function+0x0/0x30
[ 3138.456674] [803350ac] submit_wb_list+0x11c/0x130
[ 3138.456690] [80335409] reiser4_txn_end+0x349/0x530
[ 3138.456710] [803355f9] reiser4_txn_restart+0x9/0x20
[ 3138.456781] [80335680] force_commit_atom+0x50/0x60
[ 3138.456793] [8034cfb1] writepages_unix_file+0x671/0x780
[ 3138.456824] [802590b3] do_writepages+0x43/0x80
[ 3138.456838] [8024dbf8] __filemap_fdatawrite_range+0x58/0x70
[ 3138.456914] [8024e19d] do_fsync+0x3d/0xe0
[ 3138.456930] [802c2473] sys_msync+0x143/0x1f0
[ 3138.456945] [8025c11e] system_call+0x7e/0x83
This is waiting for IO completion, and no success because of new plugging
policy introduced by block layer folks. The attached patch should help.
Andrew, please apply.
Thanks,
Edward.
Signed-off-by: Edward Shishkin [EMAIL PROTECTED]
---
linux-2.6.20-rc6-mm3/fs/reiser4/status_flags.c |2 ++
linux-2.6.20-rc6-mm3/fs/reiser4/wander.c | 18 +++---
2 files changed, 13 insertions(+), 7 deletions(-)
--- linux-2.6.20-rc6-mm3/fs/reiser4/status_flags.c.orig
+++ linux-2.6.20-rc6-mm3/fs/reiser4/status_flags.c
@@ -63,6 +63,7 @@
}
lock_page(page);
submit_bio(READ, bio);
+ blk_replug_current_nested();
wait_on_page_locked(page);
if (!PageUptodate(page)) {
warning(green-2007,
@@ -157,6 +158,7 @@
lock_page(get_super_private(sb)-status_page); // Safe as nobody should touch our page.
/* We can block now, but we have no other choice anyway */
submit_bio(WRITE, bio);
+ blk_replug_current_nested();
return 0; // We do not wait for io to finish.
}
--- linux-2.6.20-rc6-mm3/fs/reiser4/wander.c.orig
+++ linux-2.6.20-rc6-mm3/fs/reiser4/wander.c
@@ -718,6 +718,7 @@
jnode *first, int nr, const reiser4_block_nr *block_p,
flush_queue_t *fq, int flags)
{
+ int ret = 0;
struct super_block *super = reiser4_get_current_sb();
int write_op = ( flags WRITEOUT_BARRIER ) ? WRITE_BARRIER : WRITE;
int max_blocks;
@@ -738,9 +739,10 @@
int nr_used;
bio = bio_alloc(GFP_NOIO, nr_blocks);
- if (!bio)
- return RETERR(-ENOMEM);
-
+ if (!bio) {
+ ret = RETERR(-ENOMEM);
+ break;
+ }
bio-bi_bdev = super-s_bdev;
bio-bi_sector = block * (super-s_blocksize 9);
for (nr_used = 0, i = 0; i nr_blocks; i++) {
@@ -843,8 +845,10 @@
reiser4_submit_bio(write_op, bio);
not_supported = bio_flagged(bio, BIO_EOPNOTSUPP);
bio_put(bio);
-if (not_supported)
- return -EOPNOTSUPP;
+if (not_supported) {
+ ret = -EOPNOTSUPP;
+ break;
+}
}
block += nr_used - 1;
@@ -855,8 +859,8 @@
}
nr -= nr_used;
}
-
- return 0;
+ blk_replug_current_nested();
+ return ret;
}
/* This is a procedure which recovers a contiguous sequences of disk block
Re: linux-2.6.20-rc4-mm1 Reiser4 filesystem freeze and corruption
On Thu, 2007-02-01 at 18:54 +0300, Edward Shishkin wrote: [snip] Thanks for the dump. [ 3138.456588] [8033f5de] current_atom_finish_all_fq+0x12e/0x280 [ 3138.456661] [80296510] autoremove_wake_function+0x0/0x30 [ 3138.456674] [803350ac] submit_wb_list+0x11c/0x130 [ 3138.456690] [80335409] reiser4_txn_end+0x349/0x530 [ 3138.456710] [803355f9] reiser4_txn_restart+0x9/0x20 [ 3138.456781] [80335680] force_commit_atom+0x50/0x60 [ 3138.456793] [8034cfb1] writepages_unix_file+0x671/0x780 [ 3138.456824] [802590b3] do_writepages+0x43/0x80 [ 3138.456838] [8024dbf8] __filemap_fdatawrite_range+0x58/0x70 [ 3138.456914] [8024e19d] do_fsync+0x3d/0xe0 [ 3138.456930] [802c2473] sys_msync+0x143/0x1f0 [ 3138.456945] [8025c11e] system_call+0x7e/0x83 This is waiting for IO completion, and no success because of new plugging policy introduced by block layer folks. The attached patch should help. Andrew, please apply. OK, I have been using it with your patch for many hours and it has not frozen up yet. I believe that the patch did indeed fix it. Thank you. -- Zan Lynx [EMAIL PROTECTED] signature.asc Description: This is a digitally signed message part
Re: linux-2.6.20-rc4-mm1 Reiser4 filesystem freeze and corruption
Vladimir V. Saveliev wrote: Hello On Tuesday 23 January 2007 10:38, Vince wrote: [...] I don't know if it is related, but I've had the following BUG on 2.6.20-rc4-mm1 (+ hot-fixes patches applied) : --- kernel BUG at fs/reiser4/plugin/item/extent_file_ops.c:973! This is another problem than Zan's one. The attached patch should fix it. Andrew, please apply. From: Vladimir Saveliev <[EMAIL PROTECTED]> remove_suid may open a transaction in reiser4 which is to be restarted before entering into main write loop. Signed-off-by: Vladimir Saveliev <[EMAIL PROTECTED]> I'm pleased to confirm I wasn't able to reproduce the bug with your patch applied. Regards, Vince - 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: linux-2.6.20-rc4-mm1 Reiser4 filesystem freeze and corruption
Vladimir V. Saveliev wrote: Hello On Tuesday 23 January 2007 10:38, Vince wrote: [...] I don't know if it is related, but I've had the following BUG on 2.6.20-rc4-mm1 (+ hot-fixes patches applied) : --- kernel BUG at fs/reiser4/plugin/item/extent_file_ops.c:973! This is another problem than Zan's one. The attached patch should fix it. Andrew, please apply. From: Vladimir Saveliev [EMAIL PROTECTED] remove_suid may open a transaction in reiser4 which is to be restarted before entering into main write loop. Signed-off-by: Vladimir Saveliev [EMAIL PROTECTED] I'm pleased to confirm I wasn't able to reproduce the bug with your patch applied. Regards, Vince - 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: linux-2.6.20-rc4-mm1 Reiser4 filesystem freeze and corruption
Hello On Tuesday 23 January 2007 10:38, Vince wrote: > Zan Lynx wrote: > > I have been running 2.6.20-rc2-mm1 without problems, but both rc3-mm1 > > and rc4-mm1 have been giving me these freezes. They were happening > > inside X and without external console it was impossible to get anything, > > plus I was reluctant to test it since the freeze sometimes requires a > > full fsck.reiser4 --build-fs to recover the filesystem. > > [...] > > Hi, > > I don't know if it is related, but I've had the following BUG on > 2.6.20-rc4-mm1 (+ hot-fixes patches applied) : > > --- > kernel BUG at fs/reiser4/plugin/item/extent_file_ops.c:973! This is another problem than Zan's one. The attached patch should fix it. Andrew, please apply. From: Vladimir Saveliev <[EMAIL PROTECTED]> remove_suid may open a transaction in reiser4 which is to be restarted before entering into main write loop. Signed-off-by: Vladimir Saveliev <[EMAIL PROTECTED]> diff -puN fs/reiser4/plugin/file/file.c~reiser4-restart-transaction-after-remove_suid fs/reiser4/plugin/file/file.c --- linux-2.6.20-rc3-mm1/fs/reiser4/plugin/file/file.c~reiser4-restart-transaction-after-remove_suid 2007-01-23 18:59:14.0 +0300 +++ linux-2.6.20-rc3-mm1-vs/fs/reiser4/plugin/file/file.c 2007-01-23 19:00:37.0 +0300 @@ -2175,6 +2175,8 @@ ssize_t write_unix_file(struct file *fil reiser4_exit_context(ctx); return result; } + /* remove_suid might create a transaction */ + reiser4_txn_restart(ctx); uf_info = unix_file_inode_data(inode); _ > invalid opcode: [#1] > PREEMPT > last sysfs file: /devices/pci:00/:00:13.0/eth0/statistics/collisions > Modules linked in: binfmt_misc nfs lockd sunrpc radeon drm reiser4 > ati_remote fuse usbhid snd_via82xx snd_ac97_codec ac97_bus snd_pcm_oss > snd_mixer_oss snd_pcm snd_page_alloc snd_mpu401_uart snd_seq_oss > snd_seq_midi snd_rawmidi snd_seq_midi_event snd_seq snd_timer > snd_seq_device ohci1394 ieee1394 psmouse sr_mod cdrom sg ehci_hcd > via_agp agpgart uhci_hcd usbcore i2c_viapro snd soundcore > CPU:0 > EIP:0060:[]Not tainted VLI > EFLAGS: 00010282 (2.6.20-rc4-mm1 #1) > EIP is at reiser4_write_extent+0xd5/0x626 [reiser4] > eax: ccca139c ebx: 0200 ecx: f5bec400 edx: ffe4 > esi: edi: f5bec414 ebp: da6ff274 esp: e17d7e34 > ds: 007b es: 007b fs: 00d8 gs: 0033 ss: 0068 > Process sstrip (pid: 23858, ti=e17d6000 task=d8ffc570 task.ti=e17d6000) > Stack: 00100100 00200200 00100100 0034 bf826a50 e083ff00 > > c000 da6ff2c8 dccba4c0 0005 01ff 021e > > 0004 f9b6cdad 0004 0004 > 0001 > Call Trace: > [] reiser4_update_sd+0x22/0x28 [reiser4] > [] notify_change+0x200/0x20f > [] vsscanf+0x1e2/0x3ff > [] write_unix_file+0x0/0x495 [reiser4] > [] __remove_suid+0x10/0x14 > [] mark_page_accessed+0x1c/0x2e > [] reiser4_txn_begin+0x1c/0x2e [reiser4] > [] reiser4_write_extent+0x0/0x626 [reiser4] > [] write_unix_file+0x25a/0x495 [reiser4] > [] __handle_mm_fault+0x2bd/0x79b > [] write_unix_file+0x0/0x495 [reiser4] > [] vfs_write+0x8a/0x136 > [] sys_write+0x41/0x67 > [] sysenter_past_esp+0x5f/0x85 > === > Code: 04 89 0c 24 31 c9 89 5c 24 04 e8 52 fc ff ff 31 d2 e9 59 05 00 00 > 64 a1 08 00 00 00 8b 80 b4 04 00 00 8b 40 38 83 78 08 00 74 04 <0f> 0b > eb fe 8b 8c 24 e0 00 00 00 31 db 8b 01 8b 51 04 89 c1 0f > EIP: [] reiser4_write_extent+0xd5/0x626 [reiser4] SS:ESP > 0068:e17d7e34 > <4>reiser4[sstrip(23858)]: release_unix_file > (fs/reiser4/plugin/file/file.c:2417)[vs-44]: > WARNING: out of memory? > reiser4[sstrip(23858)]: release_unix_file > (fs/reiser4/plugin/file/file.c:2417)[vs-44]: > WARNING: out of memory? > > > - 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: linux-2.6.20-rc4-mm1 Reiser4 filesystem freeze and corruption
Hello On Tuesday 23 January 2007 10:38, Vince wrote: Zan Lynx wrote: I have been running 2.6.20-rc2-mm1 without problems, but both rc3-mm1 and rc4-mm1 have been giving me these freezes. They were happening inside X and without external console it was impossible to get anything, plus I was reluctant to test it since the freeze sometimes requires a full fsck.reiser4 --build-fs to recover the filesystem. [...] Hi, I don't know if it is related, but I've had the following BUG on 2.6.20-rc4-mm1 (+ hot-fixes patches applied) : --- kernel BUG at fs/reiser4/plugin/item/extent_file_ops.c:973! This is another problem than Zan's one. The attached patch should fix it. Andrew, please apply. From: Vladimir Saveliev [EMAIL PROTECTED] remove_suid may open a transaction in reiser4 which is to be restarted before entering into main write loop. Signed-off-by: Vladimir Saveliev [EMAIL PROTECTED] diff -puN fs/reiser4/plugin/file/file.c~reiser4-restart-transaction-after-remove_suid fs/reiser4/plugin/file/file.c --- linux-2.6.20-rc3-mm1/fs/reiser4/plugin/file/file.c~reiser4-restart-transaction-after-remove_suid 2007-01-23 18:59:14.0 +0300 +++ linux-2.6.20-rc3-mm1-vs/fs/reiser4/plugin/file/file.c 2007-01-23 19:00:37.0 +0300 @@ -2175,6 +2175,8 @@ ssize_t write_unix_file(struct file *fil reiser4_exit_context(ctx); return result; } + /* remove_suid might create a transaction */ + reiser4_txn_restart(ctx); uf_info = unix_file_inode_data(inode); _ invalid opcode: [#1] PREEMPT last sysfs file: /devices/pci:00/:00:13.0/eth0/statistics/collisions Modules linked in: binfmt_misc nfs lockd sunrpc radeon drm reiser4 ati_remote fuse usbhid snd_via82xx snd_ac97_codec ac97_bus snd_pcm_oss snd_mixer_oss snd_pcm snd_page_alloc snd_mpu401_uart snd_seq_oss snd_seq_midi snd_rawmidi snd_seq_midi_event snd_seq snd_timer snd_seq_device ohci1394 ieee1394 psmouse sr_mod cdrom sg ehci_hcd via_agp agpgart uhci_hcd usbcore i2c_viapro snd soundcore CPU:0 EIP:0060:[f9b8a2e0]Not tainted VLI EFLAGS: 00010282 (2.6.20-rc4-mm1 #1) EIP is at reiser4_write_extent+0xd5/0x626 [reiser4] eax: ccca139c ebx: 0200 ecx: f5bec400 edx: ffe4 esi: edi: f5bec414 ebp: da6ff274 esp: e17d7e34 ds: 007b es: 007b fs: 00d8 gs: 0033 ss: 0068 Process sstrip (pid: 23858, ti=e17d6000 task=d8ffc570 task.ti=e17d6000) Stack: 00100100 00200200 00100100 0034 bf826a50 e083ff00 c000 da6ff2c8 dccba4c0 0005 01ff 021e 0004 f9b6cdad 0004 0004 0001 Call Trace: [f9b6cdad] reiser4_update_sd+0x22/0x28 [reiser4] [c0162459] notify_change+0x200/0x20f [c01b89ed] vsscanf+0x1e2/0x3ff [f9b75c80] write_unix_file+0x0/0x495 [reiser4] [c013630d] __remove_suid+0x10/0x14 [c013d847] mark_page_accessed+0x1c/0x2e [f9b5fbc2] reiser4_txn_begin+0x1c/0x2e [reiser4] [f9b8a20b] reiser4_write_extent+0x0/0x626 [reiser4] [f9b75eda] write_unix_file+0x25a/0x495 [reiser4] [c0142601] __handle_mm_fault+0x2bd/0x79b [f9b75c80] write_unix_file+0x0/0x495 [reiser4] [c01514e9] vfs_write+0x8a/0x136 [c0151a27] sys_write+0x41/0x67 [c0103c86] sysenter_past_esp+0x5f/0x85 === Code: 04 89 0c 24 31 c9 89 5c 24 04 e8 52 fc ff ff 31 d2 e9 59 05 00 00 64 a1 08 00 00 00 8b 80 b4 04 00 00 8b 40 38 83 78 08 00 74 04 0f 0b eb fe 8b 8c 24 e0 00 00 00 31 db 8b 01 8b 51 04 89 c1 0f EIP: [f9b8a2e0] reiser4_write_extent+0xd5/0x626 [reiser4] SS:ESP 0068:e17d7e34 4reiser4[sstrip(23858)]: release_unix_file (fs/reiser4/plugin/file/file.c:2417)[vs-44]: WARNING: out of memory? reiser4[sstrip(23858)]: release_unix_file (fs/reiser4/plugin/file/file.c:2417)[vs-44]: WARNING: out of memory? - 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: linux-2.6.20-rc4-mm1 Reiser4 filesystem freeze and corruption
Zan Lynx wrote:
I have been running 2.6.20-rc2-mm1 without problems, but both rc3-mm1
and rc4-mm1 have been giving me these freezes. They were happening
inside X and without external console it was impossible to get anything,
plus I was reluctant to test it since the freeze sometimes requires a
full fsck.reiser4 --build-fs to recover the filesystem.
> [...]
Hi,
I don't know if it is related, but I've had the following BUG on
2.6.20-rc4-mm1 (+ hot-fixes patches applied) :
---
kernel BUG at fs/reiser4/plugin/item/extent_file_ops.c:973!
invalid opcode: [#1]
PREEMPT
last sysfs file: /devices/pci:00/:00:13.0/eth0/statistics/collisions
Modules linked in: binfmt_misc nfs lockd sunrpc radeon drm reiser4
ati_remote fuse usbhid snd_via82xx snd_ac97_codec ac97_bus snd_pcm_oss
snd_mixer_oss snd_pcm snd_page_alloc snd_mpu401_uart snd_seq_oss
snd_seq_midi snd_rawmidi snd_seq_midi_event snd_seq snd_timer
snd_seq_device ohci1394 ieee1394 psmouse sr_mod cdrom sg ehci_hcd
via_agp agpgart uhci_hcd usbcore i2c_viapro snd soundcore
CPU:0
EIP:0060:[]Not tainted VLI
EFLAGS: 00010282 (2.6.20-rc4-mm1 #1)
EIP is at reiser4_write_extent+0xd5/0x626 [reiser4]
eax: ccca139c ebx: 0200 ecx: f5bec400 edx: ffe4
esi: edi: f5bec414 ebp: da6ff274 esp: e17d7e34
ds: 007b es: 007b fs: 00d8 gs: 0033 ss: 0068
Process sstrip (pid: 23858, ti=e17d6000 task=d8ffc570 task.ti=e17d6000)
Stack: 00100100 00200200 00100100 0034 bf826a50 e083ff00
c000 da6ff2c8 dccba4c0 0005 01ff 021e
0004 f9b6cdad 0004 0004
0001
Call Trace:
[] reiser4_update_sd+0x22/0x28 [reiser4]
[] notify_change+0x200/0x20f
[] vsscanf+0x1e2/0x3ff
[] write_unix_file+0x0/0x495 [reiser4]
[] __remove_suid+0x10/0x14
[] mark_page_accessed+0x1c/0x2e
[] reiser4_txn_begin+0x1c/0x2e [reiser4]
[] reiser4_write_extent+0x0/0x626 [reiser4]
[] write_unix_file+0x25a/0x495 [reiser4]
[] __handle_mm_fault+0x2bd/0x79b
[] write_unix_file+0x0/0x495 [reiser4]
[] vfs_write+0x8a/0x136
[] sys_write+0x41/0x67
[] sysenter_past_esp+0x5f/0x85
===
Code: 04 89 0c 24 31 c9 89 5c 24 04 e8 52 fc ff ff 31 d2 e9 59 05 00 00
64 a1 08 00 00 00 8b 80 b4 04 00 00 8b 40 38 83 78 08 00 74 04 <0f> 0b
eb fe 8b 8c 24 e0 00 00 00 31 db 8b 01 8b 51 04 89 c1 0f
EIP: [] reiser4_write_extent+0xd5/0x626 [reiser4] SS:ESP
0068:e17d7e34
<4>reiser4[sstrip(23858)]: release_unix_file
(fs/reiser4/plugin/file/file.c:2417)[vs-44]:
WARNING: out of memory?
reiser4[sstrip(23858)]: release_unix_file
(fs/reiser4/plugin/file/file.c:2417)[vs-44]:
WARNING: out of memory?
-
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: linux-2.6.20-rc4-mm1 Reiser4 filesystem freeze and corruption
Zan Lynx wrote:
I have been running 2.6.20-rc2-mm1 without problems, but both rc3-mm1
and rc4-mm1 have been giving me these freezes. They were happening
inside X and without external console it was impossible to get anything,
plus I was reluctant to test it since the freeze sometimes requires a
full fsck.reiser4 --build-fs to recover the filesystem.
[...]
Hi,
I don't know if it is related, but I've had the following BUG on
2.6.20-rc4-mm1 (+ hot-fixes patches applied) :
---
kernel BUG at fs/reiser4/plugin/item/extent_file_ops.c:973!
invalid opcode: [#1]
PREEMPT
last sysfs file: /devices/pci:00/:00:13.0/eth0/statistics/collisions
Modules linked in: binfmt_misc nfs lockd sunrpc radeon drm reiser4
ati_remote fuse usbhid snd_via82xx snd_ac97_codec ac97_bus snd_pcm_oss
snd_mixer_oss snd_pcm snd_page_alloc snd_mpu401_uart snd_seq_oss
snd_seq_midi snd_rawmidi snd_seq_midi_event snd_seq snd_timer
snd_seq_device ohci1394 ieee1394 psmouse sr_mod cdrom sg ehci_hcd
via_agp agpgart uhci_hcd usbcore i2c_viapro snd soundcore
CPU:0
EIP:0060:[f9b8a2e0]Not tainted VLI
EFLAGS: 00010282 (2.6.20-rc4-mm1 #1)
EIP is at reiser4_write_extent+0xd5/0x626 [reiser4]
eax: ccca139c ebx: 0200 ecx: f5bec400 edx: ffe4
esi: edi: f5bec414 ebp: da6ff274 esp: e17d7e34
ds: 007b es: 007b fs: 00d8 gs: 0033 ss: 0068
Process sstrip (pid: 23858, ti=e17d6000 task=d8ffc570 task.ti=e17d6000)
Stack: 00100100 00200200 00100100 0034 bf826a50 e083ff00
c000 da6ff2c8 dccba4c0 0005 01ff 021e
0004 f9b6cdad 0004 0004
0001
Call Trace:
[f9b6cdad] reiser4_update_sd+0x22/0x28 [reiser4]
[c0162459] notify_change+0x200/0x20f
[c01b89ed] vsscanf+0x1e2/0x3ff
[f9b75c80] write_unix_file+0x0/0x495 [reiser4]
[c013630d] __remove_suid+0x10/0x14
[c013d847] mark_page_accessed+0x1c/0x2e
[f9b5fbc2] reiser4_txn_begin+0x1c/0x2e [reiser4]
[f9b8a20b] reiser4_write_extent+0x0/0x626 [reiser4]
[f9b75eda] write_unix_file+0x25a/0x495 [reiser4]
[c0142601] __handle_mm_fault+0x2bd/0x79b
[f9b75c80] write_unix_file+0x0/0x495 [reiser4]
[c01514e9] vfs_write+0x8a/0x136
[c0151a27] sys_write+0x41/0x67
[c0103c86] sysenter_past_esp+0x5f/0x85
===
Code: 04 89 0c 24 31 c9 89 5c 24 04 e8 52 fc ff ff 31 d2 e9 59 05 00 00
64 a1 08 00 00 00 8b 80 b4 04 00 00 8b 40 38 83 78 08 00 74 04 0f 0b
eb fe 8b 8c 24 e0 00 00 00 31 db 8b 01 8b 51 04 89 c1 0f
EIP: [f9b8a2e0] reiser4_write_extent+0xd5/0x626 [reiser4] SS:ESP
0068:e17d7e34
4reiser4[sstrip(23858)]: release_unix_file
(fs/reiser4/plugin/file/file.c:2417)[vs-44]:
WARNING: out of memory?
reiser4[sstrip(23858)]: release_unix_file
(fs/reiser4/plugin/file/file.c:2417)[vs-44]:
WARNING: out of memory?
-
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: linux-2.6.20-rc4-mm1 Reiser4 filesystem freeze and corruption
Hello On Friday 19 January 2007 20:58, Zan Lynx wrote: > I have been running 2.6.20-rc2-mm1 without problems, but both rc3-mm1 > and rc4-mm1 have been giving me these freezes. They were happening > inside X and without external console it was impossible to get anything, > plus I was reluctant to test it since the freeze sometimes requires a > full fsck.reiser4 --build-fs to recover the filesystem. > > But I finally got some output in a console session. I wasn't able to > get it all, I made some notes of what I think the problem is. I may try > again later once I get netconsole working (netconsole fails as a > built-in, I'll try it as a module next). > > 1 lock held by pdflush/185: > #0: (>s_umount_key#15) ... writeback_inodes+0x89 > > 3 locks held by realsync/12942: > #0: (>s_umount_key#15) at ... __sync_inodes+0x78 > #1: (>commit_mutex) ... reiser4_txn_end+0x37a > #2: (>mutex) ... synchronize_qrcu+0x19 > > So, I *think* the problem is two locks on s_umount_key#15. Does that > sound likely? I also noticed QRCU may be involved. > > Perhaps someone will look at this and instantly know what the problem > is. > > If not, I'll be following up with more details like .config and perhaps > a full sysrq-T dump as soon as that fsck finishes. > yes, please provide more information. Full kernel output at time of freeze is very desirable. - 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: linux-2.6.20-rc4-mm1 Reiser4 filesystem freeze and corruption
Zan Lynx wrote: I have been running 2.6.20-rc2-mm1 without problems, but both rc3-mm1 and rc4-mm1 have been giving me these freezes. I didn't investigate it in details yet, other file systems also freeze for me: http://marc.theaimsgroup.com/?l=linux-kernel=116809282829254=2 They were happening inside X and without external console it was impossible to get anything, plus I was reluctant to test it since the freeze sometimes requires a full fsck.reiser4 --build-fs to recover the filesystem. Why did you decide to recover? Got oops after mount, or? But I finally got some output in a console session. I wasn't able to get it all, I made some notes of what I think the problem is. I may try again later once I get netconsole working (netconsole fails as a built-in, I'll try it as a module next). 1 lock held by pdflush/185: #0: (>s_umount_key#15) ... writeback_inodes+0x89 3 locks held by realsync/12942: #0: (>s_umount_key#15) at ... __sync_inodes+0x78 #1: (>commit_mutex) ... reiser4_txn_end+0x37a #2: (>mutex) ... synchronize_qrcu+0x19 So, I *think* the problem is two locks on s_umount_key#15. Does that sound likely? I also noticed QRCU may be involved. Perhaps someone will look at this and instantly know what the problem is. If not, I'll be following up with more details like .config and perhaps a full sysrq-T dump as soon as that fsck finishes. - 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/
linux-2.6.20-rc4-mm1 Reiser4 filesystem freeze and corruption
I have been running 2.6.20-rc2-mm1 without problems, but both rc3-mm1 and rc4-mm1 have been giving me these freezes. They were happening inside X and without external console it was impossible to get anything, plus I was reluctant to test it since the freeze sometimes requires a full fsck.reiser4 --build-fs to recover the filesystem. But I finally got some output in a console session. I wasn't able to get it all, I made some notes of what I think the problem is. I may try again later once I get netconsole working (netconsole fails as a built-in, I'll try it as a module next). 1 lock held by pdflush/185: #0: (>s_umount_key#15) ... writeback_inodes+0x89 3 locks held by realsync/12942: #0: (>s_umount_key#15) at ... __sync_inodes+0x78 #1: (>commit_mutex) ... reiser4_txn_end+0x37a #2: (>mutex) ... synchronize_qrcu+0x19 So, I *think* the problem is two locks on s_umount_key#15. Does that sound likely? I also noticed QRCU may be involved. Perhaps someone will look at this and instantly know what the problem is. If not, I'll be following up with more details like .config and perhaps a full sysrq-T dump as soon as that fsck finishes. signature.asc Description: This is a digitally signed message part
linux-2.6.20-rc4-mm1 Reiser4 filesystem freeze and corruption
I have been running 2.6.20-rc2-mm1 without problems, but both rc3-mm1 and rc4-mm1 have been giving me these freezes. They were happening inside X and without external console it was impossible to get anything, plus I was reluctant to test it since the freeze sometimes requires a full fsck.reiser4 --build-fs to recover the filesystem. But I finally got some output in a console session. I wasn't able to get it all, I made some notes of what I think the problem is. I may try again later once I get netconsole working (netconsole fails as a built-in, I'll try it as a module next). 1 lock held by pdflush/185: #0: (type-s_umount_key#15) ... writeback_inodes+0x89 3 locks held by realsync/12942: #0: (type-s_umount_key#15) at ... __sync_inodes+0x78 #1: (mgr-commit_mutex) ... reiser4_txn_end+0x37a #2: (qp-mutex) ... synchronize_qrcu+0x19 So, I *think* the problem is two locks on s_umount_key#15. Does that sound likely? I also noticed QRCU may be involved. Perhaps someone will look at this and instantly know what the problem is. If not, I'll be following up with more details like .config and perhaps a full sysrq-T dump as soon as that fsck finishes. signature.asc Description: This is a digitally signed message part
Re: linux-2.6.20-rc4-mm1 Reiser4 filesystem freeze and corruption
Zan Lynx wrote: I have been running 2.6.20-rc2-mm1 without problems, but both rc3-mm1 and rc4-mm1 have been giving me these freezes. I didn't investigate it in details yet, other file systems also freeze for me: http://marc.theaimsgroup.com/?l=linux-kernelm=116809282829254w=2 They were happening inside X and without external console it was impossible to get anything, plus I was reluctant to test it since the freeze sometimes requires a full fsck.reiser4 --build-fs to recover the filesystem. Why did you decide to recover? Got oops after mount, or? But I finally got some output in a console session. I wasn't able to get it all, I made some notes of what I think the problem is. I may try again later once I get netconsole working (netconsole fails as a built-in, I'll try it as a module next). 1 lock held by pdflush/185: #0: (type-s_umount_key#15) ... writeback_inodes+0x89 3 locks held by realsync/12942: #0: (type-s_umount_key#15) at ... __sync_inodes+0x78 #1: (mgr-commit_mutex) ... reiser4_txn_end+0x37a #2: (qp-mutex) ... synchronize_qrcu+0x19 So, I *think* the problem is two locks on s_umount_key#15. Does that sound likely? I also noticed QRCU may be involved. Perhaps someone will look at this and instantly know what the problem is. If not, I'll be following up with more details like .config and perhaps a full sysrq-T dump as soon as that fsck finishes. - 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: linux-2.6.20-rc4-mm1 Reiser4 filesystem freeze and corruption
Hello On Friday 19 January 2007 20:58, Zan Lynx wrote: I have been running 2.6.20-rc2-mm1 without problems, but both rc3-mm1 and rc4-mm1 have been giving me these freezes. They were happening inside X and without external console it was impossible to get anything, plus I was reluctant to test it since the freeze sometimes requires a full fsck.reiser4 --build-fs to recover the filesystem. But I finally got some output in a console session. I wasn't able to get it all, I made some notes of what I think the problem is. I may try again later once I get netconsole working (netconsole fails as a built-in, I'll try it as a module next). 1 lock held by pdflush/185: #0: (type-s_umount_key#15) ... writeback_inodes+0x89 3 locks held by realsync/12942: #0: (type-s_umount_key#15) at ... __sync_inodes+0x78 #1: (mgr-commit_mutex) ... reiser4_txn_end+0x37a #2: (qp-mutex) ... synchronize_qrcu+0x19 So, I *think* the problem is two locks on s_umount_key#15. Does that sound likely? I also noticed QRCU may be involved. Perhaps someone will look at this and instantly know what the problem is. If not, I'll be following up with more details like .config and perhaps a full sysrq-T dump as soon as that fsck finishes. yes, please provide more information. Full kernel output at time of freeze is very desirable. - 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/
