I read a couple of articles about Linux inode and understand that each file created always have a corresponding inode number. Since one of our servers is using ext4 there is no way to increase the inode to an already running production server.

There are two solutions we can do one is to delete older files and the other is to transfer older files to another server and archive it. My question now is if I archive and compress the files and then move it to another server. On the archive server how many inode number will be assigned to the compressed file I just transferred?


Collecting multiple files in a single archive file reduces inode consumption to that required to handle that file. The number of blocks used is not correspondingly guaranteed to be reduced (but it usually will be regardless).

  • Thanks for answering, so if I have 3 files which ideally should have 3 inode numbers. Once I archive and compress the file it will have less than 3 inode or ideally 1 inode number assigned to the archive file and the previous 3 inode numbers are freed up. Am I right in this assumption? – dimas Oct 25 '17 at 10:40
  • The inodes will only be freed up if the files are removed, of course. – Ignacio Vazquez-Abrams Oct 25 '17 at 10:41
  • ok, i just need to clarify this ... back on my original question. If i have 3 files and compressed/archived in Server A then transferred it to Server B. On Server B the OS will assign 4 inode number to the archived file I just transferred or just 1 inode? – dimas Oct 25 '17 at 10:47
  • Just the one, since there's just the one file. – Ignacio Vazquez-Abrams Oct 25 '17 at 10:48
  • i see thank you very much for clarifying that. – dimas Oct 25 '17 at 10:51

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Not the answer you're looking for? Browse other questions tagged or ask your own question.