• Debian 11 is approaching its end-of-life (vendor EOL date - August 31, 2026). Plesk Obsidian 18.0.80 will be the last release to support it.
    If you are running Plesk Obsidian on Debian 11, we recommend you upgrade those servers to Debian 12 using our dist-upgrade tool.
  • We plan to deprecate and remove the support for XML RPC protocol versions earlier than 1.6.9.1 in Plesk Obsidian 18.0.82. We strongly recommend that you update all existing integrations using earlier versions of the XML RPC protocol to comply with the version 1.6.9.1 specification.

Hard memory limit

B

brianbatson

Guest
In the VDS world, I have been allocated 10GB of hard disk. I am using about 3.3GB. Yesterday, for some reason, the system temporarily identified that I had used the full disk quota. Attempting to clear numerous failing programs, I removed some files (a couple hundred MB) and rebooted.

After reboot, the statistics page still identified I was at full disk quota. The boot process began to fail and xinetd deactivated some services - effectively disabling portions of the system.

Is this the standard way in which PLESK handles disk usage full conditions? This was a glitch, as I did not have 10GB used - but it thought so and then started removing files.

Does every account that used PLESK run the risk of UNIX (Fedora Core 2) suicide when disk quota is reached?

Isn't there a reasonable way to prevent system destruction at this condition?
 
Sounds to me like a VDS issue, but I have not really used VDS systems before. I had a file system fill up once on a standard RHEL3 system and though it cause problems, I didn't see the behavior that you are seeing.

thanks,
mikeS
 
Back
Top