• Our team is looking to connect with folks who use email services provided by Plesk, or a premium service. If you'd like to be part of the discovery process and share your experiences, we invite you to complete this short screening survey. If your responses match the persona we are looking for, you'll receive a link to schedule a call at your convenience. We look forward to hearing from you!
  • We are looking for U.S.-based freelancer or agency working with SEO or WordPress for a quick 30-min interviews to gather feedback on XOVI, a successful German SEO tool we’re looking to launch in the U.S.
    If you qualify and participate, you’ll receive a $30 Amazon gift card as a thank-you. Please apply here. Thanks for helping shape a better SEO product for agencies!
  • The BIND DNS server has already been deprecated and removed from Plesk for Windows.
    If a Plesk for Windows server is still using BIND, the upgrade to Plesk Obsidian 18.0.70 will be unavailable until the administrator switches the DNS server to Microsoft DNS. We strongly recommend transitioning to Microsoft DNS within the next 6 weeks, before the Plesk 18.0.70 release.
  • The Horde component is removed from Plesk Installer. We recommend switching to another webmail software supported in Plesk.

Question Inefficient PLESK Partition Setup on CloudLinux - Root vs Home

Miro

New Pleskian
Server operating system version
CloudLinux 8.10
Plesk version and microupdate number
18.0.68
Hello everyone,

I’m having an issue with the disk space distribution on a server running Plesk + CloudLinux. The current setup looks like this:

/dev/mapper/cloudlinux-root:
Total space: 69.97 GB
Used: 62.50 GB (89.32%)
Available: only 7.47 GB

/dev/mapper/cloudlinux-home:
Total space: 506.50 GB
Used: only 3.56 GB (0.70%)
Available: 502.94 GB

As you can see, the root partition is nearly full, while the home partition remains mostly unused. The VM hosts around 25 domains and 20 hosting accounts.

My questions:

1. Is this a standard configuration when installing Plesk + CloudLinux? Or could something have been misconfigured during the setup?

2. Has anyone faced a similar issue, and how did you resolve it? I’m especially interested in safe methods of redistributing space.

3. What are your recommendations for the optimal partitioning between root and home for a hosting server?

4. Is resizing partitions using LVM safe in a production environment with Plesk? What precautions should be taken?

5. Are there any known issues or pitfalls I should watch out for when modifying partitions in a Plesk + CloudLinux environment?

VM specifications:

Plesk Obsidian
CloudLinux 8.10 (Shared Pro)
RAM: 44 GB
Total disk space: ~700 GB

The cloudlinux-root space is already filling up, and I’m worried about what will happen when it runs out…:confused:


cloudlinux-root-17-03.png


Thank you in advance for any help and advice!
 
Plesk by default does not use /home and also does not set up partitions, that is on OS side when you install it.

You can for example change the location for the sites data, mail, etc. manually:

Above articles are as an example.

Also, check:
 
3. What are your recommendations for the optimal partitioning between root and home for a hosting server?
Usually you don't need /home at all.
What is there in /home anyway? All subscription users should have their $HOME under /var/www/vhosts.
4. Is resizing partitions using LVM safe in a production environment with Plesk? What precautions should be taken?
Growing partitions is safe.
I would copy the content of /home to e.g. /home2, then kill the mountpoint and the entry in /etc/fstab, rename /home2 to /home, remove the LV, grow the root LV, and resizefs.
 
Back
Top