On Analytics1028:
[Sun Mar 5 12:12:39 2017] EXT4-fs warning (device sdj1): ext4_end_bio:317: I/O error -5 writing to inode 205259304 (offset 3952640 size 61440 starting block 650475380) [Sun Mar 5 12:12:39 2017] Buffer I/O error on device sdj1, logical block 650475108 [Sun Mar 5 12:12:39 2017] Buffer I/O error on device sdj1, logical block 650475109 [Sun Mar 5 12:12:39 2017] Buffer I/O error on device sdj1, logical block 650475110 [Sun Mar 5 12:12:39 2017] Buffer I/O error on device sdj1, logical block 650475111 [Sun Mar 5 12:12:39 2017] Buffer I/O error on device sdj1, logical block 650475112 [Sun Mar 5 12:12:39 2017] Buffer I/O error on device sdj1, logical block 650475113 [Sun Mar 5 12:12:39 2017] Buffer I/O error on device sdj1, logical block 650475114 [Sun Mar 5 12:12:39 2017] Buffer I/O error on device sdj1, logical block 650475115 [Sun Mar 5 12:12:39 2017] Buffer I/O error on device sdj1, logical block 650475116 [Sun Mar 5 12:12:39 2017] Buffer I/O error on device sdj1, logical block 650475117
This host is a bit delicate since it is a journal node (only three on the entire Hadoop cluster) so before doing maintenance on it we'd need to coordinate to triple check that the other two hosts are up and running (to avoid things like Hadoop HDFS Master shutdown).