This is resolved, now. We were having some problems yesterday with the Puppet infrastructure we use to manage our cluster that resulted in daemons being installed on hosts they shouldn't be on (datanode/tasktracker running on master nodes, for example) that I wasn't aware of when I made my original post. Once we figured that out, this sticky bit problem went away.

I wish I could be more specific just so anyone that finds this thread in the archives could have something useful...

Thanks for your time!

On Wed, Nov 7, 2012 at 2:44 PM, Kartashov, Andy <> wrote:

Have you tried hadoop fs -chmod a+rwx /tmp



From: Arun C Murthy []
Sent: Wednesday, November 07, 2012 3:11 PM
Subject: Re: Sticky Bit Problem (CDH4.1)


Pls ask Cloudera lists...


On Nov 7, 2012, at 9:57 AM, Brian Derickson wrote:

Hey all,

When setting up the namenode, some of the commands that we run are:
hadoop fs -mkdir /tmp
hadoop fs -chmod -R 1777 /tmp

This has worked for previous CDH releases of Hadoop.

We recently upgraded our test cluster to CDH 4.1 and the chmod no longer works.

sudo -u hdfs hadoop fs -chmod -R 1777 /tmp
chmod: chmod : mode '1777' does not match the expected pattern.

sudo -u hdfs hadoop fs -chmod -R +t /tmp
chmod: chmod : mode '+t' does not match the expected pattern.

This disagrees with the docs here:

Has anyone else encountered this? Let me know if you need more information, and thanks for your time.



Arun C. Murthy

Hortonworks Inc.


NOTICE: This e-mail message and any attachments are confidential, subject to copyright and may be privileged. Any unauthorized use, copying or disclosure is prohibited. If you are not the intended recipient, please delete and contact the sender immediately. Please consider the environment before printing this e-mail. AVIS : le présent courriel et toute pièce jointe qui l'accompagne sont confidentiels, protégés par le droit d'auteur et peuvent être couverts par le secret professionnel. Toute utilisation, copie ou divulgation non autorisée est interdite. Si vous n'êtes pas le destinataire prévu de ce courriel, supprimez-le et contactez immédiatement l'expéditeur. Veuillez penser à l'environnement avant d'imprimer le présent courriel