[
https://issues.apache.org/jira/browse/HADOOP-3452?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Lohit Vijayarenu updated HADOOP-3452:
-------------------------------------
Attachment: HADOOP-3452-3.patch
Thanks for reviewing this Dhruba. The reason I scan for "is CORRUPT" is
because, fsck now also reports CORRUPT blocks. And also, if a filename contains
CORRUPT, we do not want to report filesystem to be corrupt. As I mentioned,
this is a temporary fix. I have updated the patch comments as you suggested.
> fsck exit code would be better if non-zero when FS corrupt
> ----------------------------------------------------------
>
> Key: HADOOP-3452
> URL: https://issues.apache.org/jira/browse/HADOOP-3452
> Project: Hadoop Core
> Issue Type: Improvement
> Components: dfs
> Reporter: Pete Wyckoff
> Priority: Minor
> Fix For: 0.18.0
>
> Attachments: HADOOP-3452-1.patch, HADOOP-3452-2.patch,
> HADOOP-3452-3.patch
>
>
> fsck exit code would be better if behaved like other sys admin tools and exit
> code indicated healthy/corrupt or other errors.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
