From: Hans Reiser <reiser@namesys.com>
To: Valdis.Kletnieks@vt.edu
Cc: Benjamin Scott <bscott@ntisys.com>,
ReiserFS List <reiserfs-list@namesys.com>
Subject: Re: Silly question, defrag
Date: Fri, 05 Apr 2002 19:13:39 +0400 [thread overview]
Message-ID: <3CADBF23.4060707@namesys.com> (raw)
In-Reply-To: 200204051404.g35E4L6H007366@foo-bar-baz.cc.vt.edu
Valdis.Kletnieks@vt.edu wrote:
>On Fri, 05 Apr 2002 08:50:35 EST, Benjamin Scott <bscott@ntisys.com> said:
>
>> What about using "idle time" to defragment the filesystem on a continuous
>>basis? If the system is not doing anything else, a background daemon in the
>>kernel could move blocks around to optimize things. While I expect this
>>
>
>A good idea, worth researching, but probably a royal pain to implement.
>The biggest problem is identifying "idle", and being careful to do things
>in a way that doesn't cause problems if the system suddenly goes un-idle.
>
>It's not as bad as doing an fsck on a live filesystem - but you do want to
>be sure that if a program suddenly decides to read the file you're currently
>moving around, that you do the right thing (writing gets a bit trickier -
>you have to worry about stuff like somebody doing an fsync() of a block
>that you're in the middle of moving around on the disk. Race Condition City ;)
>
Actually, we will be able to do repacking online without a lot of extra
code, due to our designing the right functionality into our flushing and
journaling algorithms.
Some things become a lot easier when they are architected in at the
beginning....
Hans
next prev parent reply other threads:[~2002-04-05 15:13 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
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 [this message]
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=3CADBF23.4060707@namesys.com \
--to=reiser@namesys.com \
--cc=Valdis.Kletnieks@vt.edu \
--cc=bscott@ntisys.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.