[
https://issues.apache.org/jira/browse/HADOOP-2540?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
dhruba borthakur updated HADOOP-2540:
-
Resolution: Fixed
Status: Resolved (was: Patch Available)
I just committed this
[
https://issues.apache.org/jira/browse/HADOOP-2540?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
dhruba borthakur updated HADOOP-2540:
-
Attachment: recoverLastBlock2.patch
I incorporated all of Konstantin's comments except t
[
https://issues.apache.org/jira/browse/HADOOP-2540?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
dhruba borthakur updated HADOOP-2540:
-
Status: Patch Available (was: Open)
> Empty blocks make fsck report corrupt, even when
[
https://issues.apache.org/jira/browse/HADOOP-2540?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Nigel Daley updated HADOOP-2540:
Priority: Blocker (was: Major)
Dhruba, is this patch ready? Can we get it reviewed, Hudson'd and
[
https://issues.apache.org/jira/browse/HADOOP-2540?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Koji Noguchi updated HADOOP-2540:
-
Fix Version/s: 0.15.3
I'm guessing this also means, if client fails while writing, it has to del
[
https://issues.apache.org/jira/browse/HADOOP-2540?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
dhruba borthakur updated HADOOP-2540:
-
Attachment: recoverLastBlock.patch
The namenode was not cleaning up the last block on le
