From: Oleg Drokin <green@namesys.com>
To: venom@sns.it
Cc: linux-kernel@vger.kernel.org
Subject: Re: ReiserFS corruption with kernel 2.5.59
Date: Mon, 20 Jan 2003 17:28:26 +0300 [thread overview]
Message-ID: <20030120172826.A2758@namesys.com> (raw)
In-Reply-To: <Pine.LNX.4.43.0301201523180.1706-100000@cibs9.sns.it>
Hello!
On Mon, Jan 20, 2003 at 03:23:54PM +0100, venom@sns.it wrote:
> Yes, it was.
> Before I started 2.5.59 I was running 2.4.20 with no problems at all.
Hm. Interesting. I will look for the cause.
Let us know if you'd see this problem again, though (and if you'd be able
to find what sequence of events caused this to happen, that would be even
more good).
Thank you.
Bye,
Oleg
next prev parent reply other threads:[~2003-01-20 14:19 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-01-20 13:23 ReiserFS corruption with kernel 2.5.59 venom
2003-01-20 13:43 ` Oleg Drokin
2003-01-20 14:23 ` venom
2003-01-20 14:28 ` Oleg Drokin [this message]
2003-01-20 16:06 ` venom
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=20030120172826.A2758@namesys.com \
--to=green@namesys.com \
--cc=linux-kernel@vger.kernel.org \
--cc=venom@sns.it \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox