https://jira.whamcloud.com This file is an XML representation of an issue en-us 9.4.14 940014 05-12-2023 https://jira.whamcloud.com/browse/LU-9501 Lustre <p>In certain cases device size where filesystem is created is not know in advance, and it's impractical to try guess correct inode ratio to satisfy filesystem limitations (which is 4G inodes for ext4 and ldiskfs).<br/> We need a flag to tell mke2fs to limit inode count to match current filesystem limits.<br/> Example of current behavior:</p> <div class="code panel" style="border-width: 1px;"><div class="codeContent panelContent"> <pre class="code-java"># mke2fs -i 1024 img mke2fs 1.42.13.x2 (29-Sep-2016) mke2fs: too many inodes (5269225472), raise inode ratio? root@kvkvm1oem(0):~# </pre> </div></div> <p>Proposed behavior (example only, feel free to change message text):</p> <div class="code panel" style="border-width: 1px;"><div class="codeContent panelContent"> <pre class="code-java"># mke2fs -i 1024 --adjust-inode-count img mke2fs 1.42.13.x2 (29-Sep-2016) mke2fs: too many inodes (5269225472), changing to &lt;supported FS limit&gt; ... formatting continues ... </pre> </div></div> LU-9501

Flag for mke2fs to automatically adjust number of inodes

Improvement Major Resolved Fixed WC Triage Artem Blagodarenko e2fsprogs patch Mon, 15 May 2017 12:26:18 +0000 Sat, 16 Sep 2017 01:39:12 +0000 Sat, 16 Sep 2017 01:39:12 +0000 0 3 <p>I think if you don't specify "-I" then it will cap the inode count at 4B? </p> <p>In any case, I think that this should really be a fix in mke2fs and should probably be discussed on the linux-ext4 mailing list?</p> <p>Hello Andreas.</p> <p>Thank you for quick answer. I am agree that mke2fs requires such useful modification. But this feature is very important now for customers running Lustre FS. Currently users which what to create custom large enough cluster, hit this error message and need to readjust config scripts manually, that stops deployment with other automatic parts. This little fix solves the problem and make customers happy. Can we apply it now and switch to another one from ext4 latter?</p> <p>Anyway I will upload this patch here. It can be useful if we decide land it or sent patch to linux-ext4.</p> <p>Thanks.</p> <p>IMHO, I don't think we even need an option for this? Just limit the inode count to 4B inodes automatically rather than returning an error. </p> <p>Artem Blagodarenko (artem.blagodarenko@seagate.com) uploaded a new patch: <a href="https://review.whamcloud.com/27111" class="external-link" target="_blank" rel="nofollow noopener">https://review.whamcloud.com/27111</a><br/> Subject: <a href="https://jira.whamcloud.com/browse/LU-9501" title="Flag for mke2fs to automatically adjust number of inodes" class="issue-link" data-issue-key="LU-9501"><del>LU-9501</del></a> mke2fs: avoid inode number error with large FS<br/> Project: tools/e2fsprogs<br/> Branch: master-lustre<br/> Current Patch Set: 1<br/> Commit: d8b68ec2ccf56dd97cb7be30188d9f745206e534</p> <p>&gt;Just limit the inode count to 4B inodes automatically rather than returning an error.<br/> This patch exact this idea</p> <p>Andreas Dilger (andreas.dilger@intel.com) merged in patch <a href="https://review.whamcloud.com/27111/" class="external-link" target="_blank" rel="nofollow noopener">https://review.whamcloud.com/27111/</a><br/> Subject: <a href="https://jira.whamcloud.com/browse/LU-9501" title="Flag for mke2fs to automatically adjust number of inodes" class="issue-link" data-issue-key="LU-9501"><del>LU-9501</del></a> mke2fs: avoid inode number error with large FS<br/> Project: tools/e2fsprogs<br/> Branch: master-lustre<br/> Current Patch Set: <br/> Commit: ec44b0534beb51ce70bb9b997cbbad2476506b2a</p> Development Rank 1|hzzcpz: Rank (Obsolete) 9223372036854775807