From: Martin Schlemmer <azarah@gentoo.org>
To: "Theodore Ts'o" <tytso@mit.edu>
Cc: Andreas Dilger <adilger@clusterfs.com>,
KML <linux-kernel@vger.kernel.org>
Subject: Re: Corruption problem with ext3 and htree
Date: 11 Mar 2003 10:27:08 +0200 [thread overview]
Message-ID: <1047371228.3512.46.camel@workshop.saharact.lan> (raw)
In-Reply-To: <20030311061911.GF1965@think.thunk.org>
On Tue, 2003-03-11 at 08:19, Theodore Ts'o wrote:
> Hmm... can you help construct a test case that doesn't rely on the
> presence of the Gentoo distribution? Is there some way we can
> instrument the python code so we can see the exact filesystem
> operations (renames, deletions, moves, etc.) that is going on? The
> good news is that you say that you're able to reproduce it every
> single time, which implies it's not a timing related problem.
>
Ok, will try to get A short way to duplicate this.
Regards,
--
Martin Schlemmer
next prev parent reply other threads:[~2003-03-11 8:18 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-03-07 4:39 Corruption problem with ext3 and htree Martin Schlemmer
2003-03-07 6:48 ` Andreas Dilger
2003-03-07 7:38 ` Martin Schlemmer
2003-03-09 4:33 ` Martin Schlemmer
2003-03-09 6:32 ` Andreas Dilger
2003-03-09 6:36 ` Martin Schlemmer
2003-03-11 6:19 ` Theodore Ts'o
2003-03-11 8:27 ` Martin Schlemmer [this message]
2003-03-11 19:17 ` Martin Schlemmer
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=1047371228.3512.46.camel@workshop.saharact.lan \
--to=azarah@gentoo.org \
--cc=adilger@clusterfs.com \
--cc=linux-kernel@vger.kernel.org \
--cc=tytso@mit.edu \
/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