Either works. Some people don’t like all the writes to the SSD / NMVe boot-pool. I have mine set to my data pool, a regular HD.
The root dataset of the first pool you create automatically becomes the system dataset, by default
Ah so that explains why it was set for the HDD dataset
But then it doesn’t exactly explain my other problem/thread - how come it’s my nvme boot drive that’s getting all the write activity? And the HDDs are actually getting basically zero when I’m not using it
I have made the opposit decision of smallbarky, keep the system dataset into boot pool, basically to avoid my data pool to unnecessary wake up from idle.
From what i see from MR, 1.1tb of data has been written in ~9500 hours, so nothing that should kill my boot pool (i use same 16gb optane)
I have seen your other thread, honestly your situation looks kinda odd and IMHO you should dig a bit more into it (but i can’t help you so much on how )