From: Hans Reiser <reiser@namesys.com>
To: Steve Felt <steve@circlepix.com>
Cc: reiserfs-list@namesys.com, vs <vs@thebsh.namesys.com>
Subject: Re: [Fwd: kernel bug]
Date: Tue, 22 Feb 2005 10:45:00 -0800 [thread overview]
Message-ID: <421B7DAC.70208@namesys.com> (raw)
In-Reply-To: <1109096270.7723.3.camel@sfelt>
Vladimir will get back to you on this tomorrow.
Hans
Steve Felt wrote:
>I'm submitting this again. Any help is greatly appreciated!
>
>I am open to any suggestions and I DO appreciate the hard work that's
>gone into ReiserFS. I'm not above paying for the core developers' help,
>if it comes to that (yes, I've read http://www.namesys.com/support.html and
>http://www.namesys.com/faq.html ). Also, I am open to suggestions, such as "you need to recompile the
>kernel with..." or "why don't you read..." or "the hardware has to be
>replaced..."
>
>I'm getting the following "kernel BUG" on SuSE 9.1 Pro (and on 9.2):
>
>[first, the hw/sw details]
> LSI 929x (7202xp) HBA (fiber channel card)
>
> Large array of drives (1.4TB)
>
> cat /proc/meminfo
> MemTotal: 1036148 kB
>
> cat /proc/cpuinfo
> processor : 0
> vendor_id : AuthenticAMD
> cpu family : 6
> model : 6
> model name : AMD Athlon(tm) MP 2000+
>
> cat /proc/mpt/version
> mptlinux-3.01.14.23
> Fusion MPT base driver
> Fusion MPT SCSI host driver
>
> cat /etc/SuSE-release
> SuSE Linux 9.1 (i586)
> VERSION = 9.1
>
> dmesg | grep -i reiser | grep sda
> ReiserFS: sda1: found reiserfs format "3.6" with standard journal
> ReiserFS: sda1: using ordered data mode
> ReiserFS: sda1: journal params: device sda1, size 8192, journal first
>block 18, max trans len 1024, max batch 900, max commit age 30, max
>trans age 30
> ReiserFS: sda1: checking transaction log (sda1)
> reiserfs: disabling flush barriers on sda1
> ReiserFS: sda1: Using r5 hash to sort names
>
>Symptoms:
> I can do an initial rsync of a large amount of data (~300MB) from
>another host, but subsequent rsync attempts fail after about 1hour (when
>files are actually being copied over/ replaced etc.) with the following:
>
> kernel: ------------[ cut here ]------------
> kernel: kernel BUG at fs/reiserfs/namei.c:1291!
> kernel: invalid operand: 0000 [#1]
> kernel: CPU: 0
> kernel: EIP: 0060:[__crc_device_suspend+2680266/3186568] Not tainted
> kernel: EIP: 0060:[] Not tainted
> kernel: EFLAGS: 00010296 (2.6.5-7.111.19-default)
> kernel: EIP is at reiserfs_rename+0x299/0x7d0 [reiserfs]
> kernel: eax: ffffffff ebx: 00008000 ecx: e88a7cf0 edx: e88a7cf0
> kernel: esi: 00000000 edi: e88a7ca0 ebp: e4aa5dcc esp: e88a7be8
> kernel: ds: 007b es: 007b ss: 0068
> kernel: Process rsync (pid: 3062, threadinfo=e88a6000 task=f13de220)
> kernel: Stack: 00000009 00000009 00000001 00008180 f5b49018 00001000
>00000000 00000000
> kernel: 00000000 f5b4bb4c e4a84080 f5b4bb4c 00000000 00000000 c1a0e400
>00000001
> kernel: 00000000 0000003b 00002b5b 00000000 00000000 e88a7c3c e88a7c3c
>e88a7d50
> kernel: Call Trace:
> kernel: [__crc_device_suspend+2716835/3186568]
>reiserfs_allocate_blocks_for_region+0xf32/0x1320 [reiserfs]
> kernel: [] reiserfs_allocate_blocks_for_region+0xf32/0x1320 [reiserfs]
> kernel: [__crc_device_suspend+2692640/3186568] inode2sd+0x12f/0x140
>[reiserfs]
> kernel: [] inode2sd+0x12f/0x140 [reiserfs]
> kernel: [__crc_device_suspend+2772063/3186568] pathrelse+0x1e/0x30
>[reiserfs]
> kernel: [] pathrelse+0x1e/0x30 [reiserfs]
> kernel: [autoremove_wake_function+0/48]
>autoremove_wake_function+0x0/0x30
> kernel: [] autoremove_wake_function+0x0/0x30
> kernel: [__crc_device_suspend+2807928/3186568]
>do_journal_end+0x1f7/0xc40 [reiserfs]
> kernel: [] do_journal_end+0x1f7/0xc40 [reiserfs]
> kernel: [__crc_device_suspend+2812134/3186568] journal_end+0x65/0xc0
>[reiserfs]
> kernel: [] journal_end+0x65/0xc0 [reiserfs]
> kernel: [__crc_device_suspend+2719325/3186568]
>reiserfs_file_write+0x5cc/0x639 [reiserfs]
> kernel: [] reiserfs_file_write+0x5cc/0x639 [reiserfs]
> kernel: [vfs_rename_other+149/272] vfs_rename_other+0x95/0x110
> kernel: [] vfs_rename_other+0x95/0x110
> kernel: [vfs_rename+335/896] vfs_rename+0x14f/0x380
> kernel: [] vfs_rename+0x14f/0x380
> kernel: [sys_rename+575/704] sys_rename+0x23f/0x2c0
> kernel: [] sys_rename+0x23f/0x2c0
> kernel: [__pollwait+0/208] __pollwait+0x0/0xd0
> kernel: [] __pollwait+0x0/0xd0
> kernel: [sys_close+112/208] sys_close+0x70/0xd0
> kernel: [] sys_close+0x70/0xd0
> kernel: [sysenter_past_esp+82/121] sysenter_past_esp+0x52/0x79
> kernel: [] sysenter_past_esp+0x52/0x79
> kernel:
> kernel: Code: 0f 0b 0b 05 35 d0 10 f9 8b 84 24 58 02 00 00 8b 8c c4 60
>02
>
>
>--------------------------------------------
>
>Thanks for your help!
>("Spasibo za pomosh'!")
>
>-steve
>
>
>
>
>
>
next prev parent reply other threads:[~2005-02-22 18:45 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-02-22 18:17 [Fwd: kernel bug] Steve Felt
2005-02-22 18:45 ` Hans Reiser [this message]
2005-02-25 12:59 ` Mikhail L. Titov
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=421B7DAC.70208@namesys.com \
--to=reiser@namesys.com \
--cc=reiserfs-list@namesys.com \
--cc=steve@circlepix.com \
--cc=vs@thebsh.namesys.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is 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.