Inodes is restricted separately, but the blocks value also increases with the creation of Empty files.

Inodes restrictions are imposed separately, but blocks values also increase with the creation of Empty files-Linux general technology-Linux technology and application information. The following is a detailed description. : 0) 1. There are two ways to limit the disk quota: 1. The number of files that a user can create (inodes); 2. the disk size that the user can use. Started the disk quota of user1 under "/dev/hda5". Now I start the experiment on disk restrictions of user1 in this partition: only set restrictions on inodes, in inodes, the soft value is 6 and the hard value is 12. Save the setting and start to use user1 to create a new file under "/dev/hda5" and run the touch command, it should be okay to create the "1, 2, 3" file, run "edquota user1" under the root user to check if user1 is restricted under "/dev/hda5". At this time, the inodes value is 3, but what makes me incredible is: the blocks value also changes to 3! It's strange that the empty file created with the touch command does not occupy the block size! This is correct when I perform an experiment on the computer in the school data center. Why does the new file created with the touch command affect the change of the blocks value? Is it because the system in the school data center is different from the system kernel on my computer? (The Linux version I installed is Red Hat Enterprise Linux 4 downloaded from the Internet)