From: Alex Zarochentsev <zam@namesys.com>
To: Henning Westerholt <henning-04@die.informatik.uni-siegen.de>
Cc: Markus T?rnqvist <mjt@nysv.org>, reiserfs-list@namesys.com
Subject: Re: Problem with the latest auto snapshot
Date: Tue, 15 Jun 2004 12:06:53 +0400 [thread overview]
Message-ID: <20040615080653.GY8091@backtop.namesys.com> (raw)
In-Reply-To: <200406131537.54853.henning-04@die.informatik.uni-siegen.de>
On Sun, Jun 13, 2004 at 03:37:54PM +0200, Henning Westerholt wrote:
> Am Samstag, 12. Juni 2004 21:46 schrieb Markus T?rnqvist:
> > I had something similar, with an old auto-snapshot, but I didn't get
> > those log messages. It also repeated on, 2004.06.09 under some mild load,
> > compiling .11-19.36 and doing a dist-upgrade. I'll dig out some traces
> > if it still repeats with this kernel, as they seem to have systematically
> > receeded.
> >
> > I wonder if we have something different concerning debug?
> > mjt@shrike:~$ zgrep -i reiser4 /proc/config.gz
> > [snip]
>
> Hello Markus,
>
> i'm using the same reiser4 config like you.
>
> I just rebuild the partition, and start a small compile job. After them i
> started a fsck. It reported a new fatal error about a broken node. I attached
> the output from fsck. I could reproduce this error two times.
new fsck 0.5.5 is available for testing
(http://www.namesys.com/snapshots/2004.06.14-internal.testing/), please try it.
Can you also enable CONFIG_REISER4_CHECK and CONFIG_REISER4_DEBUG? It may help to
catch a bug faster.
--
Alex.
next prev parent reply other threads:[~2004-06-15 8:06 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-06-12 19:31 Problem with the latest auto snapshot Henning Westerholt
2004-06-12 19:46 ` mjt
2004-06-13 13:37 ` Henning Westerholt
2004-06-13 13:43 ` mjt
2004-06-14 9:13 ` Henning Westerholt
2004-06-14 9:21 ` mjt
2004-06-14 18:08 ` Hans Reiser
2004-06-15 8:06 ` Alex Zarochentsev [this message]
2004-06-15 8:14 ` Alex Zarochentsev
2004-06-15 16:50 ` Henning Westerholt
2004-06-15 17:44 ` Alex Zarochentsev
2004-06-15 18:19 ` Henning Westerholt
2004-06-14 18:22 ` Alex Zarochentsev
2004-06-14 22:55 ` Henning Westerholt
2004-06-15 4:34 ` Alex Zarochentsev
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=20040615080653.GY8091@backtop.namesys.com \
--to=zam@namesys.com \
--cc=henning-04@die.informatik.uni-siegen.de \
--cc=mjt@nysv.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.