archive mirror
 help / color / mirror / Atom feed
From: Marc-Christian Petersen <>
To: "Theodore Ts'o" <>,
	"Christopher Li",
	"Ryan Cumming" <>
Subject: Re: [PATCH] fix htree dir corrupt after fsck -fD
Date: Sun, 29 Sep 2002 19:12:46 +0200	[thread overview]
Message-ID: <> (raw)

Hi Ryan,

>> This is a completely fresh loopback EXT3 filesystem, untouched by fsck -D,
>> and normally unmounted.

> Oh, and I've attached the current version of my test program if anyone is 
> interested.
> ...
> It can corrupt my loopback test filesystems in under 5 minutes. Note that it
> will completely destroy any data in its working directory, however.
I am running your program now over an hour without any corruption on the 
loopback mounted ext3 filesystem.

This is with the latest patch (1) from Theodore + latest small fix from 
Christoper for the kernel and for latest e2fsprogs.

I made some debian packages available which includes the latest fixes, can be 
found here (2).

Anyway, works great for me! :)


Kind regards
        Marc-Christian Petersen

PGP/GnuPG Key: 1024D/569DE2E3DB441A16
Fingerprint: 3469 0CF8 CA7E 0042 7824 080A 569D E2E3 DB44 1A16
Key available at Encrypted e-mail preferred.

             reply	other threads:[~2002-09-29 17:08 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-09-29 17:12 Marc-Christian Petersen [this message]
  -- strict thread matches above, loose matches on Subject: below --
2002-09-25 20:03 [BK PATCH] Add ext3 indexed directory (htree) support tytso
2002-09-26 23:57 ` Theodore Ts'o
2002-09-27  4:12   ` Andreas Dilger
2002-09-28  1:20     ` Ryan Cumming
2002-09-28 14:13       ` Theodore Ts'o
2002-09-29  7:03         ` [PATCH] fix htree dir corrupt after fsck -fD chrisl
2002-09-29  8:16           ` Ryan Cumming
2002-09-29  8:36             ` Ryan Cumming
2002-09-30  2:46             ` Ryan Cumming
2002-09-29 14:13           ` Theodore Ts'o

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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \ \ \ \ \ \

* 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;
as well as URLs for NNTP newsgroup(s).