gluster-devel
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[Gluster-devel] Wiki pages possible error about tune2fs optimizations


From: Angel
Subject: [Gluster-devel] Wiki pages possible error about tune2fs optimizations
Date: Sun, 13 Jan 2008 13:45:13 +0100
User-agent: KMail/1.9.6 (enterprise 20070904.708012)

Hi,

Ive ben searching on de list archives related to the following:

On wiki 
http://www.gluster.org/docs/index.php/Guide_to_Optimizing_GlusterFS#Tuning_Kernel_Parameters


You can read...

" Ext3 also has directory indexing which is very much useful for the 
directories which have larger files or many files by boosting the file access. 
This is done by generating hashed binary trees to store directory information. 
But by default if a directory grows beyond a single disk block its 
automatically indexed using a hash tree. 

To enable directory indexing use the following commands 

$ tune2fs -0 /dev/hda1 
"

But the man page for tune2fs says:

"
-O [^]feature[,...]
              Set or clear the indicated filesystem features (options) in the 
filesystem.  More than  one  filesystem  feature  can  be
              cleared  or  set  by  separating features with commas.  
Filesystem features prefixed with a caret character ('^') will be
              cleared in the filesystem's superblock; filesystem features 
without a prefix character or prefixed with a plus  character
              ('+') will be added to the filesystem.

              The following filesystem features can be set or cleared using 
tune2fs:

                   dir_index
                          Use hashed b-trees to speed up lookups in large 
directories.
"

this would lead to ..

$ tune2fs -O dir_index /dev/hda1



My distribution is OpenSuse 10.3

¿is this an error on he wiki or there are more ways to activate dir_index flag 
in other distributions.?


Regards, Angel
-- 
------------------------------------------------
Clist UAH
------------------------------------------------




reply via email to

[Prev in Thread] Current Thread [Next in Thread]