How is the size of a filesystem defined?












0















man resize2fs says




The resize2fs program will resize ext2, ext3, or ext4 file systems. It can be used to enlarge or
shrink an unmounted file system located on device. ...
The size parameter specifies the requested new size of the filesystem




How do you choose a size parameter to specify to resize2fs? More specifically:



How is the size of a filesystem defined?



Does it count external fragmentation and/or internal fragmentation?
If it doesn't count external fragmentation but counts internal fragmentation, the size of a filesystem should be the same, as long as resize2fs doesn't modify or remove the existing files.



Does it count the space for storing inodes and the space for root usage, such as defragmentation?



Do df's and gparted's "used" columns show the size of each file system? Can the "used" numbers be used for choosing a size parameter for resize2fs? Note that df's and gparted's "used" columns show different used numbers for the same partition, and not sure why.



Thanks.










share|improve this question





























    0















    man resize2fs says




    The resize2fs program will resize ext2, ext3, or ext4 file systems. It can be used to enlarge or
    shrink an unmounted file system located on device. ...
    The size parameter specifies the requested new size of the filesystem




    How do you choose a size parameter to specify to resize2fs? More specifically:



    How is the size of a filesystem defined?



    Does it count external fragmentation and/or internal fragmentation?
    If it doesn't count external fragmentation but counts internal fragmentation, the size of a filesystem should be the same, as long as resize2fs doesn't modify or remove the existing files.



    Does it count the space for storing inodes and the space for root usage, such as defragmentation?



    Do df's and gparted's "used" columns show the size of each file system? Can the "used" numbers be used for choosing a size parameter for resize2fs? Note that df's and gparted's "used" columns show different used numbers for the same partition, and not sure why.



    Thanks.










    share|improve this question



























      0












      0








      0








      man resize2fs says




      The resize2fs program will resize ext2, ext3, or ext4 file systems. It can be used to enlarge or
      shrink an unmounted file system located on device. ...
      The size parameter specifies the requested new size of the filesystem




      How do you choose a size parameter to specify to resize2fs? More specifically:



      How is the size of a filesystem defined?



      Does it count external fragmentation and/or internal fragmentation?
      If it doesn't count external fragmentation but counts internal fragmentation, the size of a filesystem should be the same, as long as resize2fs doesn't modify or remove the existing files.



      Does it count the space for storing inodes and the space for root usage, such as defragmentation?



      Do df's and gparted's "used" columns show the size of each file system? Can the "used" numbers be used for choosing a size parameter for resize2fs? Note that df's and gparted's "used" columns show different used numbers for the same partition, and not sure why.



      Thanks.










      share|improve this question
















      man resize2fs says




      The resize2fs program will resize ext2, ext3, or ext4 file systems. It can be used to enlarge or
      shrink an unmounted file system located on device. ...
      The size parameter specifies the requested new size of the filesystem




      How do you choose a size parameter to specify to resize2fs? More specifically:



      How is the size of a filesystem defined?



      Does it count external fragmentation and/or internal fragmentation?
      If it doesn't count external fragmentation but counts internal fragmentation, the size of a filesystem should be the same, as long as resize2fs doesn't modify or remove the existing files.



      Does it count the space for storing inodes and the space for root usage, such as defragmentation?



      Do df's and gparted's "used" columns show the size of each file system? Can the "used" numbers be used for choosing a size parameter for resize2fs? Note that df's and gparted's "used" columns show different used numbers for the same partition, and not sure why.



      Thanks.







      filesystems partition resize2fs






      share|improve this question















      share|improve this question













      share|improve this question




      share|improve this question








      edited Feb 20 at 12:25







      Tim

















      asked Feb 20 at 12:19









      TimTim

      27.5k78264476




      27.5k78264476






















          1 Answer
          1






          active

          oldest

          votes


















          4














          The size of a file system, as used for resize2fs (and mke2fs and other similar tools) is the external size of the file system, i.e. the amount of space it occupies as viewed from the outside. The internal data structures of the file system don’t matter here. Everything in the file system — metadata, data, and unused space within the file system — fits within the file system’s size. This also includes any boot loader hosted in the same partition as the file system, where such a configuration is possible (it is with Ext2/3/4, not with XFS, for example).



          The best way to determine the current size of a file system is to read it from the file system; for example, for ext2/3/4 file systems, you’d multiply the block count by the block size:



          dumpe2fs -h /path/to/file/system | grep -E 'Block (count|size):'


          By default, the size of a file system is usually the size of its container, e.g. its containing partition or logical volume. This is the value that resize2fs will use if you don’t specify a size explicitly. Specifying size is useful when you want to shrink a file system and its container: you’d start by running resize2fs with the target size, and then shrink the container (partition, logical volume, etc.) to match.



          To determine the minimum size to which you can shrink a file system, the best approach is to use resize2fs itself:



          resize2fs -M -P /path/to/file/system


          will tell you how many blocks a minimal file system would occupy (preserving all the current contents); to determine the block size used, run



          dumpe2fs -h /path/to/file/system | grep Block size


          You can get the details of the calculation by adding -d 32:



          resize2fs -d 32 -M -P /path/to/file/system


          The maximum size of a file system is usually the size of its container (partition or logical volume). A file system which is in a partition or logical volume can never be bigger than the partition or logical volume; there can be additional constraints which limit the extent to which a file system can grow. (File systems stored in image files behave differently, resize2fs changes the file size to match the file system size, whether growing or shrinking.)






          share|improve this answer


























          • Thanks. (1) Since the size parameter doesn't mean the target used size in the partition of the file system, an resize2fs won't remove or modify existing files in any case, what is the purpose of the size parameter? (2) What is "the external size of the file system, i.e. the amount of space it occupies as viewed from the outside"? Does it count external fragmentation and/or internal fragmentation? Does it count the space for storing inodes and the space for root usage (defragmentation)? (3) Can df's and gparted's "used" columns be useful for choosing a size parameter for resize2fs?

            – Tim
            Feb 20 at 13:36











          • No, I don't, but I often check if you did. (1) "Everything in the file system — metadata and data — fits within the file system’s size." How about external fragmentation, i.e. the free space holes between files? I believe it counts internal fragmentation. (2) by resize, do you mean for terminal?

            – Tim
            Feb 20 at 14:19













          • (1) Sorry, feel difficulty understanding your analogy. I am surprised that you don't know about it, while it is understandable that I don't. external fragmentation means the free space in the partition is split into pieces by files (or parts of files). So does the size of a file system count the holes between files (or file parts)?

            – Tim
            Feb 20 at 14:39













          • Forget about partitions, we’re talking about file systems here. The space between files is still inside the file system, so yes, it’s part of the file system’s size. Otherwise a file system’s size would change as you add and remove files.

            – Stephen Kitt
            Feb 20 at 14:44






          • 1





            @炸鱼薯条德里克 I was trying to clarify that the file system’s size isn’t one of the “internal” sizes visible using df etc., to address Tim’s questions about fragmentation and so on. In my mind the underlying storage is a separate issue; when you look at the apparent size of a sparse file, you still see the full size (“space it occupies as viewed from the outside”). How can resize2fs “help you resize the container in just one run”? I thought that was fsadm.

            – Stephen Kitt
            Feb 21 at 10:10











          Your Answer








          StackExchange.ready(function() {
          var channelOptions = {
          tags: "".split(" "),
          id: "106"
          };
          initTagRenderer("".split(" "), "".split(" "), channelOptions);

          StackExchange.using("externalEditor", function() {
          // Have to fire editor after snippets, if snippets enabled
          if (StackExchange.settings.snippets.snippetsEnabled) {
          StackExchange.using("snippets", function() {
          createEditor();
          });
          }
          else {
          createEditor();
          }
          });

          function createEditor() {
          StackExchange.prepareEditor({
          heartbeatType: 'answer',
          autoActivateHeartbeat: false,
          convertImagesToLinks: false,
          noModals: true,
          showLowRepImageUploadWarning: true,
          reputationToPostImages: null,
          bindNavPrevention: true,
          postfix: "",
          imageUploader: {
          brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
          contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
          allowUrls: true
          },
          onDemand: true,
          discardSelector: ".discard-answer"
          ,immediatelyShowMarkdownHelp:true
          });


          }
          });














          draft saved

          draft discarded


















          StackExchange.ready(
          function () {
          StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2funix.stackexchange.com%2fquestions%2f501843%2fhow-is-the-size-of-a-filesystem-defined%23new-answer', 'question_page');
          }
          );

          Post as a guest















          Required, but never shown

























          1 Answer
          1






          active

          oldest

          votes








          1 Answer
          1






          active

          oldest

          votes









          active

          oldest

          votes






          active

          oldest

          votes









          4














          The size of a file system, as used for resize2fs (and mke2fs and other similar tools) is the external size of the file system, i.e. the amount of space it occupies as viewed from the outside. The internal data structures of the file system don’t matter here. Everything in the file system — metadata, data, and unused space within the file system — fits within the file system’s size. This also includes any boot loader hosted in the same partition as the file system, where such a configuration is possible (it is with Ext2/3/4, not with XFS, for example).



          The best way to determine the current size of a file system is to read it from the file system; for example, for ext2/3/4 file systems, you’d multiply the block count by the block size:



          dumpe2fs -h /path/to/file/system | grep -E 'Block (count|size):'


          By default, the size of a file system is usually the size of its container, e.g. its containing partition or logical volume. This is the value that resize2fs will use if you don’t specify a size explicitly. Specifying size is useful when you want to shrink a file system and its container: you’d start by running resize2fs with the target size, and then shrink the container (partition, logical volume, etc.) to match.



          To determine the minimum size to which you can shrink a file system, the best approach is to use resize2fs itself:



          resize2fs -M -P /path/to/file/system


          will tell you how many blocks a minimal file system would occupy (preserving all the current contents); to determine the block size used, run



          dumpe2fs -h /path/to/file/system | grep Block size


          You can get the details of the calculation by adding -d 32:



          resize2fs -d 32 -M -P /path/to/file/system


          The maximum size of a file system is usually the size of its container (partition or logical volume). A file system which is in a partition or logical volume can never be bigger than the partition or logical volume; there can be additional constraints which limit the extent to which a file system can grow. (File systems stored in image files behave differently, resize2fs changes the file size to match the file system size, whether growing or shrinking.)






          share|improve this answer


























          • Thanks. (1) Since the size parameter doesn't mean the target used size in the partition of the file system, an resize2fs won't remove or modify existing files in any case, what is the purpose of the size parameter? (2) What is "the external size of the file system, i.e. the amount of space it occupies as viewed from the outside"? Does it count external fragmentation and/or internal fragmentation? Does it count the space for storing inodes and the space for root usage (defragmentation)? (3) Can df's and gparted's "used" columns be useful for choosing a size parameter for resize2fs?

            – Tim
            Feb 20 at 13:36











          • No, I don't, but I often check if you did. (1) "Everything in the file system — metadata and data — fits within the file system’s size." How about external fragmentation, i.e. the free space holes between files? I believe it counts internal fragmentation. (2) by resize, do you mean for terminal?

            – Tim
            Feb 20 at 14:19













          • (1) Sorry, feel difficulty understanding your analogy. I am surprised that you don't know about it, while it is understandable that I don't. external fragmentation means the free space in the partition is split into pieces by files (or parts of files). So does the size of a file system count the holes between files (or file parts)?

            – Tim
            Feb 20 at 14:39













          • Forget about partitions, we’re talking about file systems here. The space between files is still inside the file system, so yes, it’s part of the file system’s size. Otherwise a file system’s size would change as you add and remove files.

            – Stephen Kitt
            Feb 20 at 14:44






          • 1





            @炸鱼薯条德里克 I was trying to clarify that the file system’s size isn’t one of the “internal” sizes visible using df etc., to address Tim’s questions about fragmentation and so on. In my mind the underlying storage is a separate issue; when you look at the apparent size of a sparse file, you still see the full size (“space it occupies as viewed from the outside”). How can resize2fs “help you resize the container in just one run”? I thought that was fsadm.

            – Stephen Kitt
            Feb 21 at 10:10
















          4














          The size of a file system, as used for resize2fs (and mke2fs and other similar tools) is the external size of the file system, i.e. the amount of space it occupies as viewed from the outside. The internal data structures of the file system don’t matter here. Everything in the file system — metadata, data, and unused space within the file system — fits within the file system’s size. This also includes any boot loader hosted in the same partition as the file system, where such a configuration is possible (it is with Ext2/3/4, not with XFS, for example).



          The best way to determine the current size of a file system is to read it from the file system; for example, for ext2/3/4 file systems, you’d multiply the block count by the block size:



          dumpe2fs -h /path/to/file/system | grep -E 'Block (count|size):'


          By default, the size of a file system is usually the size of its container, e.g. its containing partition or logical volume. This is the value that resize2fs will use if you don’t specify a size explicitly. Specifying size is useful when you want to shrink a file system and its container: you’d start by running resize2fs with the target size, and then shrink the container (partition, logical volume, etc.) to match.



          To determine the minimum size to which you can shrink a file system, the best approach is to use resize2fs itself:



          resize2fs -M -P /path/to/file/system


          will tell you how many blocks a minimal file system would occupy (preserving all the current contents); to determine the block size used, run



          dumpe2fs -h /path/to/file/system | grep Block size


          You can get the details of the calculation by adding -d 32:



          resize2fs -d 32 -M -P /path/to/file/system


          The maximum size of a file system is usually the size of its container (partition or logical volume). A file system which is in a partition or logical volume can never be bigger than the partition or logical volume; there can be additional constraints which limit the extent to which a file system can grow. (File systems stored in image files behave differently, resize2fs changes the file size to match the file system size, whether growing or shrinking.)






          share|improve this answer


























          • Thanks. (1) Since the size parameter doesn't mean the target used size in the partition of the file system, an resize2fs won't remove or modify existing files in any case, what is the purpose of the size parameter? (2) What is "the external size of the file system, i.e. the amount of space it occupies as viewed from the outside"? Does it count external fragmentation and/or internal fragmentation? Does it count the space for storing inodes and the space for root usage (defragmentation)? (3) Can df's and gparted's "used" columns be useful for choosing a size parameter for resize2fs?

            – Tim
            Feb 20 at 13:36











          • No, I don't, but I often check if you did. (1) "Everything in the file system — metadata and data — fits within the file system’s size." How about external fragmentation, i.e. the free space holes between files? I believe it counts internal fragmentation. (2) by resize, do you mean for terminal?

            – Tim
            Feb 20 at 14:19













          • (1) Sorry, feel difficulty understanding your analogy. I am surprised that you don't know about it, while it is understandable that I don't. external fragmentation means the free space in the partition is split into pieces by files (or parts of files). So does the size of a file system count the holes between files (or file parts)?

            – Tim
            Feb 20 at 14:39













          • Forget about partitions, we’re talking about file systems here. The space between files is still inside the file system, so yes, it’s part of the file system’s size. Otherwise a file system’s size would change as you add and remove files.

            – Stephen Kitt
            Feb 20 at 14:44






          • 1





            @炸鱼薯条德里克 I was trying to clarify that the file system’s size isn’t one of the “internal” sizes visible using df etc., to address Tim’s questions about fragmentation and so on. In my mind the underlying storage is a separate issue; when you look at the apparent size of a sparse file, you still see the full size (“space it occupies as viewed from the outside”). How can resize2fs “help you resize the container in just one run”? I thought that was fsadm.

            – Stephen Kitt
            Feb 21 at 10:10














          4












          4








          4







          The size of a file system, as used for resize2fs (and mke2fs and other similar tools) is the external size of the file system, i.e. the amount of space it occupies as viewed from the outside. The internal data structures of the file system don’t matter here. Everything in the file system — metadata, data, and unused space within the file system — fits within the file system’s size. This also includes any boot loader hosted in the same partition as the file system, where such a configuration is possible (it is with Ext2/3/4, not with XFS, for example).



          The best way to determine the current size of a file system is to read it from the file system; for example, for ext2/3/4 file systems, you’d multiply the block count by the block size:



          dumpe2fs -h /path/to/file/system | grep -E 'Block (count|size):'


          By default, the size of a file system is usually the size of its container, e.g. its containing partition or logical volume. This is the value that resize2fs will use if you don’t specify a size explicitly. Specifying size is useful when you want to shrink a file system and its container: you’d start by running resize2fs with the target size, and then shrink the container (partition, logical volume, etc.) to match.



          To determine the minimum size to which you can shrink a file system, the best approach is to use resize2fs itself:



          resize2fs -M -P /path/to/file/system


          will tell you how many blocks a minimal file system would occupy (preserving all the current contents); to determine the block size used, run



          dumpe2fs -h /path/to/file/system | grep Block size


          You can get the details of the calculation by adding -d 32:



          resize2fs -d 32 -M -P /path/to/file/system


          The maximum size of a file system is usually the size of its container (partition or logical volume). A file system which is in a partition or logical volume can never be bigger than the partition or logical volume; there can be additional constraints which limit the extent to which a file system can grow. (File systems stored in image files behave differently, resize2fs changes the file size to match the file system size, whether growing or shrinking.)






          share|improve this answer















          The size of a file system, as used for resize2fs (and mke2fs and other similar tools) is the external size of the file system, i.e. the amount of space it occupies as viewed from the outside. The internal data structures of the file system don’t matter here. Everything in the file system — metadata, data, and unused space within the file system — fits within the file system’s size. This also includes any boot loader hosted in the same partition as the file system, where such a configuration is possible (it is with Ext2/3/4, not with XFS, for example).



          The best way to determine the current size of a file system is to read it from the file system; for example, for ext2/3/4 file systems, you’d multiply the block count by the block size:



          dumpe2fs -h /path/to/file/system | grep -E 'Block (count|size):'


          By default, the size of a file system is usually the size of its container, e.g. its containing partition or logical volume. This is the value that resize2fs will use if you don’t specify a size explicitly. Specifying size is useful when you want to shrink a file system and its container: you’d start by running resize2fs with the target size, and then shrink the container (partition, logical volume, etc.) to match.



          To determine the minimum size to which you can shrink a file system, the best approach is to use resize2fs itself:



          resize2fs -M -P /path/to/file/system


          will tell you how many blocks a minimal file system would occupy (preserving all the current contents); to determine the block size used, run



          dumpe2fs -h /path/to/file/system | grep Block size


          You can get the details of the calculation by adding -d 32:



          resize2fs -d 32 -M -P /path/to/file/system


          The maximum size of a file system is usually the size of its container (partition or logical volume). A file system which is in a partition or logical volume can never be bigger than the partition or logical volume; there can be additional constraints which limit the extent to which a file system can grow. (File systems stored in image files behave differently, resize2fs changes the file size to match the file system size, whether growing or shrinking.)







          share|improve this answer














          share|improve this answer



          share|improve this answer








          edited Feb 21 at 14:06

























          answered Feb 20 at 12:39









          Stephen KittStephen Kitt

          175k24400477




          175k24400477













          • Thanks. (1) Since the size parameter doesn't mean the target used size in the partition of the file system, an resize2fs won't remove or modify existing files in any case, what is the purpose of the size parameter? (2) What is "the external size of the file system, i.e. the amount of space it occupies as viewed from the outside"? Does it count external fragmentation and/or internal fragmentation? Does it count the space for storing inodes and the space for root usage (defragmentation)? (3) Can df's and gparted's "used" columns be useful for choosing a size parameter for resize2fs?

            – Tim
            Feb 20 at 13:36











          • No, I don't, but I often check if you did. (1) "Everything in the file system — metadata and data — fits within the file system’s size." How about external fragmentation, i.e. the free space holes between files? I believe it counts internal fragmentation. (2) by resize, do you mean for terminal?

            – Tim
            Feb 20 at 14:19













          • (1) Sorry, feel difficulty understanding your analogy. I am surprised that you don't know about it, while it is understandable that I don't. external fragmentation means the free space in the partition is split into pieces by files (or parts of files). So does the size of a file system count the holes between files (or file parts)?

            – Tim
            Feb 20 at 14:39













          • Forget about partitions, we’re talking about file systems here. The space between files is still inside the file system, so yes, it’s part of the file system’s size. Otherwise a file system’s size would change as you add and remove files.

            – Stephen Kitt
            Feb 20 at 14:44






          • 1





            @炸鱼薯条德里克 I was trying to clarify that the file system’s size isn’t one of the “internal” sizes visible using df etc., to address Tim’s questions about fragmentation and so on. In my mind the underlying storage is a separate issue; when you look at the apparent size of a sparse file, you still see the full size (“space it occupies as viewed from the outside”). How can resize2fs “help you resize the container in just one run”? I thought that was fsadm.

            – Stephen Kitt
            Feb 21 at 10:10



















          • Thanks. (1) Since the size parameter doesn't mean the target used size in the partition of the file system, an resize2fs won't remove or modify existing files in any case, what is the purpose of the size parameter? (2) What is "the external size of the file system, i.e. the amount of space it occupies as viewed from the outside"? Does it count external fragmentation and/or internal fragmentation? Does it count the space for storing inodes and the space for root usage (defragmentation)? (3) Can df's and gparted's "used" columns be useful for choosing a size parameter for resize2fs?

            – Tim
            Feb 20 at 13:36











          • No, I don't, but I often check if you did. (1) "Everything in the file system — metadata and data — fits within the file system’s size." How about external fragmentation, i.e. the free space holes between files? I believe it counts internal fragmentation. (2) by resize, do you mean for terminal?

            – Tim
            Feb 20 at 14:19













          • (1) Sorry, feel difficulty understanding your analogy. I am surprised that you don't know about it, while it is understandable that I don't. external fragmentation means the free space in the partition is split into pieces by files (or parts of files). So does the size of a file system count the holes between files (or file parts)?

            – Tim
            Feb 20 at 14:39













          • Forget about partitions, we’re talking about file systems here. The space between files is still inside the file system, so yes, it’s part of the file system’s size. Otherwise a file system’s size would change as you add and remove files.

            – Stephen Kitt
            Feb 20 at 14:44






          • 1





            @炸鱼薯条德里克 I was trying to clarify that the file system’s size isn’t one of the “internal” sizes visible using df etc., to address Tim’s questions about fragmentation and so on. In my mind the underlying storage is a separate issue; when you look at the apparent size of a sparse file, you still see the full size (“space it occupies as viewed from the outside”). How can resize2fs “help you resize the container in just one run”? I thought that was fsadm.

            – Stephen Kitt
            Feb 21 at 10:10

















          Thanks. (1) Since the size parameter doesn't mean the target used size in the partition of the file system, an resize2fs won't remove or modify existing files in any case, what is the purpose of the size parameter? (2) What is "the external size of the file system, i.e. the amount of space it occupies as viewed from the outside"? Does it count external fragmentation and/or internal fragmentation? Does it count the space for storing inodes and the space for root usage (defragmentation)? (3) Can df's and gparted's "used" columns be useful for choosing a size parameter for resize2fs?

          – Tim
          Feb 20 at 13:36





          Thanks. (1) Since the size parameter doesn't mean the target used size in the partition of the file system, an resize2fs won't remove or modify existing files in any case, what is the purpose of the size parameter? (2) What is "the external size of the file system, i.e. the amount of space it occupies as viewed from the outside"? Does it count external fragmentation and/or internal fragmentation? Does it count the space for storing inodes and the space for root usage (defragmentation)? (3) Can df's and gparted's "used" columns be useful for choosing a size parameter for resize2fs?

          – Tim
          Feb 20 at 13:36













          No, I don't, but I often check if you did. (1) "Everything in the file system — metadata and data — fits within the file system’s size." How about external fragmentation, i.e. the free space holes between files? I believe it counts internal fragmentation. (2) by resize, do you mean for terminal?

          – Tim
          Feb 20 at 14:19







          No, I don't, but I often check if you did. (1) "Everything in the file system — metadata and data — fits within the file system’s size." How about external fragmentation, i.e. the free space holes between files? I believe it counts internal fragmentation. (2) by resize, do you mean for terminal?

          – Tim
          Feb 20 at 14:19















          (1) Sorry, feel difficulty understanding your analogy. I am surprised that you don't know about it, while it is understandable that I don't. external fragmentation means the free space in the partition is split into pieces by files (or parts of files). So does the size of a file system count the holes between files (or file parts)?

          – Tim
          Feb 20 at 14:39







          (1) Sorry, feel difficulty understanding your analogy. I am surprised that you don't know about it, while it is understandable that I don't. external fragmentation means the free space in the partition is split into pieces by files (or parts of files). So does the size of a file system count the holes between files (or file parts)?

          – Tim
          Feb 20 at 14:39















          Forget about partitions, we’re talking about file systems here. The space between files is still inside the file system, so yes, it’s part of the file system’s size. Otherwise a file system’s size would change as you add and remove files.

          – Stephen Kitt
          Feb 20 at 14:44





          Forget about partitions, we’re talking about file systems here. The space between files is still inside the file system, so yes, it’s part of the file system’s size. Otherwise a file system’s size would change as you add and remove files.

          – Stephen Kitt
          Feb 20 at 14:44




          1




          1





          @炸鱼薯条德里克 I was trying to clarify that the file system’s size isn’t one of the “internal” sizes visible using df etc., to address Tim’s questions about fragmentation and so on. In my mind the underlying storage is a separate issue; when you look at the apparent size of a sparse file, you still see the full size (“space it occupies as viewed from the outside”). How can resize2fs “help you resize the container in just one run”? I thought that was fsadm.

          – Stephen Kitt
          Feb 21 at 10:10





          @炸鱼薯条德里克 I was trying to clarify that the file system’s size isn’t one of the “internal” sizes visible using df etc., to address Tim’s questions about fragmentation and so on. In my mind the underlying storage is a separate issue; when you look at the apparent size of a sparse file, you still see the full size (“space it occupies as viewed from the outside”). How can resize2fs “help you resize the container in just one run”? I thought that was fsadm.

          – Stephen Kitt
          Feb 21 at 10:10


















          draft saved

          draft discarded




















































          Thanks for contributing an answer to Unix & Linux Stack Exchange!


          • Please be sure to answer the question. Provide details and share your research!

          But avoid



          • Asking for help, clarification, or responding to other answers.

          • Making statements based on opinion; back them up with references or personal experience.


          To learn more, see our tips on writing great answers.




          draft saved


          draft discarded














          StackExchange.ready(
          function () {
          StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2funix.stackexchange.com%2fquestions%2f501843%2fhow-is-the-size-of-a-filesystem-defined%23new-answer', 'question_page');
          }
          );

          Post as a guest















          Required, but never shown





















































          Required, but never shown














          Required, but never shown












          Required, but never shown







          Required, but never shown

































          Required, but never shown














          Required, but never shown












          Required, but never shown







          Required, but never shown







          Popular posts from this blog

          How to make a Squid Proxy server?

          Is this a new Fibonacci Identity?

          19世紀