Disk marked for backup wont back up of size is not set.

Submitted by Franco Nogarin on Fri, 02/08/2013 - 09:44 Pro Licensee

I have a VM with logical volume based disk, which for some reason does not indicate its size, even though when i created the VM using the "create empty instance" I indicated 20GB for the "Disk space allocated to instance". it is marked for backup but in the backup log it indicates it is excluded, when I tried to toggle the backup on and off it reports:

Failed to save disk : Missing or invalid disk size

Now in the past I have learned that setting this value can scramble the drive, so I need to know an approach to setting this correctly, as I dont have a backup and need it to back up with all the others.

The volume on the host is set at 20 GB. I think this might be a bug in the "Create Empty System" process, so while we try to sort out my VM, I will do some tests and see if I cant replicate the missing size problem.

Franco

Status: 
Active

Comments

Submitted by Franco Nogarin on Fri, 02/08/2013 - 09:51 Pro Licensee

Bummer, I could not reproduce this, even though it has happend before :( F

Submitted by JamieCameron on Fri, 02/08/2013 - 15:15

Ok .. but it sounds like the issue was that Cloudmin could not work on the size of the VMs disks.

If you do see this again, SSH into your Cloudmin master system as root and run :

cloudmin list-disks --host your-vm-name --multiline

and include that output in the bug report.

Submitted by Franco Nogarin on Fri, 02/08/2013 - 17:11 Pro Licensee

Hi Jamie,
I may have misspoke, I cannot cause another VM to to have this issue, but my VM is still in this condition.
here is the output requested:

/dev/lv_storage/spiceworks_localhost_img
Description: LVM VG lv_storage, LV spiceworks_localhost_img
Device on system: /dev/hda
Description on system: IDE device A
Format: disk
Type: Device
Storage name: Regular files
Storage ID: files
Media: disk
Partition 1: range 2048-206847 size 100 MB blocks 102400 type 7
Partition 2: range 206848-41940991 size 19.90 GB blocks 20867072 type 7
Include in backups: Yes
/home/sparcsadmin/virtio-win-0.1-52.iso
Device on system: /dev/hdd
Description on system: IDE device D
Format: disk
Type: File
Storage name: Regular files
Storage ID: files
Media: cdrom
Size: 58497024
Nice size: 55.79 MB
Include in backups: No

Submitted by JamieCameron on Fri, 02/08/2013 - 17:15

The size being missing from that output is a problem..

If you run the command lvdisplay /dev/lv_storage/spiceworks_localhost_img on the system hosting that VM, what does it output?

Submitted by Franco Nogarin on Sat, 02/09/2013 - 14:16 Pro Licensee

Ok, the VM is running but here is the output, it has some creepy errors, too.

Found duplicate PV KhlOQa35a6k5zhEmZTVeTaiaiJoeaiyC: using /dev/dm-16 not /dev/dm-11
Found duplicate PV KhlOQa35a6k5zhEmZTVeTaiaiJoeaiyC: using /dev/dm-19 not /dev/dm-16
Found duplicate PV KhlOQa35a6k5zhEmZTVeTaiaiJoeaiyC: using /dev/dm-21 not /dev/dm-19
Found duplicate PV KhlOQa35a6k5zhEmZTVeTaiaiJoeaiyC: using /dev/dm-22 not /dev/dm-21
Found duplicate PV KhlOQa35a6k5zhEmZTVeTaiaiJoeaiyC: using /dev/dm-23 not /dev/dm-22
--- Logical volume ---
LV Name /dev/lv_storage/spiceworks_localhost_img
VG Name lv_storage
LV UUID vkGSGT-ZloZ-HjMq-ABEe-uFAC-rXR0-FrlgGy
LV Write Access read/write
LV Status available
# open 3
LV Size 20.00 GiB
Current LE 5120
Segments 2
Allocation inherit
Read ahead sectors auto
- currently set to 256
Block device 251:4

Submitted by JamieCameron on Sat, 02/09/2013 - 14:37

That actually looks OK..

If you go into Webmin on the host system, and go to Hardware -> Logical Volume Management, is the size of that LV shown correctly?

Submitted by Franco Nogarin on Sun, 02/10/2013 - 11:17 Pro Licensee

When I click on "logical Volumes" Tab, I see a drive icon that says:

spiceworks_localhost_img
20 GB

and when I click the icon for details it says: 20 GB as well.

Submitted by JamieCameron on Sun, 02/10/2013 - 11:38

That all looks OK as well. If you run list-disks again, is the size of disks still missing?

Submitted by Franco Nogarin on Mon, 02/11/2013 - 14:36 Pro Licensee

Yes it is still missing.

/dev/lv_storage/spiceworks_localhost_img
Description: LVM VG lv_storage, LV spiceworks_localhost_img
Device on system: /dev/hda
Description on system: IDE device A
Format: disk
Type: Device
Storage name: Regular files
Storage ID: files
Media: disk
Partition 1: range 2048-206847 size 100 MB blocks 102400 type 7
Partition 2: range 206848-41940991 size 19.90 GB blocks 20867072 type 7
Include in backups: Yes
/home/sparcsadmin/virtio-win-0.1-52.iso
Device on system: /dev/hdd
Description on system: IDE device D
Format: disk
Type: File
Storage name: Regular files
Storage ID: files
Media: cdrom
Size: 58497024
Nice size: 55.79 MB
Include in backups: No

Submitted by JamieCameron on Mon, 02/11/2013 - 17:13

It looks like the Cloudmin master is having trouble connecting to Webmin on the host system for this VM.

Is the host a separate machine from the Cloudmin master?

Submitted by Franco Nogarin on Mon, 02/18/2013 - 13:13 Pro Licensee

yes cloudmin master is SMVMHOST and the host for the SPICEWORKS.LOCAL VM is SMVMHOST64. What else can I test for you? F

Submitted by JamieCameron on Mon, 02/18/2013 - 19:28

Does only this specific VM have this problem, or do all your VMs have it? Or just VMs on that host?

Submitted by Franco Nogarin on Tue, 02/19/2013 - 17:58 Pro Licensee

I have had this issue before on different servers, but right now it is only this VM. As I mentioned in comment #1, I cannot reproduce the problem but am left with a VM I cannot backup because of this size issue.
F

Submitted by JamieCameron on Tue, 02/19/2013 - 20:54

Would it be possible for me to login to your system to see what is going on here? I'd need root SSH access to the Cloudmin master.

If that is possible, please email me at jcameron@virtualmin.com

Submitted by JamieCameron on Tue, 02/19/2013 - 20:54

Would it be possible for me to login to your system to see what is going on here? I'd need root SSH access to the Cloudmin master.

If that is possible, please email me at jcameron@virtualmin.com

Submitted by Franco Nogarin on Wed, 02/20/2013 - 10:53 Pro Licensee

you have the logins sent on feb 1 and feb 2 and i am migrating my VMS right now so its not a good day. F

Submitted by andreychek on Wed, 02/20/2013 - 11:00

Unfortunately, we don't typically store login info after a given problem has been resolved, so Jamie isn't likely to have your login info available.

We understand that you're doing a migration now, and it's no problem to wait until you're ready.

Whenever it's convenient for us to log into your system, could you re-send your login into to jcameron@virtualmin.com?

Thanks!

Submitted by JamieCameron on Wed, 02/20/2013 - 12:48

Ok, I am logging in to take a look now..

Submitted by Franco Nogarin on Wed, 02/20/2013 - 12:55 Pro Licensee

thanks @andreychek Ok, Its done, I manually DDed the lv to a new server and then told cloumin to move the VM, it said cannot move the volume because it is not an image. but it moved the vm anyway and now its running fine on the new server. since I created the volume myself meticulously, I doubt the problem is the volume rather i think its in the config file or script that initiates the VM.

Creds sent to Jamie. F

Submitted by JamieCameron on Wed, 02/20/2013 - 12:58

Ok, I found and fixed the problem - somehow this particular VM was missing the entries in its data file indicating that its root disk was on LVM. The solution was to edit the file /etc/webmin/servers/1360107183151130.serv and add the lines :

kvm_filesystem_vg=lv_storage
kvm_filesystem_lv=spiceworks_localhost_img

I'm unsure how this could have happened though. Was this VM perhaps dis-associated from Cloudmin and re-added at some point?

Submitted by Franco Nogarin on Wed, 02/20/2013 - 14:30 Pro Licensee

NICE! Thank you Jamie! I cant say enough good things about using cloudmin. it has changed my job dramatically and I now spend time doing cool things instead of finding ways to do them.

As to your question, Disconnected? Hmm, dont think so. But Now that I think of it, the building of this particular VM was troublesome. I first created an install image from a window7 install DVD and then used the create from image, and had problems with virtio drivers so I fudged about until I got it to see the disk and then went forward all guns blazing.

Franco