Server Fault is a question and answer site for system and network administrators. It's 100% free, no registration required.

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

What I did and what it did:

> getfacl  x.txt 
# file: x.txt
# owner: cwhii
# group: cwhii

> groups
cwhii adm dialout cdrom plugdev lpadmin admin sambashare
> setfacl --modify=g:adm:rw x.txt
setfacl: x.txt: Operation not supported
> uname -a
Linux road 2.6.31-19-generic #56-Ubuntu SMP Thu Jan 28 01:26:53 UTC 2010 i686 GNU/Linux

What I expected was an additional access control entry on x.txt without an error message.

share|improve this question
i checked tune2fs and it said that the defaults include xattrs and acl but I got the same response. Is it possible that I still need to add acl? – dacresni Oct 14 '15 at 16:42
up vote 13 down vote accepted

This sounds like the default mount behavior is not allowing ACLs on the filesystem. getfacl will report the normal filesystem permissions without error, but setfacl is unable to operate because the filesystem is mounted without the ACL option.

You can add this in /etc/fstab or by modifying your filesystem options.

Assuming you have the /home filesystem on /dev/sda, you can do the following:

Modify Filesystem method:

sudo /sbin/tune2fs -o +acl /dev/sda

Modify /etc/fstab method:

/dev/sda /home ext3 defaults,acl 1 2

Using either method, the filesystem has to be remounted to take effect. You can accomplish this by rebooting, or by running

sudo /bin/mount -o remount /home

share|improve this answer
ACLs are disabled by default due to performance reasons. – grawity Feb 7 '10 at 16:18

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.