From: geearf@free.fr
To: Edward Shishkin <edward.shishkin@gmail.com>
Cc: reiserfs-devel <reiserfs-devel@vger.kernel.org>
Subject: Re: Reiser4 Fragmentation
Date: Tue, 17 Feb 2009 01:14:32 +0100 (CET) [thread overview]
Message-ID: <1385878997.819661234829671975.JavaMail.root@zimbra4-e1.priv.proxad.net> (raw)
In-Reply-To: <493286232.819611234829500161.JavaMail.root@zimbra4-e1.priv.proxad.net>
----- Mail Original -----
"Edward Shishkin" <edward.shishkin@gmail.com> wrote:
>geearf@free.fr wrote:
>Hello.
>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.
>Internal fragmentation, resulted in wasteful space utilization
>("holes" in the metadata blocks") would mean a bug in the code.
>This fragmentation can be measured as 1 minus the fraction
>du (1) / df (1). Note, that du (1) should be applied to the semantic
>root. If you have ccreg40 partition, then check it with
>"fsck.reiser4 --fix" prior using du (1). Also make sure (for example
>with sync (1)) that there is no dirty pages prior using df (1).
>If the internal fragmentation is more then 0.02, while du (1) is
>large enough (> 100 000), then, please, report.
>Thanks,
>Edward.
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 ?
Thanks Edward,
John
next parent reply other threads:[~2009-02-17 0:14 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 ` geearf [this message]
2009-02-22 16:32 ` Reiser4 Fragmentation Edward Shishkin
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=1385878997.819661234829671975.JavaMail.root@zimbra4-e1.priv.proxad.net \
--to=geearf@free.fr \
--cc=edward.shishkin@gmail.com \
--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