From: erik.tews@gmx.net (Erik Tews)
To: Roy Sigurd Karlsbakk <roy@karlsbakk.net>
Cc: linux-kernel@vger.kernel.org
Subject: Re: tuning ext2 or ReiserFS to avoid fragmentation with large files?
Date: Tue, 4 Dec 2001 14:20:47 +0100 [thread overview]
Message-ID: <20011204142047.N11967@no-maam.dyndns.org> (raw)
In-Reply-To: <Pine.LNX.4.30.0112031404030.7944-100000@mustard.heime.net>
In-Reply-To: <Pine.LNX.4.30.0112031404030.7944-100000@mustard.heime.net>
On Mon, Dec 03, 2001 at 02:13:22PM +0100, Roy Sigurd Karlsbakk wrote:
> hi all
>
> I've got this server with lots of ~3GB files and every now and then we
> need to add some more or delete some old ones. All files are potentially
> read concurrently, so to reduce disk seeks, I've increased the readahead
> settings in kernel (/proc/sys/vm/(min|max)-readahead).
>
> Then... A friend of mine told me I could tune the fs (or vfs) to allocate
> n kB each time a file is created, and by setting this to whatever I've set
> (min|max)-readahead to (currently 1048576), I will reduce the negative
> effect of fragmentation to a minimum, since the data blocks will be large,
> and read more-or-less sequencially.
>
> Can anyone tell me how to tell the fs or the kernel to allocate n pages/kB
> this way? Is it possible? Can I possibly set different sizes per file
> system?
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.
next prev parent reply other threads:[~2001-12-04 15:26 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-12-03 13:13 Roy Sigurd Karlsbakk
2001-12-04 13:20 ` Erik Tews [this message]
2001-12-05 2:17 ` Rasmus Bøg Hansen
2001-12-05 4:40 ` Mike Fedyk
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=20011204142047.N11967@no-maam.dyndns.org \
--to=erik.tews@gmx.net \
--cc=linux-kernel@vger.kernel.org \
--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 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®