From: Alexander Zarochentsev <zam@namesys.com>
To: reiserfs-list@namesys.com
Cc: Kelvie Wong <kelvie@ieee.org>
Subject: Re: Kernel Panic with reiserfs during a rm command; complains about j_len too long during journal_mark_dirty
Date: Tue, 11 Apr 2006 09:44:39 +0400 [thread overview]
Message-ID: <200604110944.39591.zam@namesys.com> (raw)
In-Reply-To: <4430B34C.9040509@ieee.org>
Hi,
On Monday 03 April 2006 09:31, Kelvie Wong wrote:
> Attached is the relevant dmesg output; I have ran rebuild-tree, and
> when I try to rm certain files, I get the same error (a segfault),
> then it hangs.
>
> Tell me if you need more information; I'd really like to know if this
> is a kernel/reiserfs problem, or rather if I need a new hard drive.
It is a reiserfs bug, please use 2.6.17-rc1 which has a fix for it,
or apply
ftp.kernel.org:/pub/linux/kernel/people/akpm/patches/2.6/2.6.16/2.6.16-mm1/broken-out/reiserfs-fix-transaction-overflowing.patch
--
Alex.
next prev parent reply other threads:[~2006-04-11 5:44 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-04-03 5:31 Kernel Panic with reiserfs during a rm command; complains about j_len too long during journal_mark_dirty Kelvie Wong
2006-04-11 5:44 ` Alexander Zarochentsev [this message]
2006-04-11 18:50 ` Kelvie Wong
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=200604110944.39591.zam@namesys.com \
--to=zam@namesys.com \
--cc=kelvie@ieee.org \
--cc=reiserfs-list@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.