From: Oleg Drokin <green@namesys.com>
To: Javier Marcet <jmarcet@pobox.com>
Cc: reiserfs-list@namesys.com
Subject: Re: Corruptions on every filesystem with 02-reiserfs_file_write.diff.gz
Date: Wed, 21 Aug 2002 20:41:41 +0400 [thread overview]
Message-ID: <20020821204141.A919@namesys.com> (raw)
In-Reply-To: <20020821163122.GA6628@jerry.boludo.cjb.net>
Hello!
On Wed, Aug 21, 2002 at 06:31:22PM +0200, Javier Marcet wrote:
> > You said XFS, does that mean you had XFS patched in too in all cases?
> No, that was the first patch I removed - or didn't add, since I began
> from scratch again -, since I only wanted to test it and being such a
> big piece of code which modified so many things, there were good chances
> for it to be the culprit.
Ok, one thing off the equation.
> If you tell me any way to further investigate this situation and find a
> possible solution, I'll be glad to. My only fear is running a kernel
> with the patch applied for too long. After all I value my date and do
> want to keep it safe, not only access to it fast.
Can you try compiling your kernel with gcc 2.95.3? (I just don't have
gcc 3.2 at hand, that's it).
To avoid risking your data - you may have empty scratch partition, on which
you can test and boot off rescue CD-ROM, so that your data will be safe.
Bye,
Oleg
next prev parent reply other threads:[~2002-08-21 16:41 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-08-20 15:17 Corruptions on every filesystem with 02-reiserfs_file_write.diff.gz Javier Marcet
2002-08-21 6:13 ` Oleg Drokin
2002-08-21 16:31 ` Javier Marcet
2002-08-21 16:41 ` Oleg Drokin [this message]
2002-08-23 7:42 ` Oleg Drokin
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=20020821204141.A919@namesys.com \
--to=green@namesys.com \
--cc=jmarcet@pobox.com \
--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.