Right, you need write permissions for this user/group r-x is read/execute only.
mn > On May 8, 2015, at 10:26 AM, Pratik Gadiya <[email protected]> > wrote: > > @Matt: > [root@vmkdev0022 ~]# hadoop fs -ls -d / > drwxr-xr-x - hdfs hdfs 0 2015-05-08 10:44 / > > @Olivier: > [admin@vmkdev0022 root]$ hadoop fs -mkdir /tptp > mkdir: Permission denied: user=admin, access=WRITE, > inode="/":hdfs:hdfs:drwxr-xr-x > > [admin@vmkdev0022 root]$ groups admin > admin : admin hdfs > > [admin@vmkdev0022 root]$ id admin > uid=500(admin) gid=500(admin) groups=500(admin),498(hdfs) > > > Please suggest what should be the change for the permissions on / or if there > is any other way to resolve this. > > Thanks, > Pratik > From: Matt Narrell [mailto:[email protected]] > Sent: Friday, May 08, 2015 9:37 PM > To: [email protected] > Subject: Re: Access on HDFS > > It looks like the group permissions on / is set to prohibit writes. > > mn > > On May 8, 2015, at 9:59 AM, Olivier Renault <[email protected] > <mailto:[email protected]>> wrote: > > I meant did you check that user admin is part of the hdfs group on the > namenode. > > Olivier > > > From: Pratik Gadiya > Reply-To: "[email protected] <mailto:[email protected]>" > Date: Friday, 8 May 2015 16:57 > To: "[email protected] <mailto:[email protected]>" > Subject: RE: Access on HDFS > > Confirmed, that I have checked it on Namenode. > In addition to that, I have checked on all of the nodes in observed that > superusergroup is set as “hdfs” in hdfs-site.xml for all nodes. > > Thanks, > Pratik Gadiya > > From: Olivier Renault [mailto:[email protected] > <mailto:[email protected]>] > Sent: Friday, May 08, 2015 8:59 PM > To: [email protected] <mailto:[email protected]> > Subject: Re: Access on HDFS > > Could you confirm that you are doing it on the namenode ? ( I tend to do it > on all nodes ) > > Thanks, > Olivier > > > From: Pratik Gadiya > Reply-To: "[email protected] <mailto:[email protected]>" > Date: Friday, 8 May 2015 16:14 > To: "[email protected] <mailto:[email protected]>" > Subject: RE: Access on HDFS > > Checked it’s hdfs > > <property> > <name>dfs.permissions.superusergroup</name> > <value>hdfs</value> > </property> > > Thanks, > Pratik > > From: Olivier Renault [mailto:[email protected] > <mailto:[email protected]>] > Sent: Friday, May 08, 2015 8:39 PM > To: [email protected] <mailto:[email protected]> > Subject: Re: Access on HDFS > > You need to double check which group is setup in hdfs-site.xml. The parameter > is: dfs.permissions.superusergroup > > Thanks > Olivier > > From: Pratik Gadiya > Reply-To: "[email protected] <mailto:[email protected]>" > Date: Friday, 8 May 2015 15:46 > To: "[email protected] <mailto:[email protected]>" > Subject: Access on HDFS > > Hi All, > > I want to add a user who can create/remove and perform all the operations on > hdfs. > > Here is what I tried: > > 1. Create user: adduser admin > 2. /usr/sbin/usermod -a -G hdfs admin > > And when I try to create a directory on hdfs under “/” it raises error as > follows, > [root@vmkdev0021 ~]# id admin > uid=500(admin) gid=500(admin) groups=500(admin),498(hdfs) > > [root@vmkdev0021 ~]# su admin > [admin@vmkdev0021 root]$ hadoop fs -mkdir /input > mkdir: Permission denied: user=admin, access=WRITE, > inode="/":hdfs:hdfs:drwxr-xr-x > > Please let me know how can I overcome this, this is reallly bugging me. > > With Regards, > Pratik Gadiya > > DISCLAIMER ========== This e-mail may contain privileged and confidential > information which is the property of Persistent Systems Ltd. It is intended > only for the use of the individual or entity to which it is addressed. If you > are not the intended recipient, you are not authorized to read, retain, copy, > print, distribute or use this message. If you have received this > communication in error, please notify the sender and delete all copies of > this message. Persistent Systems Ltd. does not accept any liability for virus > infected mails. > DISCLAIMER ========== This e-mail may contain privileged and confidential > information which is the property of Persistent Systems Ltd. It is intended > only for the use of the individual or entity to which it is addressed. If you > are not the intended recipient, you are not authorized to read, retain, copy, > print, distribute or use this message. If you have received this > communication in error, please notify the sender and delete all copies of > this message. Persistent Systems Ltd. does not accept any liability for virus > infected mails. > DISCLAIMER ========== This e-mail may contain privileged and confidential > information which is the property of Persistent Systems Ltd. It is intended > only for the use of the individual or entity to which it is addressed. If you > are not the intended recipient, you are not authorized to read, retain, copy, > print, distribute or use this message. If you have received this > communication in error, please notify the sender and delete all copies of > this message. Persistent Systems Ltd. does not accept any liability for virus > infected mails. > > DISCLAIMER ========== This e-mail may contain privileged and confidential > information which is the property of Persistent Systems Ltd. It is intended > only for the use of the individual or entity to which it is addressed. If you > are not the intended recipient, you are not authorized to read, retain, copy, > print, distribute or use this message. If you have received this > communication in error, please notify the sender and delete all copies of > this message. Persistent Systems Ltd. does not accept any liability for virus > infected mails. >
