solaris.pro / Field manuals / ZFS

ZFS datasets, properties and quotas

Build manageable filesystem boundaries and prevent uncontrolled growth

Scope: Oracle Solaris 11.4 and, for LDoms, compatible SPARC hardware with Oracle VM Server for SPARC. Examples are educational: verify release, privileges, target names and backups before running changes.

How it works

Dataset boundaries

Separate applications, logs and backups when their quota, snapshot and mount policies differ.

Properties

Compression, recordsize, atime and sync affect different workload patterns.

Quota versus reservation

Quotas cap usage; reservations guarantee capacity at the cost of flexibility.

Worked examples

Each example explains the question it answers, a reproducible starting point, what to look for, and operational precautions.

1. Create filesystem

Use this as a starting point for create filesystem.

zfs create tank/apps

Interpretation: Check command output against the expected host configuration; record the before/after state.

Operational note: Run commands in a test environment first; confirm device names, privileges and release-specific options.

2. Enable compression

Use this as a starting point for enable compression.

zfs set compression=lz4 tank/apps

Interpretation: Check command output against the expected host configuration; record the before/after state.

Operational note: Run commands in a test environment first; confirm device names, privileges and release-specific options.

3. Inspect inherited properties

Use this as a starting point for inspect inherited properties.

zfs get -r compression,recordsize,atime tank/apps

Interpretation: Check command output against the expected host configuration; record the before/after state.

Operational note: Run commands in a test environment first; confirm device names, privileges and release-specific options.

4. Set quota

Use this as a starting point for set quota.

zfs set quota=100G tank/apps

Interpretation: Check command output against the expected host configuration; record the before/after state.

Operational note: Run commands in a test environment first; confirm device names, privileges and release-specific options.

5. Review space

Use this as a starting point for review space.

zfs list -o name,used,avail,refer,mountpoint

Interpretation: Check command output against the expected host configuration; record the before/after state.

Operational note: Run commands in a test environment first; confirm device names, privileges and release-specific options.

Primary documentation

Read the relevant Oracle documentation for exact version-specific flags, supported platforms and limitations: Oracle primary reference ↗.

This field manual is independent, not affiliated with or endorsed by Oracle. Command examples should be adapted to your environment.