Linux ReiserFS filesystem (obsolete)
 help / color / mirror / Atom feed
From: Edward Shishkin <edward.shishkin@gmail.com>
To: geearf@free.fr
Cc: reiserfs-devel <reiserfs-devel@vger.kernel.org>
Subject: Re: Reiser4 Fragmentation
Date: Sun, 22 Feb 2009 19:32:19 +0300	[thread overview]
Message-ID: <49A17E13.3040102@gmail.com> (raw)
In-Reply-To: <1385878997.819661234829671975.JavaMail.root@zimbra4-e1.priv.proxad.net>

geearf@free.fr wrote:
>> measurefs.reiser4 is pretty ancient, and I guess
>> that it works incorrectly for compressed files.
>>
>>     
>> (External) fragmentation resulted in a number of "extents" is
>> a sticky thing inherent to all linux file systems, including reiser4.
>> Currently there is no tools to reorganize reiser4 without having
>> a spare partition. However, it is possible to create something
>> simple like xfs_fsr: it would be an appreciable help.
>>     
>> The "smart reiser4 repacker" based on the flush algorithm was
>> supposed to be the paid option, and therefore there are some
>> obvious issues of its development.
> Well I ended up taring my /, mkfs and untaring it.
> So it should not be fragmented in any way anymore.
> I will look at the internal fragmentation of my /home, but this is not under ccreg40.
>
> I've also just looked at the xfs_fsr thing and it looks pretty useful.
> Can't that be done with a simple script? (sort of like Con's defrag script) or does it need to be related to R4 ?
>
>   

Hello.

Perhaps a simple script is useful, but it has a number of
disadvantages, which make it a software of "not enterprise" level ;)
1) it doesn't take care of holes;
2) it doesn't report about cases when reorganization makes things worser.

Both (1) and (2) need active support of kernel. As to "xfs_fsr simplicity":
it seems, I have misled you. Xfs provides special ioctls to show/allocate
"in place" map of extents, whereas reiser4 doesn't have such service.

Edward.

  reply	other threads:[~2009-02-22 16:32 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <493286232.819611234829500161.JavaMail.root@zimbra4-e1.priv.proxad.net>
2009-02-17  0:14 ` Reiser4 Fragmentation geearf
2009-02-22 16:32   ` Edward Shishkin [this message]
2009-02-22 23:01     ` geearf
2009-02-11 20:47 libaal patch fixing pointer cast warnings Frederik Himpe
2009-02-12  1:17 ` Reiser4 Fragmentation geearf
2009-02-14 13:15   ` Edward Shishkin

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=49A17E13.3040102@gmail.com \
    --to=edward.shishkin@gmail.com \
    --cc=geearf@free.fr \
    --cc=reiserfs-devel@vger.kernel.org \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox