Prepare a stock centos HN to do vzdumps using LVM snapshots

Situation:

- Stock Centos 4 system with OpenVZ kernel + utilities installed. One big /vz partition, using LVM.

Trying to make a backup using:

vzdump --dumpdir /var/ --snapshot 101
Error message received:
Insufficient free extents (1) in volume group
VolGroup00: 16 required
What does that mean?

It means that you don't have enough free space in the VG (Volume Group) to create an LVM snapshot.

What is the solution? Reduce the size of one partition, then resize one LV (logical volume). This is easily done if you don't have only one big / partition. I usually always make a separate partition for /var and for /vz.

To determine what logical volume needs to be resized, you can use the df -h command. Mine showed:

/dev/mapper/VolGroup00-LogVol05
119G 16G 99G 14% /vz

To resize it:

  1. Make backups of your VM to be sure
  2. Stop the vz service (service vz stop)
  3. umount /vz
  4. e2fsck -f /dev/VolGroup00/LogVol05
  5. Use resize2fs /dev/VolGroup00/LogVol05 110G
  6. Use lvresize to reduce the LV sizey by 2 GB:lvresize --size -2G /dev/VolGroup00/LogVol05
Optionnaly, you can resize your FS to match the size of the LV, using no size arguments to ext2resize:
  1. e2fsck -f /dev/VolGroup00/LogVol05
  2. resize2fs /dev/VolGroup00/LogVol05
I have not re-tested this procedure itself from the beginning (I don't have a test system here), but it should be pretty safe. Please leave comments if you try this.

If you need to know how big are your LV : lvdisplay.
If you need to know how big are our VG: vgdisplay. This also tells the free space in the VG.

You can not try to use lvm snapshots with vzdump.

Comments

Post a Comment

Popular posts from this blog

General linux performance troubleshooting

Here's a list of commands that you should execute and then share the output to someone who can help you figure out what resource is the bottleneck in your system. Note, it requires the  sysstat  and  procps  packages (ubuntu and RHEL and its derivatives): uptime vmstat 1 10 iostat -xN 2 10 mpstat -P ALL 3 10 pidstat 1 10 free -mw (or free -m, if your OS doesn't support -w)  uptime is to see the load averages on the system. vmstat is mostly used to tell if the system is swapping or not. If you see significant numbers in the 'si' and 'so' columns, your system is most likely swapping (using the hard drive as RAM), which usually slows performance a lot. iostat is mostly used to determine if your disk subsystem is not able to cope with the load. If you see one or more lines that shows 100 or close almost constantly, it is probably the case.  If it is your swap volume, you probably saw numbers in the 'si' and 'so' columns in the  vmsta
Read more

Asterisk works under OpenVZ (no zaptel)

Hi, Just to let you know that I did a basic test with asterisk on an OpenVZ VE and it works. We only tested SIP connectivity (it would probably be complex to have Zaptel support and I don't really need it). We were able to connect to a VoIP provider using SIP ( unlimitel ) and music on hold works. The only thing I had to change to make it work is to comment out this line in /usr/sbin/safe_asterisk: #TTY=9 # TTY (if you want one) for Asterisk to run on (I guess there is no TTY9 (console # 9) on openVZ since it is a virtual machine and TTY9 is usually a physical console (monitor)). I'll soon put my asterisk server in a VE, I'll let you know how it goes. I also use Unlimitel and ATAs to link my PSTN line and cordless phones.
Read more