All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Vladimir V. Saveliev" <vs@namesys.com>
To: Guillaume Pelat <gp@winch-hebergement.net>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Reiserfs 3.6 + quota enabled, crash on delete (or maybe truncate)
Date: Fri, 05 Aug 2005 13:38:01 +0400	[thread overview]
Message-ID: <42F33379.5030804@namesys.com> (raw)
In-Reply-To: <42F27161.2020702@winch-hebergement.net>

[-- Attachment #1: Type: text/plain, Size: 2488 bytes --]

Hello

Guillaume Pelat wrote:
> Hi,
> 
>  >> I'm having a crash with reiserfs 3.6 + user quota enabled, on
>  >> 2.6.11.10 kernel (no smp), apparently when deleting files (or maybe
>  >>  during a runcate operation). The problem seems to happen under high
>  >>  load.
>  >> When the error occurs, all the processes accessing the reiserfs
>  >> partition seems to hang. This problem happened several times on
>  >> different servers (having the same hardware configuration) during
>  >> last weeks.
> 
>  > The attached patch should help to get rid of clm-2100 and to avoid
>  > crash.
>  > Also, I think you should reiserfsck sda3.
> 
> Thanks for your answer. I tried the patch attached to your mail, but it 
> seems that it doesnt solve my problem :)
> The error also occured after i did a reiserfsck on sda3, I also tested 
> 2.6.13-rc4 with your patch applied, without success (the error also 
> occured on serveral servers having the same hardware configuration).
> 

Would you, please, try to reproduce the problem having reiserfs check mode on.
(it is File systems->Reiserfs support->Enable reiserfs debug mode in kernel configuration)
and with attached patch.

> Here are the error logs:
> 

Was there anything about reiserfs in the logs before this dump?

> ------------[ cut here ]------------
> kernel BUG at fs/reiserfs/prints.c:362!
> invalid operand: 0000 [#1]
> CPU:    0
> EIP:    0060:[<c019ae2f>]    Not tainted VLI
> EFLAGS: 00010296   (2.6.13-rc4-endy)
> EIP is at reiserfs_panic+0x4f/0x80
> eax: 00000053   ebx: c02b8fde   ecx: 00000000   edx: c02dfdac
> esi: 00000000   edi: 00000140   ebp: e75b383c   esp: e75b3824
> ds: 007b   es: 007b   ss: 0068
> Process pure-ftpd (pid: 12771, threadinfo=e75b2000 task=f091d530)
> Stack: c02bd610 c02b8fde c03acdc0 00000fa0 c0971154 00000002 e75b3864 
> c01ac75f
>        00000000 c02bf89c 00000fa0 00000002 00020000 00000000 c097101c 
> 00000000
>        e75b38b8 c01939d3 c097101c 00000fd0 00000000 00000000 00000000 
> 00000000
> Call Trace:
>  [<c0102e5f>] show_stack+0x7f/0xa0
>  [<c0103002>] show_registers+0x152/0x1c0
>  [<c01031f8>] die+0xc8/0x140
>  [<c0103325>] do_trap+0xb5/0xc0
>  [<c010366c>] do_invalid_op+0xbc/0xd0
>  [<c0102aa3>] error_code+0x4f/0x54
>  [<c01ac75f>] direntry_check_left+0x8f/0x90
>  [<c01939d3>] get_num_ver+0x303/0x350
>  [<c01949ac>] ip_check_balance+0x3dc/0xbc0
>  [<c0195948>] check_balance+0x58/0x70
>  [<c019623b>] fix_nodes+0x15b/0x420
>  [<c01a2daf>] reiserfs_cut_from_item+0x10f/0x570

[-- Attachment #2: reiserfs-panic-fix.patch --]
[-- Type: text/plain, Size: 694 bytes --]

 fs/reiserfs/prints.c |    3 ---
 1 files changed, 3 deletions(-)

diff -puN fs/reiserfs/prints.c~reiserfs-panic-fix fs/reiserfs/prints.c
--- linux-2.6.13-rc4-mm1/fs/reiserfs/prints.c~reiserfs-panic-fix	2005-08-05 13:36:09.947391212 +0400
+++ linux-2.6.13-rc4-mm1-vs/fs/reiserfs/prints.c	2005-08-05 13:36:23.346671407 +0400
@@ -359,9 +359,6 @@ void reiserfs_panic(struct super_block *
 	do_reiserfs_warning(fmt);
 	printk(KERN_EMERG "REISERFS: panic (device %s): %s\n",
 	       reiserfs_bdevname(sb), error_buf);
-	BUG();
-
-	/* this is not actually called, but makes reiserfs_panic() "noreturn" */
 	panic("REISERFS: panic (device %s): %s\n",
 	      reiserfs_bdevname(sb), error_buf);
 }

_

  reply	other threads:[~2005-08-05  9:39 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-08-04 19:49 Reiserfs 3.6 + quota enabled, crash on delete (or maybe truncate) Guillaume Pelat
2005-08-05  9:38 ` Vladimir V. Saveliev [this message]
2005-08-09 21:27   ` Guillaume Pelat
2005-08-10 13:06     ` Jan Kara

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=42F33379.5030804@namesys.com \
    --to=vs@namesys.com \
    --cc=gp@winch-hebergement.net \
    --cc=linux-kernel@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.