If the new burn-in feature would be non-destructive, I can imagine people using it on existing pools as well. Patience is almost rarer than RAM these days. TN could just show a warning about “impacting pool performance for an extended time and might also cause additional noise due to the stress test and maybe even increased cooling needs”. That should do it imho.
I would hope it would not. Validating the disk really calls for writing to every sector, then reading it back, ensuring that it reads back correctly. But further discussion probably belongs on the FR thread.
How is this related to being able to run a smart test via the gui? Couldn’t you have both, running you alert system while still allowing user run their own test via gui in addition to that, if they wanted to? Or were those actually leading to customer claiming disk being faulty and had to be replaced?
Yes, in many cases it would unnecessarily worry customers and require executive discussions on why the false alerts were raised and then ignored. That adds cost to both our customers and TrueNAS operations. The customer is right… “its your software raising the alert”