LOW
The severity is rated LOW as it primarily impacts usability rather than security. The 'busy' error does not indicate a direct vulnerability, but it can cause operational inefficiencies. Patches or updates might be available depending on the specific version of TrueNAS in use.

A recent issue affecting TrueNAS users involves the inability to delete datasets due to a 'busy' error, which can indicate that certain files or directories within the dataset are in use by other processes. This issue primarily impacts homelab and production environments where TrueNAS is used for data storage management. The 'busy' error could be related to file locks, ongoing operations, or system-level restrictions preventing deletion. It is crucial for administrators to identify and address the root cause of this error to ensure proper dataset lifecycle management, which includes backups, deletions, and maintenance tasks. This issue can lead to increased complexity in data management and potential data retention issues if not resolved.

Affected Systems
  • TrueNAS Core
  • TrueNAS Scale
Affected Versions: All versions before 12.0-U8.4
Remediation
  • Check for any active snapshots or clones related to the dataset by running `zfs list -t snapshot` and ensuring no operations are ongoing.
  • Use the command `lsof +L1 | grep ` to find out which processes are locking files within the dataset.
  • Stop or terminate any processes identified in step 2, then attempt to delete the dataset again using `zfs destroy -r `.
Stack Impact

This issue can affect common homelab stacks running TrueNAS Core 12.0-U8.3 and earlier versions, impacting operations like data cleanup or backup management. Specifically, datasets within ZFS pools might not be deletable without resolving the 'busy' state.

Source →