From: Ed Sweetman <ed.sweetman@wmich.edu>
To: Alex Tomas <alex@clusterfs.com>
Cc: linux-kernel@vger.kernel.org, Stephen Hemminger <shemminger@osdl.org>
Subject: Re: [PATCH] EXT3 extents against 2.6.0-test7
Date: Mon, 13 Oct 2003 17:39:45 -0400 [thread overview]
Message-ID: <3F8B1BA1.4020800@wmich.edu> (raw)
In-Reply-To: <20031013222747.37f5ee7b.alex@clusterfs.com>
Alex Tomas wrote:
> changes since last publication:
> 1) few bugs fixed: they caused extents tree corruption
> 2) several asserts added
> 3) binary search used to find an extent
> 4) last found entry is cached: this allows to skip tree
> traversal and saves cpu a bit
> 5) truncate_sem is used to serialize get_block()/trucate()
>
>
> with best wishes, Alex
>
>
I've been using extents since the patch was introduced. I haven't seen
any corruption when using it with large files (ie. multimedia only). In
short, has there been any progress with getting fsck support? I'm 100%
in support of this patch going into mainline kernel as a non-default
option. It's perfect for partitions that deal with large files, but
still want ext3's fs corruption protection. I average 10700 blocks an
extent and see an extreme increase in performance over non-extents ext3
doing operations on files of the same size. I guess it's about time to
update.
next prev parent reply other threads:[~2003-10-13 21:39 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-10-13 18:27 Alex Tomas
2003-10-13 21:39 ` Ed Sweetman [this message]
[not found] ` <20031014212359.42243025.alex@clusterfs.com>
2003-10-17 19:32 ` Ed Sweetman
2003-10-17 20:10 ` Alex Tomas
2003-10-17 20:13 ` Ed Sweetman
2003-10-17 20:41 ` Alex Tomas
2003-10-17 21:22 ` Ed Sweetman
2003-10-17 23:05 ` Alex Tomas
2003-10-18 0:07 ` Ed Sweetman
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=3F8B1BA1.4020800@wmich.edu \
--to=ed.sweetman@wmich.edu \
--cc=alex@clusterfs.com \
--cc=linux-kernel@vger.kernel.org \
--cc=shemminger@osdl.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
Powered by JetHome