All of lore.kernel.org
 help / color / mirror / Atom feed
From: Nikola Ciprich <nikola.ciprich@linuxbox.cz>
To: linux ext4 list <linux-ext4@vger.kernel.org>
Cc: nikola.ciprich@linuxbox.cz, "Petr Kopecký" <petr.kopecky@linuxbox.cz>
Subject: ext4 and dir_index optimization
Date: Sun, 22 May 2011 14:52:37 +0200	[thread overview]
Message-ID: <20110522125237.GC2176@nik-comp.lan> (raw)

[-- Attachment #1: Type: text/plain, Size: 1198 bytes --]

Hello everybody,

I'd like to ask few questions about dir_index on ext4. On one of my servers
running 2.6.32.14, we were experiencing performance problems, especially
accessing directory with huge (hundreds of thousands) amount of files
was pain. The filesystem had dir_index enabled, so I tried running fsck
-D on it in order to force reindexation. It helped A LOT - ls -1 on this
directory took about 5 minutes, after reindexation, it took about 10
seconds!
So my question is - is it really needed to force reindexation from time
to time? I'm pretty sure dir_index has been enabled since the creation of
filesystem, so shouldn't index be maintained automatically?
Is it possible to check somehow whether optimization is needed, without
umounting fs and running fsck? And possibly also do this optimization?

Thanks a lot in advance!

Cheers!

nik



-- 
-------------------------------------
Ing. Nikola CIPRICH
LinuxBox.cz, s.r.o.
28. rijna 168, 709 01 Ostrava

tel.:   +420 596 603 142
fax:    +420 596 621 273
mobil:  +420 777 093 799

www.linuxbox.cz

mobil servis: +420 737 238 656
email servis: servis@linuxbox.cz
-------------------------------------

[-- Attachment #2: Type: application/pgp-signature, Size: 198 bytes --]

                 reply	other threads:[~2011-05-22 13:25 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=20110522125237.GC2176@nik-comp.lan \
    --to=nikola.ciprich@linuxbox.cz \
    --cc=linux-ext4@vger.kernel.org \
    --cc=petr.kopecky@linuxbox.cz \
    /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.