hadoop-common-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "lohit vijayarenu (JIRA)" <j...@apache.org>
Subject [jira] Updated: (HADOOP-3452) fsck exit code would be better if non-zero when FS corrupt
Date Wed, 28 May 2008 07:01:47 GMT

     [ https://issues.apache.org/jira/browse/HADOOP-3452?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

lohit vijayarenu updated HADOOP-3452:
-------------------------------------

    Fix Version/s: 0.18.0
     Release Note: fsck now reports exit status depending on the status of filesystem, (HEALTHY/CORRUPT)
     Hadoop Flags: [Incompatible change]
           Status: Patch Available  (was: Open)

> 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
>
>
> 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.


Mime
View raw message