From: "Theodore Ts'o" <tytso@mit.edu>
To: linux-kernel@vger.kernel.org
Subject: Updated 2.4 htree patches available for 2.4.21rc5
Date: Sat, 08 Mar 2003 08:13:57 -0500 [thread overview]
Message-ID: <E18re9F-00086y-00@think.thunk.org> (raw)
I've backported all of the bugfixes to the 2.5 dxdir/htree patches to
2.4, and have created a new set of patches for Linux 2.4.21rc5. At this
point it *looks* like we've fixed all of the htree bugs that people have
reported, including the brelse bug, the memory leak bugs, and the NFS
compatibility problems.
I've done *very* light testing, and things seem to work, but I'm now
looking for some brave souls/guinea pigs to give this some more strenous
testing. Please don't use this on production systems just yet, until
some people report success. In particular, I'm looking for people who
had trouble with NFS to confirm whether or not this patch fixes their
problems or not. If you do try out the patch, please let me know how
well (or how poorly) it works.
The patches can be found at:
http://thunk.org/tytso/linux/extfs-2.4-update/extfs-update-2.4.21rc5
Also available are the patches broken out into separate diffs, here:
http://thunk.org/tytso/linux/extfs-2.4-update/broken-out-2.4.21rc5/
In the broken out directory, only the first patch is the htree patch.
The rest are some other 2.5 features which I've backported to 2.4,
including forward compatibility for upcoming future extfs upgrades
including dynamic filesystem resizing and expanded inodes for things
like subsecond timestamps. The patches also add support for setting
default mount options via tune2fs, and the improved Orlov block
allocator.
So if you're feeling adventurour, please backup your systems (you should
*always* backup your systems, even when you're not trying out new kernel
patches :-), and give these patches a whirl, and let me know how it
goes. Thanks!
- Ted
next reply other threads:[~2003-03-08 13:03 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-03-08 13:13 Theodore Ts'o [this message]
2003-03-09 7:14 ` Still getting some NFS htree strangeness Jeremy Fitzhardinge
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=E18re9F-00086y-00@think.thunk.org \
--to=tytso@mit.edu \
--cc=linux-kernel@vger.kernel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox