Bug 74252 - Too many inodes for tera byte filesystem
Too many inodes for tera byte filesystem
Status: CLOSED UPSTREAM
Product: Red Hat Linux
Classification: Retired
Component: e2fsprogs (Show other bugs)
8.0
All Linux
medium Severity medium
: ---
: ---
Assigned To: Florian La Roche
Jay Turner
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2002-09-18 14:47 EDT by hjl
Modified: 2015-01-07 19:00 EST (History)
1 user (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2004-01-13 05:19:50 EST
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)
A patch to use 16KB per inode for big fs (433 bytes, patch)
2002-09-18 14:48 EDT, hjl
no flags Details | Diff

  None (edit)
Description hjl 2002-09-18 14:47:35 EDT
By default, mke2fs allocates one inode for every 8KB data.
On a tera byte filesystem, it is a lot of inodes. I am
uploading a patch to change it to 16KB per inode for fs
bigger than 1TB.
Comment 1 hjl 2002-09-18 14:48:44 EDT
Created attachment 76545 [details]
A patch to use 16KB per inode for big fs
Comment 2 Florian La Roche 2002-12-02 10:03:23 EST
Can you please submit this also for inclusion into the upstream release?

Thanks,

Florian La Roche
Comment 3 hjl 2002-12-02 12:09:50 EST
Done
Comment 4 Florian La Roche 2003-01-14 16:16:15 EST
Seems this is not part of release 1.32. Is this resolved with an option instead
changing the automatic defaults?

greetings,

Florian La Roche
Comment 5 Florian La Roche 2004-01-13 05:19:50 EST
Closing here, should go into upstream releases.

greetings,

Florian La Roche

Note You need to log in before you can comment on or make changes to this bug.