Table of ContentsView in Frames

Difference between a quota report and the df command in accounting space usage of CIFS sparse files

The value of the disk space that is displayed in a quota report for a volume on the storage system can be different from the value displayed by the output of the df command executed from the storage system for the same volume if the particular volume has CIFS sparse files.

The difference in the space usage values is because of the difference in methods followed by the quota report and the df command for calculating the empty data blocks in the CIFS sparse files.

When you run the df command on a volume containing CIFS sparse files, the empty data blocks in the sparse files are not counted towards the disk space. However, the quota report considers all the data blocks of the sparse files, including the empty blocks, while calculating the space usage. Therefore, the disk usage reported by the df command is less than the value reported by a quota report in case of volumes containing CIFS sparse files.

Example of the difference between space usage accounted by the df command and a quota report

The following quota report shows usage of 200 GB in a volume vol1:
system1>quota report
                                 K-Bytes             Files
Type       ID    Volume    Tree  Used      Limit     Used    Limit   Quota Specifier
----- -------- -------- -------- --------- --------- ------- ------- ---------------
tree    user1      vol1     q1   209900230         - 4373805       - /vol/vol1/q1
...
If vol1 has CIFS sparse files, the space usage for the same volume by means of the df command can be 100 GB less than the value specified in the quota report, as shown in the following example:
system1>df -V vol1
Filesystem         kbytes       used        avail     capacity   Mounted on
/vol/vol1/         367186630    105042630   262329030       28%  /vol/vol1/