proxmox 1.4beta2: glitches

M

marco

New Member
Oct 11, 2009
5
0
1
Hi,

I've been using proxmox 1.3 ( updated from 1.2) since last april, and I'm very happy with it.

Last week I decided to install (from scratch) proxmox1.4beta2.
First I backup all virtual machines/openvz I have on external USB disk, installed proxmox 1.4beta2 and recovered the virtual machine/openvz.

Here are some remarks/bug I found installing/using 1.4beta 2

1. BUG?: In one virtual machine is running the firewall (endian), with this release of proxmox the virtual machine will no more stopped when I shutdown the proxmox server from the web GUI. On the console the shutdown process is wating the virtual machine to stop, but I could login on the webinterface of the firewall, and see the machine is working. In proxmox 1.3 and 1.2 the firewall was successfully shutdown from proxmox. Any idea why?

2. REMARK: parallel-ATA come first instead S-ATA device
(the system has been installed on the same 500GB S-ATA Disks, but now is /dev/sdb)

3. REMARK/BUG? Backup, I get some error during nightly backup of the virtual machine/openvz. I do backup on ext3 partition /data/backup (Parallel-ATA disk /dev/sda1)

cronjob
Code: 
proxmox:~# more /etc/cron.d/vzdump
# Atomatically generated file - do not edit

PATH="/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin"

00 02 * * *           root vzdump --quiet --snapshot --compress --storage backup --mailto proxmox@********** 1000      1100
Output found in syslog:

