hadoop-common-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Michael Bieniosek (JIRA)" <j...@apache.org>
Subject [jira] Updated: (HADOOP-3529) dfs "Rename failed" doesn't give reason if source doesn't exist
Date Tue, 10 Jun 2008 21:27:45 GMT

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

Michael Bieniosek updated HADOOP-3529:
--------------------------------------

    Component/s: dfs

> dfs "Rename failed" doesn't give reason if source doesn't exist
> ---------------------------------------------------------------
>
>                 Key: HADOOP-3529
>                 URL: https://issues.apache.org/jira/browse/HADOOP-3529
>             Project: Hadoop Core
>          Issue Type: Bug
>          Components: dfs
>    Affects Versions: 0.16.3
>            Reporter: Michael Bieniosek
>
> If I run
> hadoop fs -mv /no/such/file /blah
> I get the error: mv: Rename failed /no/such/file
> But in the namenode log, it says 
> 2008-06-10 21:17:37,883 WARN org.apache.hadoop.dfs.StateChange: DIR* FSDirectory.unprotectedRenameTo:
failed to rename /no/such/file to /blah because source does not exist
> It would be nice if the fs shell also gave the informative error.

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