| lists.openwall.net | lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC | |
|
Open Source and information security mailing list archives
| ||
|
Message-Id: <1359129223-7366-1-git-send-email-psusi@ubuntu.com> Date: Fri, 25 Jan 2013 10:53:43 -0500 From: Phillip Susi <psusi@...ntu.com> To: tytso@....edu Cc: linux-ext4@...r.kernel.org Subject: [PATCH] mke2fs: clarify inode ratio in man page 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. Signed-off-by: Phillip Susi <psusi@...ntu.com> --- 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 023ba49..5e5e889 100644 --- a/misc/mke2fs.8.in +++ b/misc/mke2fs.8.in @@ -340,9 +340,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.7.9.5 -- To unsubscribe from this list: send the line "unsubscribe linux-ext4" in the body of a message to majordomo@...r.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
Powered by blists - more mailing lists