Code: 
Oct 11 02:00:05 proxmox vzdump[9365]: INFO: starting new backup job: vzdump --quiet --snapshot --compress --storage backup --mailto proxmox@boscac
ci.ch 1000 1100
Oct 11 02:00:05 proxmox vzdump[9365]: INFO: Starting Backup of VM 1000 (qemu)
Oct 11 02:00:08 proxmox kernel: kjournald starting.  Commit interval 5 seconds
Oct 11 02:00:08 proxmox kernel: EXT3 FS on dm-3, internal journal
Oct 11 02:00:08 proxmox kernel: ext3_orphan_cleanup: deleting unreferenced inode 4294537
Oct 11 02:00:08 proxmox kernel: ext3_orphan_cleanup: deleting unreferenced inode 4294374
Oct 11 02:00:08 proxmox kernel: ext3_orphan_cleanup: deleting unreferenced inode 4294972
Oct 11 02:00:08 proxmox kernel: EXT3-fs: dm-3: 3 orphan inodes deleted
Oct 11 02:00:08 proxmox kernel: EXT3-fs: recovery complete.
Oct 11 02:04:27 proxmox vzdump[9365]: INFO: Finished Backup of VM 1000 (00:04:22)
Oct 11 02:04:27 proxmox vzdump[9365]: INFO: Starting Backup of VM 1100 (openvz)
Oct 11 02:04:28 proxmox kernel: kjournald starting.  Commit interval 5 seconds
Oct 11 02:04:28 proxmox kernel: EXT3 FS on dm-3, internal journal
Oct 11 02:04:28 proxmox kernel: ext3_orphan_cleanup: deleting unreferenced inode 4294537
Oct 11 02:04:28 proxmox kernel: ext3_orphan_cleanup: deleting unreferenced inode 4294374
Oct 11 02:04:28 proxmox kernel: ext3_orphan_cleanup: deleting unreferenced inode 4294972
Oct 11 02:04:28 proxmox kernel: EXT3-fs: dm-3: 3 orphan inodes deleted
Oct 11 02:04:28 proxmox kernel: EXT3-fs: recovery complete.
Oct 11 02:04:28 proxmox kernel: EXT3-fs: mounted filesystem with ordered data mode.
Oct 11 02:13:10 proxmox kernel: device-mapper: snapshots: Invalidating snapshot: Unable to allocate exception.
Oct 11 02:13:12 proxmox kernel: EXT3-fs error (device dm-3): ext3_get_inode_loc: unable to read inode block - inode=27345160, block=109379602
Oct 11 02:13:12 proxmox kernel: Buffer I/O error on device dm-3, logical block 0
Oct 11 02:13:12 proxmox kernel: lost page write due to I/O error on dm-3
Oct 11 02:13:12 proxmox kernel: EXT3-fs error (device dm-3) in ext3_reserve_inode_write: IO failure
Oct 11 02:13:12 proxmox kernel: Buffer I/O error on device dm-3, logical block 0
Oct 11 02:13:12 proxmox kernel: lost page write due to I/O error on dm-3
Oct 11 02:13:12 proxmox kernel: EXT3-fs error (device dm-3): ext3_get_inode_loc: unable to read inode block - inode=27345162, block=109379602
Oct 11 02:13:12 proxmox kernel: Buffer I/O error on device dm-3, logical block 0
Oct 11 02:13:12 proxmox kernel: lost page write due to I/O error on dm-3
[..]
Oct 11 02:13:12 proxmox kernel: EXT3-fs error (device dm-3): ext3_get_inode_loc: unable to read inode block - inode=27345165, block=109379602
Oct 11 02:13:12 proxmox kernel: EXT3-fs error (device dm-3) in ext3_reserve_inode_write: IO failure
Oct 11 02:13:12 proxmox kernel: EXT3-fs error (device dm-3): ext3_get_inode_loc: unable to read inode block - inode=27345168, block=109379602
Oct 11 02:13:12 proxmox kernel: EXT3-fs error (device dm-3) in ext3_reserve_inode_write: IO failure
Oct 11 02:13:12 proxmox kernel: EXT3-fs error (device dm-3): ext3_get_inode_loc: unable to read inode block - inode=27345166, block=109379602
Oct 11 02:13:12 proxmox kernel: EXT3-fs error (device dm-3) in ext3_reserve_inode_write: IO failure
Oct 11 02:13:12 proxmox kernel: EXT3-fs error (device dm-3): ext3_get_inode_loc: unable to read inode block - inode=27345156, block=109379602
Oct 11 02:13:12 proxmox kernel: EXT3-fs error (device dm-3) in ext3_reserve_inode_write: IO failure
Oct 11 02:13:12 proxmox kernel: EXT3-fs error (device dm-3): ext3_get_inode_loc: unable to read inode block - inode=27345161, block=109379602
Oct 11 02:13:12 proxmox kernel: EXT3-fs error (device dm-3) in ext3_reserve_inode_write: IO failure
Oct 11 02:13:12 proxmox kernel: EXT3-fs error (device dm-3): ext3_get_inode_loc: unable to read inode block - inode=27345167, block=109379602
Oct 11 02:13:12 proxmox kernel: EXT3-fs error (device dm-3) in ext3_reserve_inode_write: IO failure
[..]
Oct 11 02:18:06 proxmox kernel: EXT3-fs error (device dm-3): ext3_get_inode_loc: unable to read inode block - inode=1697665, block=6783098
Oct 11 02:18:06 proxmox kernel: EXT3-fs error (device dm-3): ext3_get_inode_loc: unable to read inode block - inode=1697665, block=6783098
Oct 11 02:18:06 proxmox kernel: EXT3-fs error (device dm-3): ext3_get_inode_loc: unable to read inode block - inode=1697665, block=6783098
Oct 11 02:18:06 proxmox kernel: EXT3-fs error (device dm-3): ext3_get_inode_loc: unable to read inode block - inode=1697665, block=6783098
Oct 11 02:18:06 proxmox kernel: EXT3-fs error (device dm-3): ext3_get_inode_loc: unable to read inode block - inode=1697665, block=6783098
Oct 11 02:18:06 proxmox kernel: EXT3-fs error (device dm-3): ext3_get_inode_loc: unable to read inode block - inode=1697665, block=6783098
Oct 11 02:18:06 proxmox kernel: EXT3-fs error (device dm-3): ext3_get_inode_loc: unable to read inode block - inode=1697665, block=6783098
Oct 11 02:18:06 proxmox kernel: EXT3-fs error (device dm-3): ext3_get_inode_loc: unable to read inode block - inode=1697665, block=6783098
Oct 11 02:18:06 proxmox kernel: EXT3-fs error (device dm-3): ext3_get_inode_loc: unable to read inode block - inode=1697665, block=6783098
Oct 11 02:18:06 proxmox kernel: EXT3-fs error (device dm-3): ext3_get_inode_loc: unable to read inode block - inode=1697665, block=6783098
Oct 11 02:18:06 proxmox kernel: EXT3-fs error (device dm-3): ext3_get_inode_loc: unable to read inode block - inode=1697665, block=6783098
Which is the device dm-3 ? According to fdisk I don't have any dm-3 device:

Code: 
proxmox:~# fdisk -l

Disk /dev/sda: 300.0 GB, 300069052416 bytes
255 heads, 63 sectors/track, 36481 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Disk identifier: 0x1cdb6fa9

   Device Boot      Start         End      Blocks   Id  System
/dev/sda1               1       30401   244196001   83  Linux
/dev/sda2           30402       36481    48837600   83  Linux

Disk /dev/sdb: 500.1 GB, 500107862016 bytes
255 heads, 63 sectors/track, 60801 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Disk identifier: 0x00000000

   Device Boot      Start         End      Blocks   Id  System
