Risk of resizing partitions on production server?
I've got one centos server that we've migrated about 100 sites to, and now we've realized that the /usr partition was not sized correctly; it's too small even to handle cpanel updates. How dangerous will it be to attempt to resize? I'm thinking of reducing /home by a few gigs and adding that to /usr.
I don't want to risk any data loss.
[QUOTE]Filesystem Size Used Avail Use% Mounted on
/dev/sda5 7.8G 911M 6.5G 13% /
/dev/sda8 103G 44G 54G 46% /home
/dev/sdb1 135G 92G 37G 72% /backup
/dev/sda6 996M 46M 899M 5% /tmp
/dev/sda3 7.8G 5.9G 1.5G 81% /usr
/dev/sda2 9.7G 7.8G 1.5G 85% /var
/dev/sda1 122M 18M 98M 16% /boot
-
Hello :) It's likely a better idea to migrate/backup the accounts to a remote server, and then reinstall the OS with the recommended partition scheme. Resizing the partitions on the fly is not supported, and should be handled by a qualified system administrator if you decide to take that route. Thank you. 0 -
You shouldn't do this on a production server, nor is there really any reason nowadays to over-partition a system like that. Use bind mounts if you need to relocate anything, but otherwise I second @cPanelMichael's suggestion of migrating to another system. 0 -
[quote="cPanelMichael, post: 1628082">Hello :) It's likely a better idea to migrate/backup the accounts to a remote server
Not strictly ontopic, but migrating with email accounts is always an mega act. Since SSL/TLS the hostname as emailserver changes. Without virtual servers or separate emailserver/cluster it isn't practical any longer. No user wants to change / understands why emailserver names has to change. I don't see a way to migrate accounts without heavily interacting with customers and their settings.0
Please sign in to leave a comment.
Comments
3 comments