All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Yura Umanets" <umanets@priocom.com>
To: ReiserFS List <reiserfs-list@namesys.com>
Cc: Joe Cooper <joe@swelltech.com>
Subject: Re: Silly question, defrag
Date: Wed, 03 Apr 2002 21:47:24 +0300	[thread overview]
Message-ID: <3CAB4E3C.6010101@priocom.com> (raw)
In-Reply-To: 1351472281.20020403203135@tnonline.net

Anders Widman wrote:

>>"Don't"
>>
>
>>;-)
>>
>
>>ReiserFS (and ext2|3) do fragment somewhat, but the impact is not worth 
>>fighting over on most systems (certain environments are impacted more 
>>than others--mail servers and web caches being two examples that are hit 
>>pretty hard by fragmentation performance degradation).
>>
>
>>Besides, there is no method to defrag ReiserFS that I know of.  Hans 
>>plans repacking in some future version.  It will be nice, but the whole 
>>'defrag once a month to keep your computer running smoothly' is kind of 
>>a Windows thing.  Us Unix users don't really need to think so much on 
>>those sorts of things.
>>
>
>Fragmentation is a problem with all filesystems. There is generally no
>way around fragmentation other than "defragment".
>
>If you want to add/store a large file on a 30% full filesystem it
>would probably be stored on the first contingous area of free space.
>This works fine until you have used most of the space and changed the
>sizes of lots of files.
>
>Fragmentation is enevitable when you only have small contingous blocks
>of free/unallocated space and want to add a larger file. After some
>time you end up with heavily fragmentation on any filesystem. Of
>course, this doesn't happen when you don't add or change files.
>
>//Anders
>
This is one of things (fragmentation) about which people say "well known 
problem". Can you offer some solution?

-- 
Yury Umanets
IT Engineer of Priocom Corp.
Phone: +380 44 2011959, ICQ: 55494590




  reply	other threads:[~2002-04-03 18:47 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
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 [this message]
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=3CAB4E3C.6010101@priocom.com \
    --to=umanets@priocom.com \
    --cc=joe@swelltech.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.