You are viewing a plain text version of this content. The canonical link for it is here.
Posted to common-dev@hadoop.apache.org by "Nigel Daley (JIRA)" <ji...@apache.org> on 2007/01/04 19:40:27 UTC
[jira] Created: (HADOOP-856) fsck reports a non-existant DFS path
as healthy
fsck reports a non-existant DFS path as healthy
-----------------------------------------------
Key: HADOOP-856
URL: https://issues.apache.org/jira/browse/HADOOP-856
Project: Hadoop
Issue Type: Bug
Components: dfs
Affects Versions: 0.9.2
Reporter: Nigel Daley
Priority: Minor
I would have expected the following to generate an error message:
-bash-3.00$ bin/hadoop fsck non-existant
Status: HEALTHY
Total size: 0 B
Total blocks: 0
Total dirs: 0
Total files: 0
Over-replicated blocks: 0
Under-replicated blocks: 0
Target replication factor: 3
Real replication factor: 0.0
The filesystem under path 'non-existant' is HEALTHY
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Updated: (HADOOP-856) fsck reports a non-existant DFS path
as healthy
Posted by "Milind Bhandarkar (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HADOOP-856?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Milind Bhandarkar updated HADOOP-856:
-------------------------------------
Attachment: fsck-fix.patch
Attached a patch that fixes this issue. Also added a test to test this fix.
> fsck reports a non-existant DFS path as healthy
> -----------------------------------------------
>
> Key: HADOOP-856
> URL: https://issues.apache.org/jira/browse/HADOOP-856
> Project: Hadoop
> Issue Type: Bug
> Components: dfs
> Affects Versions: 0.9.2
> Reporter: Nigel Daley
> Assigned To: Milind Bhandarkar
> Priority: Minor
> Fix For: 0.11.0
>
> Attachments: fsck-fix.patch
>
>
> I would have expected the following to generate an error message:
> -bash-3.00$ bin/hadoop fsck non-existant
> Status: HEALTHY
> Total size: 0 B
> Total blocks: 0
> Total dirs: 0
> Total files: 0
> Over-replicated blocks: 0
> Under-replicated blocks: 0
> Target replication factor: 3
> Real replication factor: 0.0
> The filesystem under path 'non-existant' is HEALTHY
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (HADOOP-856) fsck reports a non-existant DFS path
as healthy
Posted by "Hadoop QA (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HADOOP-856?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12467689 ]
Hadoop QA commented on HADOOP-856:
----------------------------------
+1, because http://issues.apache.org/jira/secure/attachment/12349636/fsck-fix.patch applied and successfully tested against trunk revision r500023.
> fsck reports a non-existant DFS path as healthy
> -----------------------------------------------
>
> Key: HADOOP-856
> URL: https://issues.apache.org/jira/browse/HADOOP-856
> Project: Hadoop
> Issue Type: Bug
> Components: dfs
> Affects Versions: 0.9.2
> Reporter: Nigel Daley
> Assigned To: Milind Bhandarkar
> Priority: Minor
> Fix For: 0.11.0
>
> Attachments: fsck-fix.patch
>
>
> I would have expected the following to generate an error message:
> -bash-3.00$ bin/hadoop fsck non-existant
> Status: HEALTHY
> Total size: 0 B
> Total blocks: 0
> Total dirs: 0
> Total files: 0
> Over-replicated blocks: 0
> Under-replicated blocks: 0
> Target replication factor: 3
> Real replication factor: 0.0
> The filesystem under path 'non-existant' is HEALTHY
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Work started: (HADOOP-856) fsck reports a non-existant DFS
path as healthy
Posted by "Milind Bhandarkar (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HADOOP-856?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Work on HADOOP-856 started by Milind Bhandarkar.
> fsck reports a non-existant DFS path as healthy
> -----------------------------------------------
>
> Key: HADOOP-856
> URL: https://issues.apache.org/jira/browse/HADOOP-856
> Project: Hadoop
> Issue Type: Bug
> Components: dfs
> Affects Versions: 0.9.2
> Reporter: Nigel Daley
> Assigned To: Milind Bhandarkar
> Priority: Minor
> Fix For: 0.11.0
>
> Attachments: fsck-fix.patch
>
>
> I would have expected the following to generate an error message:
> -bash-3.00$ bin/hadoop fsck non-existant
> Status: HEALTHY
> Total size: 0 B
> Total blocks: 0
> Total dirs: 0
> Total files: 0
> Over-replicated blocks: 0
> Under-replicated blocks: 0
> Target replication factor: 3
> Real replication factor: 0.0
> The filesystem under path 'non-existant' is HEALTHY
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (HADOOP-856) fsck reports a non-existant DFS path
as healthy
Posted by "Milind Bhandarkar (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HADOOP-856?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Milind Bhandarkar updated HADOOP-856:
-------------------------------------
Fix Version/s: 0.11.0
Status: Patch Available (was: In Progress)
> fsck reports a non-existant DFS path as healthy
> -----------------------------------------------
>
> Key: HADOOP-856
> URL: https://issues.apache.org/jira/browse/HADOOP-856
> Project: Hadoop
> Issue Type: Bug
> Components: dfs
> Affects Versions: 0.9.2
> Reporter: Nigel Daley
> Assigned To: Milind Bhandarkar
> Priority: Minor
> Fix For: 0.11.0
>
> Attachments: fsck-fix.patch
>
>
> I would have expected the following to generate an error message:
> -bash-3.00$ bin/hadoop fsck non-existant
> Status: HEALTHY
> Total size: 0 B
> Total blocks: 0
> Total dirs: 0
> Total files: 0
> Over-replicated blocks: 0
> Under-replicated blocks: 0
> Target replication factor: 3
> Real replication factor: 0.0
> The filesystem under path 'non-existant' is HEALTHY
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Assigned: (HADOOP-856) fsck reports a non-existant DFS path
as healthy
Posted by "Milind Bhandarkar (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HADOOP-856?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Milind Bhandarkar reassigned HADOOP-856:
----------------------------------------
Assignee: Milind Bhandarkar
> fsck reports a non-existant DFS path as healthy
> -----------------------------------------------
>
> Key: HADOOP-856
> URL: https://issues.apache.org/jira/browse/HADOOP-856
> Project: Hadoop
> Issue Type: Bug
> Components: dfs
> Affects Versions: 0.9.2
> Reporter: Nigel Daley
> Assigned To: Milind Bhandarkar
> Priority: Minor
> Fix For: 0.11.0
>
> Attachments: fsck-fix.patch
>
>
> I would have expected the following to generate an error message:
> -bash-3.00$ bin/hadoop fsck non-existant
> Status: HEALTHY
> Total size: 0 B
> Total blocks: 0
> Total dirs: 0
> Total files: 0
> Over-replicated blocks: 0
> Under-replicated blocks: 0
> Target replication factor: 3
> Real replication factor: 0.0
> The filesystem under path 'non-existant' is HEALTHY
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (HADOOP-856) fsck reports a non-existant DFS path
as healthy
Posted by "Doug Cutting (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HADOOP-856?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Doug Cutting updated HADOOP-856:
--------------------------------
Resolution: Fixed
Status: Resolved (was: Patch Available)
I just committed this. Thanks, Milind!
> fsck reports a non-existant DFS path as healthy
> -----------------------------------------------
>
> Key: HADOOP-856
> URL: https://issues.apache.org/jira/browse/HADOOP-856
> Project: Hadoop
> Issue Type: Bug
> Components: dfs
> Affects Versions: 0.9.2
> Reporter: Nigel Daley
> Assigned To: Milind Bhandarkar
> Priority: Minor
> Fix For: 0.11.0
>
> Attachments: fsck-fix.patch
>
>
> I would have expected the following to generate an error message:
> -bash-3.00$ bin/hadoop fsck non-existant
> Status: HEALTHY
> Total size: 0 B
> Total blocks: 0
> Total dirs: 0
> Total files: 0
> Over-replicated blocks: 0
> Under-replicated blocks: 0
> Target replication factor: 3
> Real replication factor: 0.0
> The filesystem under path 'non-existant' is HEALTHY
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.