From: rod@tpgi.com.au
To: reiserfs-list@namesys.com
Subject: Re: Silly question, defrag
Date: Fri, 5 Apr 2002 10:04:18 +1000 [thread overview]
Message-ID: <3CAD76A2.19329.87D118@localhost> (raw)
In-Reply-To: <20020404161547.GD3990@jensbenecke.de>
<snip>
> When I started with Linux, I was told that Linux did not need a
> defragger because when saving a file, the file system (ext2 in this
> case) took the file size into account when looking for free blocks.
> Fragmentation only happens when the disk is almost full, and no
> contiguous free blocks can be found any more.
>
This should true with files were the size is known before hand.
> Windows, OTOH, starts writing at the first free block and just skips
> used blocks, which quickly leads to BIG fragmentation.
>
> To defragment a disk, if I thought it was absolutely necessary, I was
> told to just read and re-write all files once. Of course for this to be
> successful, you need total free space in one block that exceeds the size
> of the biggest fragmented file.
Though tests I've done with copy & delete with partitions less than
60% full showed that both ext2 and reiserfs did not correct
fragmentation. My guess was that cp did the job in small chunks and
the fs wasnt told the total to allocate. This also demonstrated that for
the case of multiple, continually growing files the amount of free
space was irrelevant.
>
> Are you telling me this is different with ReiserFS? Does ReiserFS not
> try to store files in one contiguous block if possible?
>
>
> --
> mfg, Jens Benecke /// www.hitchhikers.de, www.linuxfaq.de, www.linux.ms
> This mail is an attachment? Read http://www.jensbenecke.de/misc/outlook.html
>
----------------------------------------------
Rod Tunks
Hardware R&D Manager
TPG Network, Canberra
rod@tpgi.com.au (02)62851711
"bad or missing Coffee.sys - operator halted"
ICQ: 4514607
next prev parent reply other threads:[~2002-04-05 0:04 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 [this message]
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
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=3CAD76A2.19329.87D118@localhost \
--to=rod@tpgi.com.au \
--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.