Not sure which sub-forum this belongs so I put it here. This is also not a vanilla FreeBSD system (freeNAS 11.2 which should be based on FreeNAS 11.2) but I feel is more FreeBSD related.
I wrote myself a little script that uses
I feel some insights into source code is needed here. Why is this command with a seemly non-critical function made uninterruptible (I believe there should be good reason)? Or it's not the command but the drivers? Any idea is welcome.
my hardware:
Dell R620 as head unit:
Dual E5 2690 v2
128GB RAM
2 s3500 80G, boot drive
T520-CR
LSI 9207 8e
P3700, slog
NetAPP DS4243 as DAS:
24 3.5 Bay
IOM6
8 4TB HGST NL SAS drives HUS726040AL5210: 4 2-way mirrors
8 10TB WD: 1 Raid Z2
I wrote myself a little script that uses
sesutil locate $disk on
to blink LED of failed disks and sesutil locate $disk off
to un-blink good disks automatically. I set a cron job to have it run every minute and everything seems to work fine. However, after a week or so the script got hanged because the sesutil locate $disk off
(to turn off LED for good disks) command stuck in D state (uninterruptible wait). Furthermore, every and each new sesutil locate $disk off
will stuck in the same state so append a & would just create a pile of them in the same state. Only a reboot can solve the problem for a while and them it repeats.I feel some insights into source code is needed here. Why is this command with a seemly non-critical function made uninterruptible (I believe there should be good reason)? Or it's not the command but the drivers? Any idea is welcome.
my hardware:
Dell R620 as head unit:
Dual E5 2690 v2
128GB RAM
2 s3500 80G, boot drive
T520-CR
LSI 9207 8e
P3700, slog
NetAPP DS4243 as DAS:
24 3.5 Bay
IOM6
8 4TB HGST NL SAS drives HUS726040AL5210: 4 2-way mirrors
8 10TB WD: 1 Raid Z2