Forum Discussion
"What is the meaning of Bad file descriptor in this context?"
In your case, it probably means that the bigd was trying to write to a file that has already been closed. Maybe because the interval settings you have or a software bug.
Can you post here the icmp monitor settings you have?
There is this bug, but does not apply to the version you have:
https://support.f5.com/csp/article/K48693281
"Should I run e2fsck?"
The physical disk is in the vCMP host, the vCMP guests only have virtual disks that a basically files in the vCMP host disk. If there was a problem with the disk, would probably affect all vCMP guests, and within the guests, not only the bigd process.
Anyway, you don't lose anything in checking that.
You can use the platform diagnostics for that, that is more user-friendly version:
https://support.f5.com/csp/article/K15442
However, there is also the smartctl command. Don't forget that you test the disk in the vCMP host.