From: <Hell.Surfers@cwctv.net>
To: reiser@namesys.com, aaronl@vitelus.com, Nikita@Namesys.COM,
sct@redhat.com, linux-kernel@vger.kernel.org,
reiserfs-list@namesys.com
Subject: RE:Re: ext3 throughput woes on certain (possibly heavily fragmented) files
Date: Sat, 7 Sep 2002 00:19:00 +0100 [thread overview]
Message-ID: <0dafd0118230692DTVMAIL9@smtp.cwctv.net> (raw)
[-- Attachment #1: Type: text/plain, Size: 169 bytes --]
Perhaps you could use a fat partition, you can defragment those, or ntfs [mwaaaahahaha].
On Sat, 07 Sep 2002 02:05:12 +0400 Hans Reiser <reiser@namesys.com> wrote:
[-- Attachment #2: Type: message/rfc822, Size: 2689 bytes --]
From: Hans Reiser <reiser@namesys.com>
To: Aaron Lehmann <aaronl@vitelus.com>
Cc: Nikita Danilov <Nikita@Namesys.COM>, "Stephen C. Tweedie" <sct@redhat.com>, linux-kernel@vger.kernel.org, reiserfs-list@namesys.com
Subject: Re: ext3 throughput woes on certain (possibly heavily fragmented) files
Date: Sat, 07 Sep 2002 02:05:12 +0400
Message-ID: <3D792698.4010401@namesys.com>
Aaron Lehmann wrote:
>On Fri, Sep 06, 2002 at 09:22:22PM +0400, Hans Reiser wrote:
>
>
>>I think I prefer that we implement a repacker for reiser4 though, as
>>that, combined with delayed allocation, will be a balanced and thorough
>>solution.
>>
>>
>
>How does current ReiserFS fare against extreme fragmentation? What
>about XFS? Without trying to risk a flamewar, what Linux filesystems
>are the most preventive of fragmentation?
>
>The filesystem could make a huge difference on a machine like a mail
>server...
>
>
>
>
Sometimes it is best to confess that one does not have the expertise
appropriate for answering a question. Someone on our mailing list
studied it carefully though. Perhaps they can comment.
Hans
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
reply other threads:[~2002-09-06 23:15 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=0dafd0118230692DTVMAIL9@smtp.cwctv.net \
--to=hell.surfers@cwctv.net \
--cc=Nikita@Namesys.COM \
--cc=aaronl@vitelus.com \
--cc=linux-kernel@vger.kernel.org \
--cc=reiser@namesys.com \
--cc=reiserfs-list@namesys.com \
--cc=sct@redhat.com \
/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
all inboxes | Powered by JetHome®