[
https://issues.apache.org/jira/browse/HADOOP-865?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12463128
]
Tom White commented on HADOOP-865:
----------------------------------
Do you know if the files (inodes or blocks) got corrupted, or if a block didn't
get written? If you still have the files on S3 then it would be really helpful
if you could send an S3 directory listing using a regular S3 tool (e.g.
http://www.hanzoarchives.com/development-projects/s3-tools/).
Thanks.
BTW nice use of S3FileSystem as an infinite disk!
Tom
> Files written to S3 but never closed can't be deleted
> -----------------------------------------------------
>
> Key: HADOOP-865
> URL: https://issues.apache.org/jira/browse/HADOOP-865
> Project: Hadoop
> Issue Type: Bug
> Components: fs
> Reporter: Bryan Pendleton
>
> I've been playing with the S3 integration. My first attempts to use it are
> actually as a drop-in replacement for a backup job, streaming data offsite by
> piping the backup job output to a "hadoop dfs -put - targetfile".
> If enough errors occur posting to S3 (this happened easily last Thursday,
> during an S3 growth issue), the write can eventually fail. At that point,
> there are both blocks and a partial INode written into S3. Doing a "hadoop
> dfs -ls filename" shows the file, it has a non-zero size, etc. However,
> trying to "hadoop dfs -rm filename" a failed-written file results in the
> response "rm: No such file or directory."
--
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
