From: Mike Fedyk <mfedyk@matchmail.com>
To: Rasmus B?g Hansen <moffe@amagerkollegiet.dk>
Cc: Erik Tews <erik.tews@gmx.net>,
Roy Sigurd Karlsbakk <roy@karlsbakk.net>,
linux-kernel@vger.kernel.org
Subject: Re: tuning ext2 or ReiserFS to avoid fragmentation with large files?
Date: Tue, 4 Dec 2001 20:40:19 -0800 [thread overview]
Message-ID: <20011204204019.F25292@mikef-linux.matchmail.com> (raw)
In-Reply-To: <20011204142047.N11967@no-maam.dyndns.org> <Pine.LNX.4.33.0112050315450.2930-100000@grignard.amagerkollegiet.dk>
In-Reply-To: <Pine.LNX.4.33.0112050315450.2930-100000@grignard.amagerkollegiet.dk>
On Wed, Dec 05, 2001 at 03:17:17AM +0100, Rasmus B?g Hansen wrote:
> On Tue, 4 Dec 2001, Erik Tews wrote:
>
> > If I remember right xfs has got a online-defragmentation utility. So
> > have a look at xfs.
> >
> > I think xfs works different from reiserfs and ext2 when writing files to
> > disk which helps avoiding fragmentation. This feature is called
> > allocation groups.
>
> I *might* be wrong, but isn't the allocation-group thing exactly what
> ext2/ext3 does?
>
Basically, yes. They both have the name "group" in some of their feature
lists. What really matters is *what* they encompass, and *how* they're used.
Can someone in the know comment about the similarity of the ext[23] and xfs
groups?
next prev parent reply other threads:[~2001-12-05 4:40 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-12-03 13:13 tuning ext2 or ReiserFS to avoid fragmentation with large files? Roy Sigurd Karlsbakk
2001-12-04 13:20 ` Erik Tews
2001-12-05 2:17 ` Rasmus Bøg Hansen
2001-12-05 4:40 ` Mike Fedyk [this message]
2001-12-05 10:40 ` Erik Tews
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=20011204204019.F25292@mikef-linux.matchmail.com \
--to=mfedyk@matchmail.com \
--cc=erik.tews@gmx.net \
--cc=linux-kernel@vger.kernel.org \
--cc=moffe@amagerkollegiet.dk \
--cc=roy@karlsbakk.net \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.