I am getting "disk quota exceeded" error messages when trying to ftp to a site on my Plesk 6 box.

I have checked the domain in question, and it's currently using 109Mb of its 1Gb quota. No problem with the user's quota (unlimited) or disk space (6% used) either.

Anyone have any idea what's happening?

Thanks,
Dan

no clue.. but i had the same problem.. I just disabled the quota..
still havent figured this one out... also i've noticed theres a definite coding error in PSA.. i dont think it will properly accept a quota amount of 1000 MB or higer.

gulch: when you say you've checked the domain in question, do you mean within Plesk or by using the 'quota' command?

What does 'quota -u username' return (run it in ssh as root, username being the ftp user name of the problematic domain)?

I think I remember one of the Plesk staff suggesting setting quota by hand if there is a problem setting it within Plesk. So, you could set it to the same value by hand, if Plesk fails to do so properly... At least for the time being, untill the fix is out.

All of the setting up and configuration was done through Plesk, but at the end of my tether (I set the quota to unlimited and it still didn't work) I asked Rackshack support to help, and the discovered by running "quota -u" that the user's quota was different from the quota reported in Plesk.

I've no idea how this happened as I hadn't altered anything other than in Plesk, some bug somewhere perhaps, but at least it's all fixed now.

Yes, it's a bug. It's been reported before and, as I understand, Plesk intends to fix it in the next patch.

Yes it seems its a bug, its Happening with a specific Domain that is strange behaviour even if you changed the FTP username.

[root@ns5 httpdocs]# quota -u
Disk quotas for user (uid 10102):
Filesystem blocks quota limit grace files quota limit grace
/dev/hda3 10688* 0 10240 724 0 0

and with -uq

[root@ns5 httpdocs]# quota -uq
Disk quotas for user (uid 10102):
Block limit reached on /dev/hda3

After that many other domains were added they are working fine.

Hopes some one have any idea to resolve this very strange issue.