Drive activity

[jgreco]

I think that better than speculating on the individual hours of disk wear, you would (if you have the power) urge a solution to this problem. Whether in the Jira system or with your development colleagues.

Participants are reminded that the only iXsystems "development colleagues" here are people badged as iXsystems. Everyone else, community moderators included, are just community members.

Do not expect someone who is just a community member to take up your issue and fight your battles for you.

Do not expect complaints here in these forums to make a significant impact on iXsystems development.

You are able to file a request in Jira all on your own. It is likely to be ignored or not acted upon, as iXsystems has made it clear that this is a battle that cannot easily be won. Their target customer segment is commercial/enterprise, where disks spin 24/7. The design of the appliance requires some pool somewhere to soak up statistics and logging, and experience shows that this works better on the main data pool rather than on the boot pool. You are probably not going to find a developer who is anxious to "solve" this conundrum, because it turns out there's no good place to put the data on a system with its pool disks spun down.

You can probably engineer your own solution to this problem by creating a secondary SSD pool for the system dataset and then making certain the main pool is quiescent.