From: tytso@mit.edu
To: Frederic Weisbecker <fweisbec@gmail.com>
Cc: Andi Kleen <andi@firstfloor.org>,
Linus Torvalds <torvalds@linux-foundation.org>,
LKML <linux-kernel@vger.kernel.org>,
Christian Kujau <lists@nerdbynature.de>,
Alexander Beregalov <a.beregalov@gmail.com>,
Chris Mason <chris.mason@oracle.com>, Ingo Molnar <mingo@elte.hu>
Subject: Re: reiserfs broken in 2.6.32 was Re: [GIT PULL] reiserfs fixes
Date: Sat, 2 Jan 2010 16:01:01 -0500 [thread overview]
Message-ID: <20100102210101.GN828@thunk.org> (raw)
In-Reply-To: <20100102201138.GF5076@nowhere>
On Sat, Jan 02, 2010 at 09:11:39PM +0100, Frederic Weisbecker wrote:
>
> I've never lost any datas since I began this work. And
> I run it every day. If I had experienced lock inversions,
> and sometimes soft lockups, I did not experienced serious
> damages. It's a journalized filesystem that can fixup the things
> pretty well.
Have you tried using the xfsqa regression test suite? Despite the
name, it will work on non-xfs filesystems (although there are some
XFS-specific tests in the test suite.) Both the btrfs and ext4
developers use it to debug their file systems, and it's a good way of
stressing the file system in all sorts of different ways that might
not be seen during normal desktop usage. I suspect it would be a good
way of flushing out potential problems for reiserfs as well.
Regards,
- Ted
next prev parent reply other threads:[~2010-01-02 21:01 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-01-02 1:27 [GIT PULL] reiserfs fixes Frederic Weisbecker
2010-01-02 13:41 ` Andi Kleen
2010-01-02 16:36 ` Frederic Weisbecker
2010-01-02 17:43 ` reiserfs broken in 2.6.32 was " Andi Kleen
2010-01-02 19:02 ` Frederic Weisbecker
2010-01-02 19:23 ` Andi Kleen
2010-01-02 20:11 ` Frederic Weisbecker
2010-01-02 20:33 ` Andi Kleen
2010-01-02 20:54 ` Frederic Weisbecker
2010-01-02 21:10 ` Ingo Molnar
2010-01-02 21:42 ` Ingo Molnar
2010-01-02 21:01 ` tytso [this message]
2010-01-02 21:06 ` Frederic Weisbecker
2010-01-02 23:36 ` tytso
2010-01-02 23:43 ` Christian Kujau
2010-01-03 1:16 ` Frederic Weisbecker
2010-01-03 1:52 ` Frederic Weisbecker
2010-01-03 2:05 ` Christian Kujau
2010-01-03 3:27 ` tytso
2010-01-04 20:20 ` Frederic Weisbecker
2010-01-02 20:11 ` Ingo Molnar
2010-01-02 22:18 ` Ingo Molnar
2010-01-02 19:19 ` Linus Torvalds
2010-01-02 19:21 ` Linus Torvalds
2010-01-02 19:24 ` Frederic Weisbecker
2010-01-02 19:22 ` Frederic Weisbecker
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=20100102210101.GN828@thunk.org \
--to=tytso@mit.edu \
--cc=a.beregalov@gmail.com \
--cc=andi@firstfloor.org \
--cc=chris.mason@oracle.com \
--cc=fweisbec@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=lists@nerdbynature.de \
--cc=mingo@elte.hu \
--cc=torvalds@linux-foundation.org \
/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.