From: geearf@free.fr
To: reiserfs-devel <reiserfs-devel@vger.kernel.org>
Subject: Reiser4 Fragmentation
Date: Thu, 12 Feb 2009 02:17:00 +0100 (CET) [thread overview]
Message-ID: <854512329.462431234401420041.JavaMail.root@zimbra4-e1.priv.proxad.net> (raw)
In-Reply-To: <1234385241.5099.5.camel@Anastacia.local>
Hello people,
after running into big disk IO I investigated a bit and found that my / is a bit fragmented (the tree is at about 9% from measurefs).
Can that affect a ccreg40 filesystem badly? Anything else relative to R4 that I can look into?
Thank you,
John
next prev parent reply other threads:[~2009-02-12 1:17 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-02-11 20:23 libaal patch fixing pointer cast warnings Frederik Himpe
2009-02-11 20:47 ` Frederik Himpe
2009-02-12 1:17 ` geearf [this message]
2009-02-14 13:15 ` Reiser4 Fragmentation Edward Shishkin
2009-02-15 0:18 ` libaal patch fixing pointer cast warnings Edward Shishkin
2009-02-15 18:19 ` Frederik Himpe
[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
2009-02-22 23:01 ` geearf
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=854512329.462431234401420041.JavaMail.root@zimbra4-e1.priv.proxad.net \
--to=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;
as well as URLs for NNTP newsgroup(s).