You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
What steps will reproduce the problem?
1. hdfs-mount ~/data
2. sudo chmod +w ~/data
What is the expected output? What do you see instead?
I want the permissions to change, but instead I receive a permission denied
error.
What version of the product are you using? On what operating system?
I installed hdfs-fuse-0.2.linux-0.2.linux2.6-gcc4.1-x86.tar.gz onto Centos
Please provide any additional information below.
I am trying to samba share /home/hduser/data which is the mount point for
hdfs-fuse
When the system boots (before I mount the hdfs share) the samba share is active
and I can copy files over to the directory and I see them appear in from linux.
The /home/hduser/data directory has permission drwxrwxrwx and is owned by
hduser:hduser
After I execute the command
hdfs-mount /home/hduser/data
the permissions change to drwxr-xr-x and the directory is owned by root:root.
I am no longer able to write files to the samba share as I get a permission
denied error. Nor am I able to list the contents of the directory.
I can, however, write a file from linux directly to /home/hduser/data and see
it appear in HDFS by executing the command
hadoop fs -ls /
so hdfs-fuse is successfully mounting the directory, but I can't share it for
some reason.
I think the hdfs mounted directory needs write permissions. If I execute the
command
chmod +w /home/hduser/data
the permissions are unchanged. If I execute the command
sudo chmod +w /home/hduser/data
I receive the error "cannot access 'data/': Permission denied.
I've tried to change the permissions from the name node by executing
hadoop fs -chmod +w /
but no changes are reflected at the mount point.
Do you have any thoughts/suggestions?
Original issue reported on code.google.com by [email protected] on 20 Jun 2014 at 2:45
The text was updated successfully, but these errors were encountered:
Original issue reported on code.google.com by
[email protected]
on 20 Jun 2014 at 2:45The text was updated successfully, but these errors were encountered: