From: "daniel.poelzleithner" <poelzi@poelzi.org>
To: Reiser FS Mailing List <reiserfs-list@namesys.com>
Subject: Slow stats on reiserfs 3
Date: Thu, 01 Apr 2004 15:13:18 +0200 [thread overview]
Message-ID: <406C156E.406@poelzi.org> (raw)
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Hi,
There is a discussion at the BackupPC Mailinglist why the nightly
cleanup of the backup Pool takes so much more time against ext3.
Here is the thead:
http://sourceforge.net/mailarchive/forum.php?thread_id=4144370&forum_id=503
The pool directory looks like:
cpool/0/0/0/0001257ca4eff2a5c9b60797fa034275
I tested:
find /MY/CPOOL -type d -exec stat {} > /dev/null \;
and it takes around 170 minutes on my 30 gb pool with 687847 files.
I looked with debugreiserfs at the metadata and it seems that ca. every
fivest file has an hash collision, but i never saw more than on
collision per directory.
Is there anyting to speed this up on large directories ?
regards
~ Daniel
- --
nihil me cirumdat
.. . .. ... . . .. . ... . .. . ... . . .
pgp key @ http://files.poelzi.org/pgp.txt
ED80 E53D 5269 4BB1 1E73 3A53 CBF9 A421 0A7B 003D
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.4 (GNU/Linux)
Comment: Using GnuPG with Debian - http://enigmail.mozdev.org
iD8DBQFAbBVty/mkIQp7AD0RApTwAJ9E61qH2LzbJ7R5xm7YAaFARt1tcwCcDk8c
e69X2MvlWGYRU1tyTdL5yds=
=Lggx
-----END PGP SIGNATURE-----
reply other threads:[~2004-04-01 13:13 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=406C156E.406@poelzi.org \
--to=poelzi@poelzi.org \
--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.