From: Oleg Drokin <green@namesys.com>
To: pegasus@nerv.eu.org
Cc: reiserfs mailing list <reiserfs-list@namesys.com>
Subject: Re: is this a known bug?
Date: Thu, 24 Jul 2003 19:05:48 +0400 [thread overview]
Message-ID: <20030724150548.GA21786@namesys.com> (raw)
In-Reply-To: <20030723235435.3C63E9C91@mail.animeslovenija.org>
Hello!
On Thu, Jul 24, 2003 at 01:54:35AM +0200, pegasus@nerv.eu.org wrote:
> [usb-ohci:sohci_device_operations+781321/95136603] .LC62 [reiserfs] 0xc3
> Jul 14 13:25:41 mai-stor2 kernel: Call Trace: [<f8a456d5>] .LC62 [reiserfs] 0xc3
> Jul 14 13:25:41 mai-stor2 kernel: [<f8a3ad1e>] journal_mark_dirty [reiserfs] 0x13e
> Jul 14 13:25:41 mai-stor2 kernel: [<f8a43d60>] .LC93 [reiserfs] 0x27a0
> Jul 14 13:25:41 mai-stor2 kernel: [<f8a1f100>] reiserfs_free_block [reiserfs] 0xa0
> Jul 14 13:25:41 mai-stor2 kernel: [<f8a34bb0>] prepare_for_delete_or_cut
> [reiserfs] 0x760
> Jul 14 13:25:41 mai-stor2 kernel: [<f8a22417>] free_thrown [reiserfs] 0x57
> Jul 14 13:25:41 mai-stor2 kernel: [<f8a22689>] do_balance [reiserfs] 0xe9
> Jul 14 13:25:41 mai-stor2 kernel: [<f8a356ca>] reiserfs_cut_from_item [reiserfs]
Yes, I know this one. It is journal overflow we fixed in 2.4.21 or thereabout.
If you use reiserfs, you really do not want to depend on RedHat's 2.4.9 kernel,
you'd better get some recent stuff (or talk us into backporting fixes to 2.4.9?
that might work if you have enough money ;) )
Bye,
Oleg
next prev parent reply other threads:[~2003-07-24 15:05 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-07-23 23:54 is this a known bug? pegasus
2003-07-24 2:11 ` Hans Reiser
2003-07-24 10:46 ` Nikita Danilov
2003-07-24 15:05 ` Oleg Drokin [this message]
-- strict thread matches above, loose matches on Subject: below --
2006-12-05 22:32 Is " Huang, Eric
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=20030724150548.GA21786@namesys.com \
--to=green@namesys.com \
--cc=pegasus@nerv.eu.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.