From: Hans Reiser <reiser@namesys.com>
To: Richard Thornton <richard@programming-analytics.org>
Cc: Ross Vandegrift <ross@willow.seitz.com>,
Matthew Johnson <matthew@psychohorse.com>,
reiserfs-list@namesys.com
Subject: Re: Silly question, defrag
Date: Thu, 04 Apr 2002 00:44:15 +0400 [thread overview]
Message-ID: <3CAB699F.8000706@namesys.com> (raw)
In-Reply-To: Pine.GSO.4.33.0204031537160.16132-100000@loghost
Richard Thornton wrote:
>Why doesn't linux use UFS? I can't understand this.
>
>Richard
>
>
>On Wed, 3 Apr 2002, Ross Vandegrift wrote:
>
>>On Wed, Apr 03, 2002 at 08:08:21AM -0800, Matthew Johnson wrote:
>>
>>>On Wednesday 03 April 2002 00:21, Joe Cooper wrote:
>>>
>>>>"Don't"
>>>>
>>>Well I don't, but when newbies who are used to computing on win32 systems
>>>hear that they may not just accept the word don't. Actually its hard to find
>>>the reasons exactly why one does not defrag.
>>>
>>Depending on the elevator algorithms in Linux (sorry, I'm not very
>>familiar with them), performance can actually be *increased* by
>>some bit of fragmentation. If the data is spread out over the disk,
>>I've heard it allows some elevator algorithms to improve their queuing
>>stategies. I'm pretty sure this is the case on Novell Netware.
>>
>>Unfortunately I don't have enough technical knowledge about elevator
>>algorithms to really know if it helps or hurts us. However, I do know
>>that back in the days when I was just getting into Linux stuff
>>(around 2.0.0-ish era), it was generally said that ext2 driver did basic
>>defrag on write and it limited fragmentation to pathological filesystem
>>usage.
>>
>>Again, not sure that this is still the case.
>>
>>Ross Vandegrift
>>ross@willow.seitz.com
>>
>
>
>
UFS is slower than ext2 by a lot.
Hans
next prev parent reply other threads:[~2002-04-03 20:44 UTC|newest]
Thread overview: 39+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <200204030017.12595@X-Message-Flag:>
2002-04-03 8:21 ` Silly question, defrag Joe Cooper
2002-04-03 8:25 ` Hans Reiser
2002-04-03 16:14 ` Matthew Johnson
[not found] ` <200204030808.26186@X-Message-Flag:>
2002-04-03 18:28 ` Hans Reiser
2002-04-03 16:08 ` Matthew Johnson
2002-04-03 18:31 ` Anders Widman
2002-04-03 18:47 ` Yura Umanets
2002-04-03 21:41 ` Anders Widman
[not found] ` <200204030740.05950@X-Message-Flag:>
2002-04-03 18:24 ` Hans Reiser
2002-04-03 19:33 ` matthew johnson
2002-04-04 0:45 ` Tracy R Reed
2002-04-04 1:42 ` rod
2002-04-04 5:19 ` The Amazing Dragon
[not found] ` <20020404161547.GD3990@jensbenecke.de>
2002-04-05 0:04 ` rod
2002-04-07 4:52 ` The Doctor What
2002-04-03 20:30 ` Ross Vandegrift
2002-04-03 20:37 ` Richard Thornton
2002-04-03 20:44 ` Hans Reiser [this message]
2002-04-03 23:49 ` Tracy R Reed
2002-04-04 1:58 ` Manuel Krause
2002-04-04 9:16 ` Anders Widman
2002-04-04 18:54 ` Tracy R Reed
2002-04-04 19:09 ` Valdis.Kletnieks
2002-04-04 19:20 ` Anders Widman
2002-04-04 22:18 ` Rodd Zurcher
2002-04-04 22:34 ` Benjamin Scott
2002-04-05 5:31 ` Ross Vandegrift
2002-04-05 6:19 ` Anders Widman
2002-04-05 13:50 ` Benjamin Scott
2002-04-05 15:07 ` Hans Reiser
2002-04-05 8:49 ` Hans Reiser
2002-04-05 13:50 ` Benjamin Scott
2002-04-05 14:04 ` Valdis.Kletnieks
2002-04-05 14:20 ` Benjamin Scott
2002-04-05 15:13 ` Hans Reiser
2002-04-05 13:53 ` Stefan Fleiter
2002-04-05 18:56 ` Chris Dukes
2002-04-05 22:33 ` Stefan Fleiter
2002-04-03 8:20 Matthew Johnson
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=3CAB699F.8000706@namesys.com \
--to=reiser@namesys.com \
--cc=matthew@psychohorse.com \
--cc=reiserfs-list@namesys.com \
--cc=richard@programming-analytics.org \
--cc=ross@willow.seitz.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 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.