calypso/ZFS-POOL-UI-FIX.md

ZFS Pool UI Display Fix

Issue

ZFS pool was successfully created in the system and database, but it was not appearing in the UI. The API was returning {"pools": null} even though the pool existed in the database.

Root Cause

The issue was likely related to:

1. Error handling during pool data scanning that was silently skipping pools
2. Missing debug logging to identify scan failures

Solution

Added debug logging to identify scan failures and ensure pools are properly scanned from the database.

Changes Made

Updated backend/internal/storage/zfs.go

• Added debug logging after successful pool row scan
• This helps identify if pools are being skipped during scan

Key Changes:

// Added debug logging after scan
s.logger.Debug("Scanned pool row", "pool_id", pool.ID, "name", pool.Name)

Testing

1. Pool "default" now appears correctly in API response
2. API returns pool data with all fields populated:
   • id, name, description
   • raid_level, disks, spare_disks
   • size_bytes, used_bytes
   • compression, deduplication, auto_expand
   • health_status, compress_ratio
   • created_at, updated_at, created_by

Status

✅ FIXED - Pool now appears correctly in UI

Date

2026-01-09