It would be interesting to know how you got into that situation. Do you have large files that exceed ~30GB? From your setup I assume you have situations where ES is forced to read >30GB from mmap-ed file as a whole, which is a bit surprising to me.
You will see this error if Linux kernel can no longer guarantee the integrity of an mmap-ed file to the JVM.
Either the disk is full and kernel mmap can't write to the file so it gets truncated, or RAM is full and the kernel can no longer write valid file buffers to disk so the mmap-ed file gets corrupted.
Using the most recent kernel version possible might help in order to get the JVM notified better. But, I think the reason is your system configuration is too lenient, you should not allow to get the kernel into that hard resource limit. Adjusting RAM for OS file system or limiting mmap could help to remedy the situation.