From: Dave Jones <davej@codemonkey.org.uk>
To: "Theodore Ts'o" <tytso@mit.edu>,
Linux Kernel <linux-kernel@vger.kernel.org>
Subject: Re: an updated post-halloween doc.
Date: Mon, 4 Nov 2002 14:45:15 +0000 [thread overview]
Message-ID: <20021104144515.GA22371@suse.de> (raw)
In-Reply-To: <20021104142105.GA9197@think.thunk.org>
On Mon, Nov 04, 2002 at 09:21:06AM -0500, Theodore Ts'o wrote:
Hi Ted,
> Could you please change this to read version 1.30 of e2fsprogs? There
> were some rare conditions where e2fsck could get confused with htree
> directories in e2fsprogs 1.29 that were fixed in 1.30. None of the
> htree-related e2fsck bugs in 1.29 were catastrophic in the sense of
> causing data loss, but they might cause confusion and spurious kernel
> bug reports.
For now, I've moved the htree things off the list on Andreas Dilger's
request in light of the corruption reports that were mentioned.
Are you any closer in nailing those issues ?
Dave
--
| Dave Jones. http://www.codemonkey.org.uk
next prev parent reply other threads:[~2002-11-04 14:39 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-11-01 20:48 an updated post-halloween doc Dave Jones
2002-11-04 14:21 ` Theodore Ts'o
2002-11-04 14:45 ` Dave Jones [this message]
2002-11-04 14:52 ` bert hubert
2002-11-05 2:39 ` Miles Bader
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=20021104144515.GA22371@suse.de \
--to=davej@codemonkey.org.uk \
--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