Skip to main content

You are not logged in. Your edit will be placed in a queue until it is peer reviewed.

We welcome edits that make the post easier to understand and more valuable for readers. Because community members review edits, please try to make the post substantially better than how you found it, for example, by fixing grammar or adding additional resources and hyperlinks.

Required fields*

4
  • 2
    Would it be right to say that after running lvextend and prior to running resize2fs, df would NOT report the updated sizes? Commented Jan 14, 2018 at 8:25
  • Exactly. (Added to my answer.) Commented Jan 14, 2018 at 8:37
  • Thanks. What does "creating new inodes to the added space" mean, given that the added space is unused yet, and inodes exist for existing files only? Commented Feb 21, 2019 at 14:22
  • For modern filesystems like XFS it is so. However, the ext2/3/4 filesystems follow a more classic design, with a pre-allocated table of inodes. At filesystem creation time, a ratio of (maximum number of inodes) / (filesystem size) is set, and that cannot be changed as an on-line operation. As a result, the resize2fs needs to extend the inode table to maintain the ratio as the filesystem is extended. Commented Mar 10, 2019 at 8:56