.System files on all pools and boot disks

[Kuro Houou]

I am running the latest Bluefin release 22.12.2 and originally started with one pool (p01), then installed a new SSD pool (p00) for my apps to run on. I wanted to move the System Storage to the new app pool (p00) and went to System Settings -> Advanced -> Storage Configuration and changed it from P01 to P00 then rebooted. I then noticed in my snapshots it was creating snapshots of .System folders on both P00 and P01. Then I decided to investigate further and ran,

zfs list -t filesystem | grep -F ".system"

I then showed me .System folders not only on P00 and P01 but also my boot pool.

I don't know why I would have .System folders on both boot pools and my boot disks (a mirrored set of USB/System flash storage) but I know running system files on the boot disk isn't recommended with a USB drive thats for sure...

zfs list -t filesystem | grep -F ".system" boot-pool/.system 16.9M 52.6G 128K legacy boot-pool/.system/configs-40cc91dacae0491e84781ab81ded8ba4 96K 52.6G 96K legacy boot-pool/.system/cores 96K 1024M 96K legacy boot-pool/.system/ctdb_shared_vol 96K 52.6G 96K legacy boot-pool/.system/glusterd 96K 52.6G 96K legacy boot-pool/.system/rrd-40cc91dacae0491e84781ab81ded8ba4 15.5M 52.6G 15.5M legacy boot-pool/.system/samba4 348K 52.6G 240K legacy boot-pool/.system/services 96K 52.6G 96K legacy boot-pool/.system/syslog-40cc91dacae0491e84781ab81ded8ba4 408K 52.6G 408K legacy boot-pool/.system/webui 96K 52.6G 96K legacy p00/.system 168M 1.71T 160K legacy p00/.system/configs-40cc91dacae0491e84781ab81ded8ba4 890K 1.71T 730K legacy p00/.system/cores 506K 1024M 506K legacy p00/.system/ctdb_shared_vol 128K 1.71T 128K legacy p00/.system/glusterd 139K 1.71T 139K legacy p00/.system/rrd-40cc91dacae0491e84781ab81ded8ba4 147M 1.71T 56.3M legacy p00/.system/samba4 1012K 1.71T 533K legacy p00/.system/services 128K 1.71T 128K legacy p00/.system/syslog-40cc91dacae0491e84781ab81ded8ba4 18.7M 1.71T 13.5M legacy p00/.system/webui 128K 1.71T 128K legacy p01/.system 119M 44.9T 240K legacy p01/.system/configs-40cc91dacae0491e84781ab81ded8ba4 392K 44.9T 392K legacy p01/.system/configs-8f179c8648fc4419af075a5cf26c19f8 320K 44.9T 320K legacy p01/.system/cores 591K 1023M 591K legacy p01/.system/ctdb_shared_vol 192K 44.9T 192K legacy p01/.system/glusterd 192K 44.9T 192K legacy p01/.system/rrd-40cc91dacae0491e84781ab81ded8ba4 40.9M 44.9T 40.9M legacy p01/.system/rrd-8f179c8648fc4419af075a5cf26c19f8 60.2M 44.9T 60.2M legacy p01/.system/samba4 1.23M 44.9T 1.23M legacy p01/.system/services 192K 44.9T 192K legacy p01/.system/syslog-40cc91dacae0491e84781ab81ded8ba4 8.34M 44.9T 8.34M legacy p01/.system/syslog-8f179c8648fc4419af075a5cf26c19f8 6.52M 44.9T 6.52M legacy p01/.system/webui 192K 44.9T 192K legacy

Anyways, anyone know why I see these .System folders on all three locations? How do I make them only on my SSD P00 Pool? Can I delete the others somehow? Last I have a backup server running the same version of TrueNAS Scale, was an upgrade from Core. It only shows the .System folders on one pool (not the boot or second pool in that server). So I know something is wrong here...

Thanks

 

[winnielinnie]

Could be a remnant from an earlier configuration.

If you can confirm that the other two .system datasets (and their children) are not mounted nor active, then you can safely delete them.

 

[Kuro Houou]

Could be a remnant from an earlier configuration.

If you can confirm that the other two .system datasets (and their children) are not mounted nor active, then you can safely delete them.

Yeah, guessing maybe this server had .system on the boot-pool as that was the only pool that existed when I built the server and the other backup server was an upgrade so it could go directly to my apps pool there. So I ended up running zfs destory -r p01/.system and the same but with the boot-pool and everything works fine, did a reboot and no issues.