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?
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?