From 5e548ffa4611899417f13d040cc113049edf7b16 Mon Sep 17 00:00:00 2001 From: Richard Henwood Date: Wed, 25 May 2011 11:20:40 -0500 Subject: [PATCH] FIX: improved formating of an example. --- SettingUpLustreSystem.xml | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/SettingUpLustreSystem.xml b/SettingUpLustreSystem.xml index 29743ba..72396c3 100644 --- a/SettingUpLustreSystem.xml +++ b/SettingUpLustreSystem.xml @@ -132,7 +132,7 @@ <indexterm><primary>inodes</primary><secondary>OST</secondary></indexterm>Setting the Number of Inodes for an OST When formatting OST file systems, it is normally advantageous to take local file system usage into account. Try to minimize the number of inodes on each OST, while keeping enough margin for potential variance in future usage. This helps reduce the format and file system check time, and makes more space available for data. The current default is to create one inode per 16 KB of space in the OST file system, but in many environments, this is far too many inodes for the average file size. As a good rule of thumb, the OSTs should have at least: - num_ost_inodes = 4 * <num_mds_inodes> * <default_stripe_count> / <number_osts> + num_ost_inodes = 4 * <num_mds_inodes> * <default_stripe_count> / <number_osts> You can specify the number of inodes on the OST file systems using the following option to the --mkfs option: -N <num_inodes> Alternately, if you know the average file size, then you can specify the OST inode count for the OST file systems using: -- 1.8.3.1