You are viewing a plain text version of this content. The canonical link for it is here.
Posted to common-dev@hadoop.apache.org by "Hairong Kuang (JIRA)" <ji...@apache.org> on 2006/04/06 02:00:44 UTC
[jira] Created: (HADOOP-122) Failed to execute fsck with -move
option
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
Reporter: 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 denied)
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:
http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
[jira] Commented: (HADOOP-122) Failed to execute fsck with -move
option
Posted by "Doug Cutting (JIRA)" <ji...@apache.org>.
[ http://issues.apache.org/jira/browse/HADOOP-122?page=comments#action_12377279 ]
Doug Cutting commented on HADOOP-122:
-------------------------------------
To some degree this is a configuration issue. A dfs data node stores data under the value of dfs.data.dir. The dfs client code also writes temporary files in the directory dfs.data.dir. Probably these should instead be different properties. But there's also no reason that a client needs to have the same value for this property as a datanode. So, in short, this can be fixed by changing the value of dfs.data.dir in the client's configuration to an alternate location for temporary files.
> 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 denied)
> 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:
http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
[jira] Updated: (HADOOP-122) Failed to execute fsck with -move
option
Posted by "Sameer Paranjpye (JIRA)" <ji...@apache.org>.
[ 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 denied)
> 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:
http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira