From: Nikita Danilov <Nikita@Namesys.COM>
To: "Cheng" <geek@geekbone.org>
Cc: "Martin J. Bligh" <mbligh@aracnet.com>,
Andrew Morton <akpm@osdl.org>,
Linux Kernel Mailing List <Linux-Kernel@Vger.Kernel.ORG>,
Reiserfs developers mail-list <Reiserfs-Dev@Namesys.COM>
Subject: Re: Fw: [Bug 2084] New: Reiserfs causes sytem hang
Date: Fri, 13 Feb 2004 13:57:21 +0300 [thread overview]
Message-ID: <16428.44433.503851.536857@laputa.namesys.com> (raw)
In-Reply-To: <20040212184352.59ef8d7f.akpm@osdl.org>
>
> http://bugme.osdl.org/show_bug.cgi?id=2084
>
> Summary: Reiserfs causes sytem hang
> Kernel Version: 2.6.2
> Status: NEW
> Severity: high
> Owner: reiserfs-dev@namesys.com
> Submitter: geek@geekbone.org
>
>
> Distribution:
> Debian Sarge
>
> Hardware Environment:
> Whitebox P4 Xeon server with Tyan S2723 Motherboard and 3ware 7506 Raid 5 card
>
> Software Environment:
> self compiled plain Kernel 2.6.2
> Reiserfs
> Raid 5
>
> Problem Description:
> rsync was running as scheduled in cron normally and system suddenly hang up
> with the following kernel message.
Hello, Cheng,
were there any other error/warning messages in the log just before BUG?
>
> ------------[ cut here ]------------
> kernel BUG at fs/reiserfs/namei.c:1198!
> invalid operand: 0000 [#1]
> CPU: 1
> EIP: 0060:[<c01ac359>] Not tainted
> EFLAGS: 00010297
> EIP is at reiserfs_rename+0x2ec/0xaa9
> eax: 00000000 ebx: f0d81680 ecx: d66c7e50 edx: 00000000
> esi: 00000000 edi: d66c7d10 ebp: ccad0338 esp: d66c7c58
Nikita.
parent reply other threads:[~2004-02-13 10:57 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <20040212184352.59ef8d7f.akpm@osdl.org>]
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=16428.44433.503851.536857@laputa.namesys.com \
--to=nikita@namesys.com \
--cc=Linux-Kernel@Vger.Kernel.ORG \
--cc=Reiserfs-Dev@Namesys.COM \
--cc=akpm@osdl.org \
--cc=geek@geekbone.org \
--cc=mbligh@aracnet.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®