Example:
- Code: Select all
sh-3.2$ zfs list
NAME USED AVAIL REFER MOUNTPOINT
flakylaciebde 457Gi 29.3Mi 415Gi /Volumes/flakylaciebde
gjp22 381Gi 182Gi 302Gi /Volumes/gjp22
tall 1.73Ti 66.5Gi 440Gi /Volumes/tall
tall/backups 849Gi 66.5Gi 10.9Gi /Volumes/tall/backups
tall/backups/LaCie d2 Extreme 1.92Mi 66.5Gi 696Ki /Volumes/tall/backups/LaCie d2 Extreme
tall/backups/LaCie d2 Extreme/11G 644Ki 66.5Gi 644Ki /Volumes/tall/backups/LaCie d2 Extreme/11G
tall/backups/LaCie d2 Extreme/12A 628Ki 66.5Gi 628Ki /Volumes/tall/backups/LaCie d2 Extreme/12A
tall/backups/blocky 3.31Gi 66.5Gi 3.31Gi /Volumes/tall/backups/blocky
tall/backups/gjp22 376Gi 66.5Gi 301Gi /Volumes/tall/backups/gjp22
tall/backups/zhandy 458Gi 66.5Gi 398Gi /Volumes/tall/backups/zhandy
tall/backups/zhandy/Pocket Time Machine 52.8Gi 66.5Gi 52.8Gi /Volumes/tall/backups/zhandy/Pocket Time Machine
zhandy 537Gi 45.6Gi 411Gi /Volumes/zhandy
zhandy/Pocket Time Machine 50.2Gi 45.6Gi 50.2Gi /Volumes/zhandy/Pocket Time Machine
sh-3.2$
For that example, the datasets not shown by System Information are:
- flakylaciebde (no children)
- gjp22 (no children)
- tall (parent of backups)
- zhandy (parent of Pocket Time Machine).
I vaguely recall reporting to Apple a bug relating to System Information recognition of ZFS volumes, but that might have before I experimented with child file systems. (At the moment I can find neither my draft of that report, nor a follow-up number – sorry.)
Notes
As Disk Utility visualises some children at the parent level, I doubt that this problem is at the System Information.app level.
Whatever the root cause:
- for ZEVO Community Edition 1.1, command line approaches are encouraged.