Filesystems On Exadata Compute Nodes Do Not Have Dir_index Configured - Why Not?
Last updated on FEBRUARY 19, 2013
Applies to:Exadata Database Machine X2-8 - Version All Versions to All Versions [Release All Releases]
Oracle Exadata Hardware - Version 184.108.40.206 to 220.127.116.11.1 [Release 11.2]
Information in this document applies to any platform.
The Cell Server and Database Compute Node Linux imagers create ext3 filesystems without the 'dir_index' and 'resize_inode' options when a node is freshly imaged.
The dir_index option causes directory entries to be indexed which speeds up access to directories with large numbers of files. On the Database Machine, this is most likely to affect access to the ASM and RDBMS audit and trace directories.
The resize_inode option reserves extra inode space to accommodate larger resize operations on ext3 filesystems. It is still possible to resize an ext3 filesystem that was not created with the resize_inode option, but the amount by which the filesystem can be grown is lower.
Sign In with your My Oracle Support account
Don't have a My Oracle Support account? Click to get started
My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms