VMWARE - I/O error - EXT4-fs error (device dm-8): __ext4_get_inode_loc: unable to read inode block

VMWARE - I/O error - EXT4-fs error (device dm-8): __ext4_get_inode_loc: unable to read inode block

We have a ESX environment wherein we have a linux server which has iSCSI storage attached to it.
Since the iSCSI from the NetApp storage is mapped to the linux VM it doesnt find itself part of the datastore.
For some reason the linux OS stopped responding to the 1 TB iSCSI LUN.
I unmapped the LUN from the igroup and mapped it back.
The problem didnt go away.
On checking the logs of the server /var/log/messages
I found the following.
Even the reinitialize didnt do any wonder.
Oct  7 13:02:24 AF$$^&rod1 kernel: end_request: I/O error, dev dm-7, sector 2063176208
Oct  7 13:02:24 AF$$^&rod1 kernel: end_request: I/O error, dev dm-7, sector 1971791144
Oct  7 13:02:24 AF$$^&rod1 kernel: end_request: I/O error, dev dm-7, sector 1849697344
Oct  7 13:02:24 AF$$^&rod1 kernel: end_request: I/O error, dev dm-7, sector 1849697440
Oct  7 13:02:24 AF$$^&rod1 kernel: end_request: I/O error, dev dm-7, sector 1849697456
Oct  7 13:02:24 AF$$^&rod1 kernel: EXT4-fs error (device dm-8): __ext4_get_inode_loc: unable to read inode block - inode=57820282, block=231212135
Oct  7 13:02:24 AF$$^&rod1 kernel: end_request: I/O error, dev dm-7, sector 2345037096
Oct  7 13:02:24 AF$$^&rod1 kernel: end_request: I/O error, dev dm-7, sector 2111523576
Oct  7 13:02:24 AF$$^&rod1 kernel: end_request: I/O error, dev dm-7, sector 2332778144
Oct  7 13:02:24 AF$$^&rod1 kernel: end_request: I/O error, dev dm-7, sector 2511344960
Oct  7 13:02:24 AF$$^&rod1 kernel: end_request: I/O error, dev dm-7, sector 1849695496
Oct  7 13:02:24 AF$$^&rod1 kernel: EXT4-fs error (device dm-8): __ext4_get_inode_loc: unable to read inode block - inode=57816881, block=231211923
Oct  7 13:02:24 AF$$^&rod1 kernel: end_request: I/O error, dev dm-7, sector 1849695496
Oct  7 13:02:24 AF$$^&rod1 kernel: EXT4-fs error (device dm-8): __ext4_get_inode_loc: unable to read inode block - inode=57816881, block=231211923
Oct  7 13:02:24 AF$$^&rod1 kernel: end_request: I/O error, dev dm-7, sector 1849695496
Oct  7 13:02:24 AF$$^&rod1 kernel: EXT4-fs error (device dm-8): __ext4_get_inode_loc: unable to read inode block - inode=57816881, block=231211923
Oct  7 13:02:24 AF$$^&rod1 kernel: end_request: I/O error, dev dm-7, sector 1849695496
Oct  7 13:02:24 AF$$^&rod1 kernel: EXT4-fs error (device dm-8): __ext4_get_inode_loc: unable to read inode block - inode=57816881, block=231211923
Oct  7 13:02:29 AF$$^&rod1 kernel: end_request: I/O error, dev dm-7, sector 2308784176
Oct  7 13:02:29 AF$$^&rod1 kernel: end_request: I/O error, dev dm-7, sector 2308784176
Oct  7 13:02:29 AF$$^&rod1 kernel: end_request: I/O error, dev dm-7, sector 2308784176
Oct 7 13:36:19 AF$$^&rod1 mcelog: failed to prefill DIMM database from DMI data

This mostly being the I/O error there was no away the OS was getting away with the iSCSI LUN.
The only way we got rid of this error was by rebooting the machine.
This was like the last resort for us.
Thank you..