Why does du(1) report different file sizes for ZFS and UFS?
On UFS, du(1) reports the size of the data blocks within the file. On ZFS, du(1) reports the actual size of the file as stored on disk. This size includes metadata as well as compression. This reporting really helps answer the question of “how much more space will I get if I remove this file?” So, even when compression is off, you will still see different results between ZFS and UFS. • Why doesn’t ZFS have user or group quotas? ZFS file systems can be used as logical administrative control points, which allow you to view usage, manage properties, perform backups, take snapshots, and so on. For home directory servers, the ZFS model enables you to easily set up one file system per user. ZFS quotas are intentionally not associated with a particular user because file systems are points of administrative control. ZFS quotas can be set on file systems that could represent users, projects, groups, and so on, as well as on entire portions of a file system hierarchy. This allows quotas to be co
Related Questions
- The Summary of Losses and Reserves report from one of my files is comprised of different columns than the same report from another file. Whats causing this variation?
- What does Live Upgrade do to migrate my UFS root file system to a ZFS root file system?
- Why does du(1) report different file sizes for ZFS and UFS?
