The man page still said it was not possible to change the number
of inodes on a filesystem after creating it. You actually can
by resizing the fs, so clarify this language a bit.
---
misc/mke2fs.8.in | 6 +++---
1 file changed, 3 insertions(+), 3 deletions(-)
diff --git a/misc/mke2fs.8.in b/misc/mke2fs.8.in
index fe2dcdb..873fdbf 100644
--- a/misc/mke2fs.8.in
+++ b/misc/mke2fs.8.in
@@ -349,9 +349,9 @@ bytes of space on the disk. The larger the
ratio, the fewer inodes will be created. This value generally shouldn't
be smaller than the blocksize of the filesystem, since in that case more
inodes would be made than can ever be used. Be warned that it is not
-possible to expand the number
-of inodes on a filesystem after it is created, so be careful deciding the
-correct value for this parameter.
+possible to change this ratio on a filesystem after it is created, so be
+careful deciding the correct value for this parameter. Note that resizing
+a filesystem changes the numer of inodes to maintain this ratio.
.TP
.BI \-I " inode-size"
Specify the size of each inode in bytes.
--
1.8.1.2
On Mon, Oct 07, 2013 at 10:39:42AM -0400, Phillip Susi wrote:
> The man page still said it was not possible to change the number
> of inodes on a filesystem after creating it. You actually can
> by resizing the fs, so clarify this language a bit.
You didn't include a signed-off-by, but this was a simple enough
documentation-only change that I've used by discretion to accept it.
Cheers,
- Ted