fixeverything: touch aquota.user

fedlerner

Active Member
Oct 31, 2007
33
0
56
Argentina
I'm getting the following error after running fixeverything (I assume I'll get it too after running fixquotas).

Code:
touch: cannot touch `/usr/aquota.user': Permission denied
touch: cannot touch `/usr/aquota.user': Permission denied
touch: cannot touch `/var/aquota.user': Permission denied
touch: cannot touch `/var/aquota.user': Permission denied
touch: cannot touch `/aquota.user': Permission denied
touch: cannot touch `/aquota.user': Permission denied
touch: cannot touch `/home/aquota.user': Permission denied
touch: cannot touch `/home/aquota.user': Permission denied

What can I do to fix this?
 

LiNUxG0d

Well-Known Member
Jun 25, 2003
206
1
168
Gatineau, Quebec, Canada
Hi there,

It's possible that the files are attributed "+i".

You may need to "chattr -i /path/to/file" though, honestly, I don't know why it would be the case. Though, I've seen weirder things happen!

Also, check the `dmesg` command; is your file-system in read-only for the /usr partition?

Give it a go if you want, with one file to start, to see if it disappears from the list of "Permission Denied" candidates! :)

Regards,
 

LiNUxG0d

Well-Known Member
Jun 25, 2003
206
1
168
Gatineau, Quebec, Canada
Hi there,

Let's try this. Can you log into your server - as root via SSH - and issue the following command:

Code:
[[email protected] ~]# lsattr /usr/aquota.user
It will return something like:

Code:
[[email protected] ~]# lsattr /usr/aquota.user
------------- /usr/aquota.user
If instead of "-------------" in the output, you see, say, "----i--------" then your file is set with the "immutable bit" on! Basically, immutable is geek for "can't touch this, edit it, save it or overwrite it". I have rarely seen this set on the quota files, but it may happen; I've seen stranger things. ;)

Using the chattr command (which stands for change attribute) I showed you before will turn the immutable bit off. Basically +i is on, -i is off.

I hope this helps more? Sorry for being uber-nerd up top there. ;) My bad, man. :)

Regards,
 

LiNUxG0d

Well-Known Member
Jun 25, 2003
206
1
168
Gatineau, Quebec, Canada
Hmmmm,

Interesting. Can you issue and ls on them and show me the result?

Code:
[[email protected] ~]# ls -la /usr/aquota.user
-rwxr--r-- 1 root root 27648 Apr  4 01:04 /usr/aquota.user*
Are the perms ok? I mean, if they are root:root but, say, permissions 444 (r--r--r--) then this might (I say this lightly) be the cause.

If no special attributes are on, and permissions are find and you're root, I'll be totally baffled!

Short of being on your server checking your files and logs, I'm short on options.

Let me know,
 

cPanelKenneth

cPanel Development
Staff member
Apr 7, 2006
4,607
79
458
cPanel Access Level
Root Administrator
This is standard for the Linux quota files. In order to 'touch' one of the quota files, one must turn off quotas. It is the quota kernel subsystem that is blocking the access.