/dev/sdb1   *           1          66      524288   83  Linux
Partition 1 does not end on cylinder boundary.
/dev/sdb2              66       60801   487859712   8e  Linux LVM

Disk /dev/sdc: 500.1 GB, 500107862016 bytes
255 heads, 63 sectors/track, 60801 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Disk identifier: 0x94147d1b

   Device Boot      Start         End      Blocks   Id  System
/dev/sdc1               1       60801   488384001   83  Linux

Disk /dev/dm-0: 4294 MB, 4294967296 bytes
255 heads, 63 sectors/track, 522 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Disk identifier: 0x00000000

Disk /dev/dm-0 doesn't contain a valid partition table

Disk /dev/dm-1: 21.4 GB, 21474836480 bytes
255 heads, 63 sectors/track, 2610 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Disk identifier: 0x00000000

Disk /dev/dm-1 doesn't contain a valid partition table

Disk /dev/dm-2: 469.5 GB, 469506195456 bytes
255 heads, 63 sectors/track, 57080 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Disk identifier: 0x00000000

Disk /dev/dm-2 doesn't contain a valid partition table
 
Last edited:
marco said:
1. BUG?: In one virtual machine is running the firewall (endian), with this release of proxmox the virtual machine will no more stopped when I shutdown the proxmox server from the web GUI. On the console the shutdown process is wating the virtual machine to stop, but I could login on the webinterface of the firewall, and see the machine is working. In proxmox 1.3 and 1.2 the firewall was successfully shutdown from proxmox. Any idea why?
Click to expand...

Do you have a working ACPI power management inside the VM (acpid)?

marco said:
2. REMARK: parallel-ATA come first instead S-ATA device
(the system has been installed on the same 500GB S-ATA Disks, but now is /dev/sdb)
Click to expand...

There is no guarrantee about device ordering.

marco said:
3. REMARK/BUG? Backup, I get some error during nightly backup of the virtual machine/openvz. I do backup on ext3 partition /data/backup (Parallel-ATA disk /dev/sda1)
Click to expand...

Seems there is no free space in the volume group. Whats the output of

# vgs
 
OK, here the output of my system

1 BUG?: endian firewall not shutting down[..]

Do you have a working ACPI power management inside the VM (acpid)?
Click to expand...
the daemon acpid is not installed, but

Code: 
root@endian-fw:~ # ps aux|grep acpi
root        43  0.0  0.0      0     0 ?        S<   Oct11   0:00 [kacpid]
root        44  0.0  0.0      0     0 ?        S<   Oct11   0:00 [kacpi_notify]
Disable ACPI: in the option of this virtual machine (in the GUI config of proxmox) is NOT checked.

2 OK.

3. REMARK/BUG: ext3 dm-3 error during backup [..]

Seems there is no free space in the volume group. Whats the output of

# vgs
Click to expand...
here output from the system
Code: 
proxmox:~# vgs
  VG   #PV #LV #SN Attr   VSize   VFree
  pve    1   3   0 wz--n- 465.26G 4.00G
proxmox:~# lvs
  LV   VG   Attr   LSize   Origin Snap%  Move Log Copy%  Convert
  data pve  -wi-ao 437.26G
  root pve  -wi-ao  20.00G
  swap pve  -wi-ao   4.00G
proxmox:~# pvs
  PV         VG   Fmt  Attr PSize   PFree
  /dev/sdb2  pve  lvm2 a-   465.26G 4.00G

proxmox:~# df -k /var/lib/vz
Filesystem           1K-blocks      Used Available Use% Mounted on
/dev/mapper/pve-data 451306112 131672700 319633412  30% /var/lib/vz
thanks for helping

Marco
 
Try to increase the snapshot size (default is 1GB). Edit/Create /etc/vzdump.conf and add

Code: 
size: 2048
This sets snapshot size to 2GB.

see "man vzdump"
 
Last edited by a moderator:
You must log in or register to reply here.

About

The Proxmox community has been around for many years and offers help and support for Proxmox VE, Proxmox Backup Server, and Proxmox Mail Gateway.
We think our community is one of the best thanks to people like you!

Quick Navigation

Home Get Subscription Wiki Downloads Proxmox Customer Portal About

Get your subscription!

The Proxmox team works very hard to make sure you are running the best software and getting stable updates and security enhancements, as well as quick enterprise support. Tens of thousands of happy customers have a Proxmox subscription. Get yours easily in our online shop.

Buy now!
Community platform by XenForo® © 2010-2024 XenForo Ltd.
Top Bottom