All of lore.kernel.org
 help / color / mirror / Atom feed
From: Tracy R Reed <treed@ultraviolet.org>
To: Matthew Johnson <matthew@psychohorse.com>
Cc: reiserfs-list@namesys.com
Subject: Re: Silly question, defrag
Date: Wed, 3 Apr 2002 15:49:06 -0800	[thread overview]
Message-ID: <20020403154906.A21821@ultraviolet.org> (raw)
In-Reply-To: <200204030740.05950@X-Message-Flag:>; from matthew@psychohorse.com on Wed, Apr 03, 2002 at 08:08:21AM -0800

[-- Attachment #1: Type: text/plain, Size: 1546 bytes --]

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.

It is more useful to look at why one DID defrag back in the bad ol' days
of DOS and Windows. IIRC, the FAT filesystem would scan through it's
equivalient of the free block list and start writing at the first free
block. If it wrote for a while and then there was other data in the way it
stop and go to the next free space. This way fragmentation was practically
guarenteed and it happened rapidly. Modern filesystems use much smarter
ways of laying out data on the disk so that fragmentation happens much
less often. Now you will almost certainly waste more time by defragmenting
than you would suffering whatever performance hit the little fragmentation
there is causes. I've been using Linux/Unix for 10 years and I have never
(not once!) defragged a filesystem.

> Perhaps I should aim this message to the kernel mailing list, so that I can 
> get response from a wider array of people who like other filesystems. But its 
> not kernel related. 

I wouldn't recommend doing that. The answer is pretty much the same
regardless of the filesystem. If it's a non-FAT fs you probably don't have
to worry about fragmentation.

-- 
Tracy Reed      http://www.ultraviolet.org

[-- Attachment #2: Type: application/pgp-signature, Size: 240 bytes --]

  parent reply	other threads:[~2002-04-03 23:49 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
     [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
2002-04-03 23:49     ` Tracy R Reed [this message]
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 18:31   ` Anders Widman
2002-04-03 18:47     ` Yura Umanets
2002-04-03 21:41       ` Anders Widman
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=20020403154906.A21821@ultraviolet.org \
    --to=treed@ultraviolet.org \
    --cc=matthew@psychohorse.com \
    --cc=reiserfs-list@namesys.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.