Status: New
Owner: ----
New issue 879 by [email protected]: gnt-cluster upgrade backs up
all of /var/lib/ganeti/export
http://code.google.com/p/ganeti/issues/detail?id=879
Upgrading from ganeti 2.10.5 to 2.11.2 (wheezy-backports):
root@nuc1:~# gnt-cluster upgrade --to 2.11
Draining queue
Stopping daemons on master node.
Stopping daemons everywhere.
Backing up configuration as /var/lib/ganeti1404977844.tar
<< sits here for a while >>
Switching to version 2.11 on all nodes
... etc
Upgrade completed successfully. However:
root@nuc1:~# ls -lh /var/lib/ganeti1404977844.tar
-rw-r--r-- 1 root root 2.1G Jul 10 08:37 /var/lib/ganeti1404977844.tar
root@nuc1:~# tar -tvf /var/lib/ganeti1404977844.tar | grep export
drwx------ root/root 0 2014-07-02 16:13
var/lib/ganeti/export/
drwx------ root/root 0 2014-07-02 16:13
var/lib/ganeti/export/host87.example.com/
-rw------- root/root 1747 2014-07-02 16:13
var/lib/ganeti/export/host87.example.com/config.ini
-rw------- root/root 2147483648 2014-07-02 16:13
var/lib/ganeti/export/host87.example.com/25d92f7a-581c-4cf6-abac-dec180c163d6.disk0.snap
Fortunately I had only one VM export and it was only 2GB. But the results
could have been catastrophic, doubling space used in /var.
Possibilities:
1. Add "--exclude export" flag to the tar command (but that assumes all
systems have gnu tar)
2. Use python tarfile library to back it up, and filter out the export
directory
3. Fundamentally, having export as a subdir of the ganeti config directory
seems unwise . But moving the config to /var/lib/ganeti/conf is likely too
disruptive. Could move the export directory to (say) /var/spool/ganeti ?
--
You received this message because this project is configured to send all
issue notifications to this address.
You may adjust your notification preferences at:
https://code.google.com/hosting/settings
