Created 11-13-2017 06:30 PM
we see the system log on one of the worker machine ( dmesg )
and from the log we saw that:
(sdc): warning: mounting fs with errors, running e2fsck is recommended
disk - sdc include the HDFS folder - hdfs files
df | grep sdc /dev/sdc 1922721048 1560852 1921143812 1% /grop/sdc ls /grop/sdc/hadoop/ hdfs yarn
so is it safe to run the following ( as OS logs recommended ) , <in spite disk include HDFS files , is it risky?>
e2fsck -y /dev/sdc
Created 11-22-2017 05:26 PM
f you don't run the filesystem checker, the apparent corruption in the filesystem may get worse. Unchecked, this can lead to data corruption or at the unlikely worst destruction of the filesystem.
During the filesystem check, file structures within the filesystem will be checked, and if necessary repaired. The repair takes no account of content; it's all about making sure the filesystem is self-consistent.
If you run e2fsck -y /dev/sdc
you have no opportunity to validate the corrections being applied.
On the other hand if you run e2fsck -n /dev/sdc
you can see what would happen without it actually being applied, and if you run e2fsck /dev/sdc
you will be asked each time a significant correction needs to be applied.
In summary
-y
you have no option to review the potentially destructive changes, and you may lose your data-n
you will not fix any errors, and over time may lose your data, but you will get to review the set of changes that would be madeRecommendation
e2fsck -n /dev/sdc
to review the errorse2fsck /dev/sdc
(or possibly e2fsck -y /dev/sdc
) or whether you would prefer to obtain direct professional assistanceCreated 11-22-2017 05:26 PM
f you don't run the filesystem checker, the apparent corruption in the filesystem may get worse. Unchecked, this can lead to data corruption or at the unlikely worst destruction of the filesystem.
During the filesystem check, file structures within the filesystem will be checked, and if necessary repaired. The repair takes no account of content; it's all about making sure the filesystem is self-consistent.
If you run e2fsck -y /dev/sdc
you have no opportunity to validate the corrections being applied.
On the other hand if you run e2fsck -n /dev/sdc
you can see what would happen without it actually being applied, and if you run e2fsck /dev/sdc
you will be asked each time a significant correction needs to be applied.
In summary
-y
you have no option to review the potentially destructive changes, and you may lose your data-n
you will not fix any errors, and over time may lose your data, but you will get to review the set of changes that would be madeRecommendation
e2fsck -n /dev/sdc
to review the errorse2fsck /dev/sdc
(or possibly e2fsck -y /dev/sdc
) or whether you would prefer to obtain direct professional assistance