You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ozone.apache.org by "Nanda kumar (Jira)" <ji...@apache.org> on 2020/05/11 18:31:00 UTC
[jira] [Updated] (HDDS-3492) cp command not working on Ozone
mounted using hdfs-fuse.
[ https://issues.apache.org/jira/browse/HDDS-3492?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Nanda kumar updated HDDS-3492:
------------------------------
Summary: cp command not working on Ozone mounted using hdfs-fuse. (was: With hdfs-fuse file implementation 'cp' command is not working)
> cp command not working on Ozone mounted using hdfs-fuse.
> --------------------------------------------------------
>
> Key: HDDS-3492
> URL: https://issues.apache.org/jira/browse/HDDS-3492
> Project: Hadoop Distributed Data Store
> Issue Type: Bug
> Reporter: Aryan Gupta
> Assignee: Aryan Gupta
> Priority: Major
> Labels: pull-request-available
>
> 'cp' (copy) command doesn’t work with hdfs-fuse file system. It works by passing 'cp' command two times for the same file. It mainly happens when destination file doesn’t exists. It happens because when 'cp' command is performed for the first time it creates the file at the destination path, but as per ozone file system protocols any file has no access till its committed. So, 'getattr' function is not able to locate the file(though it’s present at the destination path). Hence, 'cp' command fails in the first go. Second time when 'cp' command is executed, file is already present in the destination path so 'cp' command simply override the data in the file.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: ozone-issues-unsubscribe@hadoop.apache.org
For additional commands, e-mail: ozone-issues-help@hadoop.apache.org