From: Christian Mayrhuber <christian.mayrhuber@gmx.net>
To: reiserfs-list@namesys.com
Subject: Re: Strange errors with 2.4.22 patches (from Chris) and bonnie++
Date: Mon, 01 Dec 2003 17:00:23 +0100 [thread overview]
Message-ID: <3FCB6597.8010604@gmx.net> (raw)
In-Reply-To: <1070285425.12810.2.camel@tiny.suse.com>
> I've had to remove reiserfs-jh-3, it caused problems in the suse kernel
> and a week or so of hunting wasn't able to track it down. All my effort
> right now is on fixing it in my 2.6 branch.
Nice, to see data logging in 2.6.
So one is more safe without reiserfs-jh-3 than with it?
I sometimes get permission denied messages on some files if I read from
LVM snapshots. This happens rather seldom and goes away if I redo a
snapshot. I could ask an admin to have a look for the console messsages,
if this is the same problem you are facing.
I had no corruption.
--
lg, Chris
next prev parent reply other threads:[~2003-12-01 16:00 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <bq8f7u$ufn$1@sea.gmane.org>
2003-11-28 16:46 ` Strange errors with 2.4.22 patches (from Chris) and bonnie++ Hans Reiser
2003-11-29 19:27 ` Christian Mayrhuber
2003-12-01 13:30 ` Chris Mason
2003-12-01 16:00 ` Christian Mayrhuber [this message]
2003-12-01 17:21 ` slow stat() ? David Bernick
2003-12-01 17:30 ` Chris Mason
2003-12-01 7:47 ` Hans Reiser
2003-12-11 4:44 ` update on " David Bernick
2003-12-01 17:43 ` David Bernick
2003-12-01 17:57 ` Chris Mason
2003-12-02 11:57 ` David Bernick
2003-12-01 8:02 ` Strange errors with 2.4.22 patches (from Chris) and bonnie++ Jens Benecke
2003-12-01 13:49 ` Chris Mason
2003-12-02 8:35 ` Jens Benecke
2003-12-03 19:13 ` Chris Mason
2003-12-04 12:44 ` Jens Benecke
2003-12-04 16:28 ` Chris Mason
2003-12-04 16:33 ` Chris Mason
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=3FCB6597.8010604@gmx.net \
--to=christian.mayrhuber@gmx.net \
--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.