hadoop-common-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Sameer Paranjpye (JIRA)" <j...@apache.org>
Subject [jira] Updated: (HADOOP-122) Failed to execute fsck with -move option
Date Mon, 01 May 2006 20:20:47 GMT
     [ http://issues.apache.org/jira/browse/HADOOP-122?page=all ]

Sameer Paranjpye updated HADOOP-122:

      Version: 0.1.0
    Assign To: Hairong Kuang

Does the fsck utility need to write to the dfs data directory? Perhaps it could point someplace
else by default. Is this behavior actually unreasonable? Perhaps fsck should be hard to run
if you don't have the right set of permissions.

> Failed to execute fsck with -move option
> ----------------------------------------
>          Key: HADOOP-122
>          URL: http://issues.apache.org/jira/browse/HADOOP-122
>      Project: Hadoop
>         Type: Bug

>   Components: dfs
>     Versions: 0.1.0
>     Reporter: Hairong Kuang
>     Assignee: Hairong Kuang

> I received the following error when running fsck with -move option. The dfs was started
by a user while the fsck was ran by a different user that does not have the write access to
the hadoop dfs data directory.
> - moving to /lost+found: /data.txt
> java.io.FileNotFoundException: hadoop-dfs-data-dir/tmp/client-8234960199756230677 (Permission
> at java.io.FileOutputStream.open(Native Method)
> at java.io.FileOutputStream.<init>(FileOutputStream.java:179)
> at java.io.FileOutputStream.<init>(FileOutputStream.java:131)
> at org.apache.hadoop.dfs.DFSClient$DFSOutputStream.<init>(DFSClient.java:546)
> at org.apache.hadoop.dfs.DFSClient.create(DFSClient.java:99)
> at org.apache.hadoop.dfs.DFSck.lostFoundMove(DFSck.java:222)
> at org.apache.hadoop.dfs.DFSck.check(DFSck.java:178)
> at org.apache.hadoop.dfs.DFSck.check(DFSck.java:124)
> at org.apache.hadoop.dfs.DFSck.fsck(DFSck.java:112)
> at org.apache.hadoop.dfs.DFSck.main(DFSck.java:433)
> Failed to move /data.txt to /lost+found: hadoop-dfs-data-dir/tmp/client-8234960199756230677
(Permission denied)

This message is automatically generated by JIRA.
If you think it was sent incorrectly contact one of the administrators:
For more information on JIRA, see:

View raw message