Hi. I’m using Fangtooth 25.04, 6x18TB Z2.
I accidently created two identical jobs to extend the size of my ZFS pool by one drive.
So one job ‘pool.attach’ is running and 35% complete, with id 74, that will likely take days to complete.
Then there’s an identical ‘pool.attach’ job that is listed as ‘waiting’ with id 294 that I accidently created.
Is there a way to kill this identical job (294) that in waiting?
Cheers Scott.
Very good news. TrueNAS is robust.
TrueNAS automatically cancelled the duplicate job 294 (once the original job had finished), saying that the drive was ‘already in use’.
The job was tagged an an ‘error’ (rather than keeping it in ‘waiting’ status) so I guess I don’t expect the job to suddenly start.
I might submit a feature request to allow admins to cancel any waiting jobs through the web interface. I didn’t want to kill any process via the shell (or whatever, I’m not a Linux person really), because I didn’t know if it would also kill the legitable expansion job (and possibly corrupt my pool!).
