about mke2fs -j -O dir_index

kpachopoulos · 11-12-2005, 02:00 AM

The "mke2fs -O dir_index" thing seems a good idea. What does dir_index however represent? When i create a new filesystem can i just do " mke2fs -j -O /dev/hdXY"?
Or must i, after the creation of a filesystem- mke2fs -j, do for each directory in which i want to have b-hashed trees, mke2fs -O directory_path?
Thanks

homey · 11-12-2005, 08:30 AM

From the man page, it looks like dir_index just give the filesystem a place to see where things are located so it can go there more quickly.

I think you need to put the feature after -O . For example:
mke2fs -j -O dir_index /dev/hda1
or
mkfs.ext3 -O dir_index /dev/hda1

Code:

       -O feature[,...]
              Create  filesystem with given features (filesystem options), overrid-
              ing the default filesystem options.  Currently, the sparse_super  and
              filetype  features  are  turned on by default when mke2fs is run on a
              system with Linux 2.2 or later  (unless  creator-os  is  set  to  the
              Hurd).   Filesystems  that may need to be mounted on pre-2.2 Linux or
              other kernels should be created with -O none (or -r 0 for Linux  1.2)
              which  will disable these features, even if mke2fs is run on a system
              which can support them.

              The following filesystem options are supported:

                   dir_index
                          Use hashed b-trees to speed up lookups in large  directo-
                          ries.