Few Ceph questions

September 16, 2014, 8:58 am

We are looking at deploying a cloud to host our clients systems. I have been playing with ceph for a few weeks now and starting to get a good grasp and really like the project.

Here is a little background on what we are looking to do. I plan on deploying 2 independent ceph clusters in 2 different locations. We will be using incremental snapshots to keep the 2nd ceph cluster up-to-date, this will be our failover location in case of fire/emergency. We will have either 10GB or 40GB fiber between the two locations. I also plan on building the ceph cluster itself with a basic CentOS load unless others here think proxmox would be better (We are a centos shop for the most part and would like to keep proxmox strictly for virtualization purposes). Then we will be using some proxmox front ends to provide VM's.

I have one questions on the ceph setup itself.

1. Are you guys presenting a pool directly to proxmox
- Or are you creating a block device within the pool and presenting that to proxmox

2. If block device, do you create a individual block device for each VM, or run all VM's on a single block device?

Im still rapping my head around ceph as there is alot to it. I appreciate any input on the subject!

↧

Problems with cluster...

September 16, 2014, 11:21 am

≫ Next: Proxmox VE 3.3 - Installation aborted in a Hyper-V Virtual Machine

≪ Previous: Few Ceph questions

Hello, I've been running PVE for a while now. Yesterday I updated to the latest PVE-no-subscription. It's a three-node cluster, and the first two nodes upgraded fine with no issues. The third node seemed to go fine, but after the reboot the third node initially joins the cluster, but after about five minutes the node goes red on the console, and I can see using 'pvecm' that the node status says "Activity blocked". Also, this node can't write to /etc/pve, either, but that doesn't surprise me.

root@spuproxmox02:~# pvecm nodes
Node Sts Inc Joined Name
1 X 18292 spuproxmox01
2 M 18292 2014-09-16 10:56:38 spuproxmox02
3 X 18292 spuproxmox03

root@spuproxmox02:~# pvecm status
Version: 6.2.0
Config Version: 3
Cluster Name: SPU
Cluster Id: 577
Cluster Member: Yes
Cluster Generation: 18296
Membership state: Cluster-Member
Nodes: 1
Expected votes: 3
Total votes: 1
Node votes: 1
Quorum: 2 Activity blocked
Active subsystems: 5
Flags:
Ports Bound: 0
Node name: spuproxmox02
Node ID: 2
Multicast addresses: 239.192.2.67
Node addresses: 156.74.237.69
root@spuproxmox02:~#

There are active VM's running on this node, and they seem fine, although the console doesn't see them any more. All VM's are on local storage so they can't be easily moved to another host.

Any ideas what the issue is? Any fixes? Thanks.

Brad

↧

Proxmox VE 3.3 - Installation aborted in a Hyper-V Virtual Machine

September 16, 2014, 2:10 pm

≫ Next: Did I really Type My Password Wrong 2 Times During Installation?

≪ Previous: Problems with cluster...

Hello,

i have this configuration.

settings.png

And i got this error.

error-1.png

I'm trying to install the Proxmox VE 3.3 in a Windows 2012 R2 Hyper-V Virtual Machine.

But i dont know why it doesnt work.
If i use Generation 2 machines it doesnt boot.
If i use Generation 1 the installation is aborted.

Thank you in Advance!

Attached Images

settings.png (33.9 KB)
error-1.png (20.1 KB)

↧

Did I really Type My Password Wrong 2 Times During Installation?

September 16, 2014, 2:58 pm

≫ Next: PfSense (or generic BSD 8.x) on PX 3.3, optimizations ?

≪ Previous: Proxmox VE 3.3 - Installation aborted in a Hyper-V Virtual Machine

I just installed proxmox 3.3 on a server, and right after doing so I'm unable to login as root.

Did I really type my password wrong two times during installation?

Is reinstalling the only way to get past this?

↧

PfSense (or generic BSD 8.x) on PX 3.3, optimizations ?

September 17, 2014, 12:32 am

≫ Next: Problem with 3.3 local storage

≪ Previous: Did I really Type My Password Wrong 2 Times During Installation?

Hi !

I use two PFSense firewall on a PX Cluster, all ok, works very well.
Firewal configuration is complex and works on 35 VLAN (4 virtual E1000 as NIC).

The CPU utilization (4 cores on single VM, type QEMU64) is medium/high (maximum full load 70%, typical 20-30%).
Phisical hardware is powerfull and CPU on the IBM server presents a low-medium load.

Can I increase CPU units (now 1000 as default) ? I could have benefits?
Can I change VM settings to optimize it on BSD ?

Very thanks

Luca

↧

Problem with 3.3 local storage

September 17, 2014, 1:00 am

≫ Next: Convert sata to IDE/VIRTIO

≪ Previous: PfSense (or generic BSD 8.x) on PX 3.3, optimizations ?

I just upgraded my 2 nodes to 3.3.... FYI, one of the nodes didn't upgrade correctly and would hang on reboot, so I ended up wiping and reinstalling.

The problem I am having is on the node that was wiped and reinstalled, I can't seem to upload anything to the local storage. I can download openvz templates just fine, but when I try uploading an ISO, I get "Error 500: can't activate storage local on node xyz".

I have tried just about every way to get storage on that node working i.e. I have a second hard disk on the node which I setup and tried adding an LVM and also tried adding a local directory to storage. Every time I try uploading an ISO to that node, I get the same error. It doesn't matter if it's to the default local storage, a newly created LVM or local directory, a shared directory from node 2, or anything else.

Anyone have any suggestions on how to solve this?

Btw, this problem does not occur on node2 which was upgraded to 3.3. I also noticed that node1 (which was wiped and reinstalled) has a partition table in GPT format whereas the node that was upgraded has a partition table in MBR format. I am not sure if that has any bearing on the problem.

Thanks.

↧

Convert sata to IDE/VIRTIO

September 17, 2014, 2:13 am

≫ Next: Proxmox 3.3 vs Hyper-v 2012r2 on EMC vnx over FC block access

≪ Previous: Problem with 3.3 local storage

Hello,

I have a lot of VM's with Linux systems on them. Somebody created SATA like a disk and i have problem with migrate it from one node to other. With IDE/VIRTIO i don't have that problem.

How can i change SATA to IDE for example without reinstall system?

Thank you for help and answer.

Best,
Rafal - Kamyk

↧

Proxmox 3.3 vs Hyper-v 2012r2 on EMC vnx over FC block access

September 17, 2014, 4:18 am

≫ Next: storage migration virtio failed

≪ Previous: Convert sata to IDE/VIRTIO

Hello
We have 4 servers with Proxmox using local hard drives (even in version 2.3 but at the moment it is not important).
To improve the performance of virtual machines purchased a disk array EMC VNX 5200 - block access by card 8Gb FC (lpe12002 with 2 x MiniGBIC FC 8Gb / s). 25 x 600GB 10krpm (4 x disk with RAID5 and 16 x drive with RAID 10). Each server is connected to the array 2 cables (on EMC Failover Mode: Active-Active mode (ALUA) -failovermode 4).
I devoted for testing one server (IBM System x3400) and I am shocked Proxmox 3.3 performance compared to the performance of Hyper-v 2012r2. Of course, in the case of Proxmox configured the multipath (Alua) and hyper-v MPIO.
Below screenshots of the test read / write HDTune program running on a virtual machine with a clean newly installed system Windows2008r2 - without any updates. Tests hyper-v and Proxmox done on the same physical server.
If HyperV 2012r2 on two resources (RAID5 and RAID10) I created NTFS partitions.
In the case of Proxmox 3.3 obtain similar performance with LVM as well as a mounted partition with ext3 and raw disks (writeback cache). Similar perfomance is with cache writeback an cache none. I tried virtio driver and have this same performance like without driver virtio.

We use Proxmox without purchased support because we are a public institution (Public Library), which has no additional funds for an annual subscription fee - array we bought the resources acquired of the Ministry of Culture.

I would like to stay with Proxmox, but if I can not improve the performance of this I will be forced to change virtualizer.
If I have to perform additional tests (indifferently on which hypervisor) or share some logs please let us know.

raid5_hyperv2012r2_vs_proxmox3.3.png raid10_hyperv2012r2_vs_proxmox3.3.png

Attached Images

raid5_hyperv2012r2_vs_proxmox3.3.png (62.5 KB)
raid10_hyperv2012r2_vs_proxmox3.3.png (62.4 KB)

↧

storage migration virtio failed

September 17, 2014, 6:31 am

≫ Next: proxmox 3.2 kernel issues

≪ Previous: Proxmox 3.3 vs Hyper-v 2012r2 on EMC vnx over FC block access

Hi,
I am now in process of migrating some machines from proxmox 3.2 to proxmox 3.3. With one machine I have a following error after reaching 100%:
qmp command 'block-job-complete' failed - The active block job for device 'drive-virtio0' cannot be completed
I have successfully done live migration to second server but I am not able to finish moving image from nfs storage using virtio to another nfs storage.
With another vm I solved it by using command qm rescan --vmid 108 but it was a little different case.
Do you have any hint, how to solve this?
Thanks a lot in advance

↧

proxmox 3.2 kernel issues

September 17, 2014, 6:58 am

≫ Next: Proxmox firewall and 3rd party firewalls

≪ Previous: storage migration virtio failed

Hello,

I get a lot of "errors" in the kern.log I don't understand.
Has someone any idea, because my filesystem is filling up really quickly.

kr,

Rudi

Sep 12 16:06:37 trinity kernel: WARNING: at net/core/dev.c:1917 skb_warn_bad_offload+0xc2/0xf0() (Tainted: G W --------------- )
Sep 12 16:06:37 trinity kernel: Hardware name: PowerEdge M620
Sep 12 16:06:37 trinity kernel: tun: caps=(0x80000049, 0x0) len=2802 data_len=1368 ip_summed=1
Sep 12 16:06:37 trinity kernel: Modules linked in: vzethdev vznetdev pio_nfs pio_direct pfmt_raw pfmt_ploop1 ploop simfs vzrst nf_nat nf_conntrack_ipv4 nf_defrag_ipv4 vzcpt nf_conntrack vzdquota vzmon vzdev ip6t_REJECT ip6table_mangle ip6table_filter ip6_tables xt_length xt_hl xt_tcpmss xt_TCPMSS iptable_mangle iptable_filter xt_multiport xt_limit xt_dscp ipt_REJECT vhost_net tun macvtap ip_tables macvlan kvm_intel kvm dlm configfs vzevent ib_iser rdma_cm ib_addr iw_cm ib_cm ib_sa ib_mad ib_core iscsi_tcp libiscsi_tcp libiscsi scsi_transport_iscsi nfsd nfs nfs_acl auth_rpcgss fscache lockd sunrpc bonding 8021q garp ipv6 fuse snd_pcsp iTCO_wdt snd_pcm iTCO_vendor_support snd_page_alloc snd_timer snd soundcore lpc_ich dcdbas sb_edac edac_core mfd_core shpchp wmi power_meter ext3 mbcache jbd usb_storage sg ses enclosure megaraid_sas ahci bnx2x mdio [last unloaded: scsi_wait_scan]
Sep 12 16:06:37 trinity kernel: Pid: 0, comm: swapper veid: 0 Tainted: G W --------------- 2.6.32-29-pve #1
Sep 12 16:06:37 trinity kernel: Call Trace:
Sep 12 16:06:37 trinity kernel: <IRQ> [<ffffffff81076088>] ? warn_slowpath_common+0x88/0xc0
Sep 12 16:06:37 trinity kernel: [<ffffffff81076176>] ? warn_slowpath_fmt+0x46/0x50
Sep 12 16:06:37 trinity kernel: [<ffffffff81486482>] ? skb_warn_bad_offload+0xc2/0xf0
Sep 12 16:06:38 trinity kernel: [<ffffffff8148bb51>] ? __skb_gso_segment+0x71/0xc0
Sep 12 16:06:39 trinity kernel: [<ffffffff8148bbb3>] ? skb_gso_segment+0x13/0x20
Sep 12 16:06:40 trinity kernel: [<ffffffff8148c704>] ? dev_hard_start_xmit+0x94/0x5a0
Sep 12 16:06:41 trinity kernel: [<ffffffff814a8e7a>] ? sch_direct_xmit+0x15a/0x1d0
Sep 12 16:06:41 trinity kernel: [<ffffffff8148ce38>] ? dev_queue_xmit+0x228/0x320
Sep 12 16:06:41 trinity kernel: [<ffffffff8152afe8>] ? br_dev_queue_push_xmit+0x88/0xc0
Sep 12 16:06:41 trinity kernel: [<ffffffff8152b078>] ? br_forward_finish+0x58/0x60
Sep 12 16:06:41 trinity kernel: [<ffffffff8152b12a>] ? __br_forward+0xaa/0xd0
Sep 12 16:06:41 trinity kernel: [<ffffffff8152b1b5>] ? br_forward+0x65/0x70
Sep 12 16:06:41 trinity kernel: [<ffffffff8152c37f>] ? br_handle_frame_finish+0x21f/0x320
Sep 12 16:06:41 trinity kernel: [<ffffffff8152c642>] ? br_handle_frame+0x1c2/0x270
Sep 12 16:06:41 trinity kernel: [<ffffffff8153aa50>] ? vlan_hwaccel_do_receive+0x70/0x130
Sep 12 16:06:41 trinity kernel: [<ffffffff814869ae>] ? __netif_receive_skb+0x45e/0x7a0
Sep 12 16:06:41 trinity kernel: [<ffffffff810566c4>] ? scale_rt_power+0x24/0x80
Sep 12 16:06:41 trinity kernel: [<ffffffff8148a718>] ? netif_receive_skb+0x58/0x60
Sep 12 16:06:41 trinity kernel: [<ffffffff8148a830>] ? napi_skb_finish+0x50/0x70
Sep 12 16:06:41 trinity kernel: [<ffffffff8153b1d4>] ? vlan_gro_receive+0x84/0xa0
Sep 12 16:06:41 trinity kernel: [<ffffffffa00475f5>] ? bnx2x_rx_int+0x1055/0x15d0 [bnx2x]
Sep 12 16:06:41 trinity kernel: [<ffffffff81080231>] ? __local_trigger+0xc1/0xd0
Sep 12 16:06:41 trinity kernel: [<ffffffff81015009>] ? read_tsc+0x9/0x20
Sep 12 16:06:41 trinity kernel: [<ffffffffa0047c1b>] ? bnx2x_poll+0xab/0x2f0 [bnx2x]
Sep 12 16:06:41 trinity kernel: [<ffffffff810b3fe8>] ? tick_dev_program_event+0x68/0xd0
Sep 12 16:06:41 trinity kernel: [<ffffffff8148be3b>] ? net_rx_action+0x10b/0x2f0
Sep 12 16:06:41 trinity kernel: [<ffffffff810a7635>] ? __hrtimer_start_range_ns+0x1a5/0x480
Sep 12 16:06:41 trinity kernel: [<ffffffff8107f443>] ? __do_softirq+0x103/0x260
Sep 12 16:06:41 trinity kernel: [<ffffffff810ade89>] ? do_timer+0x329/0x590
Sep 12 16:06:41 trinity kernel: [<ffffffff8100c44c>] ? call_softirq+0x1c/0x30
Sep 12 16:06:41 trinity kernel: [<ffffffff81010195>] ? do_softirq+0x65/0xa0
Sep 12 16:06:41 trinity kernel: [<ffffffff8107f26d>] ? irq_exit+0xcd/0xd0
Sep 12 16:06:41 trinity kernel: [<ffffffff81565af5>] ? do_IRQ+0x75/0xf0
Sep 12 16:06:41 trinity kernel: [<ffffffff8100ba93>] ? ret_from_intr+0x0/0x11
Sep 12 16:06:41 trinity kernel: <EOI> [<ffffffff812ef95e>] ? intel_idle+0xde/0x170
Sep 12 16:06:41 trinity kernel: [<ffffffff812ef941>] ? intel_idle+0xc1/0x170
Sep 12 16:06:41 trinity kernel: [<ffffffff81450f77>] ? cpuidle_idle_call+0xa7/0x140
Sep 12 16:06:41 trinity kernel: [<ffffffff8100a013>] ? cpu_idle+0xb3/0x110
Sep 12 16:06:41 trinity kernel: [<ffffffff815414c5>] ? rest_init+0x85/0x90
Sep 12 16:06:41 trinity kernel: [<ffffffff81c34f76>] ? start_kernel+0x406/0x412
Sep 12 16:06:41 trinity kernel: [<ffffffff81c3433a>] ? x86_64_start_reservations+0x125/0x129
Sep 12 16:06:41 trinity kernel: [<ffffffff81c34453>] ? x86_64_start_kernel+0x115/0x124
Sep 12 16:06:41 trinity kernel: ---[ end trace afb55001d9fa461b ]---
Sep 12 16:06:41 trinity kernel: Tainting kernel with flag 0x9
Sep 12 16:06:41 trinity kernel: Pid: 0, comm: swapper veid: 0 Tainted: G W --------------- 2.6.32-29-pve #1
Sep 12 16:06:41 trinity kernel: Call Trace:
Sep 12 16:06:41 trinity kernel: <IRQ> [<ffffffff81075f11>] ? add_taint+0x71/0x80
Sep 12 16:06:41 trinity kernel: [<ffffffff81076095>] ? warn_slowpath_common+0x95/0xc0
Sep 12 16:06:41 trinity kernel: [<ffffffff81076176>] ? warn_slowpath_fmt+0x46/0x50
Sep 12 16:06:41 trinity kernel: [<ffffffff81486482>] ? skb_warn_bad_offload+0xc2/0xf0
Sep 12 16:06:41 trinity kernel: [<ffffffff8148bb51>] ? __skb_gso_segment+0x71/0xc0
Sep 12 16:06:41 trinity kernel: [<ffffffff8148bbb3>] ? skb_gso_segment+0x13/0x20
Sep 12 16:06:41 trinity kernel: [<ffffffff8148c704>] ? dev_hard_start_xmit+0x94/0x5a0
Sep 12 16:06:41 trinity kernel: [<ffffffff814a8e7a>] ? sch_direct_xmit+0x15a/0x1d0
Sep 12 16:06:41 trinity kernel: [<ffffffff8148ce38>] ? dev_queue_xmit+0x228/0x320
Sep 12 16:06:41 trinity kernel: [<ffffffff8152afe8>] ? br_dev_queue_push_xmit+0x88/0xc0
Sep 12 16:06:41 trinity kernel: [<ffffffff8152b078>] ? br_forward_finish+0x58/0x60
Sep 12 16:06:41 trinity kernel: [<ffffffff8152b12a>] ? __br_forward+0xaa/0xd0
Sep 12 16:06:41 trinity kernel: [<ffffffff8152b1b5>] ? br_forward+0x65/0x70
Sep 12 16:06:41 trinity kernel: [<ffffffff8152c37f>] ? br_handle_frame_finish+0x21f/0x320
Sep 12 16:06:41 trinity kernel: [<ffffffff8152c642>] ? br_handle_frame+0x1c2/0x270
Sep 12 16:06:41 trinity kernel: [<ffffffff8153aa50>] ? vlan_hwaccel_do_receive+0x70/0x130
Sep 12 16:06:41 trinity kernel: [<ffffffff814869ae>] ? __netif_receive_skb+0x45e/0x7a0
Sep 12 16:06:41 trinity kernel: [<ffffffff810566c4>] ? scale_rt_power+0x24/0x80
Sep 12 16:06:41 trinity kernel: [<ffffffff8148a718>] ? netif_receive_skb+0x58/0x60
Sep 12 16:06:41 trinity kernel: [<ffffffff8148a830>] ? napi_skb_finish+0x50/0x70
Sep 12 16:06:41 trinity kernel: [<ffffffff8153b1d4>] ? vlan_gro_receive+0x84/0xa0
Sep 12 16:06:41 trinity kernel: [<ffffffffa00475f5>] ? bnx2x_rx_int+0x1055/0x15d0 [bnx2x]
Sep 12 16:06:41 trinity kernel: [<ffffffff81080231>] ? __local_trigger+0xc1/0xd0
Sep 12 16:06:41 trinity kernel: [<ffffffff81015009>] ? read_tsc+0x9/0x20
Sep 12 16:06:41 trinity kernel: [<ffffffffa0047c1b>] ? bnx2x_poll+0xab/0x2f0 [bnx2x]
Sep 12 16:06:41 trinity kernel: [<ffffffff810b3fe8>] ? tick_dev_program_event+0x68/0xd0
Sep 12 16:06:41 trinity kernel: [<ffffffff8148be3b>] ? net_rx_action+0x10b/0x2f0
Sep 12 16:06:41 trinity kernel: [<ffffffff810a7635>] ? __hrtimer_start_range_ns+0x1a5/0x480
Sep 12 16:06:41 trinity kernel: [<ffffffff8107f443>] ? __do_softirq+0x103/0x260
Sep 12 16:06:41 trinity kernel: [<ffffffff810ade89>] ? do_timer+0x329/0x590
Sep 12 16:06:41 trinity kernel: [<ffffffff8100c44c>] ? call_softirq+0x1c/0x30
Sep 12 16:06:41 trinity kernel: [<ffffffff81010195>] ? do_softirq+0x65/0xa0
Sep 12 16:06:41 trinity kernel: [<ffffffff8107f26d>] ? irq_exit+0xcd/0xd0
Sep 12 16:06:41 trinity kernel: [<ffffffff81565af5>] ? do_IRQ+0x75/0xf0
Sep 12 16:06:41 trinity kernel: [<ffffffff8100ba93>] ? ret_from_intr+0x0/0x11
Sep 12 16:06:41 trinity kernel: <EOI> [<ffffffff812ef95e>] ? intel_idle+0xde/0x170
Sep 12 16:06:41 trinity kernel: [<ffffffff812ef941>] ? intel_idle+0xc1/0x170
Sep 12 16:06:41 trinity kernel: [<ffffffff81450f77>] ? cpuidle_idle_call+0xa7/0x140
Sep 12 16:06:41 trinity kernel: [<ffffffff8100a013>] ? cpu_idle+0xb3/0x110
Sep 12 16:06:41 trinity kernel: [<ffffffff815414c5>] ? rest_init+0x85/0x90
Sep 12 16:06:41 trinity kernel: [<ffffffff81c34f76>] ? start_kernel+0x406/0x412
Sep 12 16:06:41 trinity kernel: [<ffffffff81c3433a>] ? x86_64_start_reservations+0x125/0x129
Sep 12 16:06:41 trinity kernel: [<ffffffff81c34453>] ? x86_64_start_kernel+0x115/0x124
Sep 12 16:06:41 trinity kernel: ------------[ cut here ]------------
Sep 12 16:06:41 trinity kernel: WARNING: at net/core/dev.c:1917 skb_warn_bad_offload+0xc2/0xf0() (Tainted: G W --------------- )
Sep 12 16:06:41 trinity kernel: Hardware name: PowerEdge M620
Sep 12 16:06:41 trinity kernel: tun: caps=(0x80000049, 0x0) len=2802 data_len=1368 ip_summed=1
Sep 12 16:06:41 trinity kernel: Modules linked in: vzethdev vznetdev pio_nfs pio_direct pfmt_raw pfmt_ploop1 ploop simfs vzrst nf_nat nf_conntrack_ipv4 nf_defrag_ipv4 vzcpt nf_conntrack vzdquota vzmon vzdev ip6t_REJECT ip6table_mangle ip6table_filter ip6_tables xt_length xt_hl xt_tcpmss xt_TCPMSS iptable_mangle iptable_filter xt_multiport xt_limit xt_dscp ipt_REJECT vhost_net tun macvtap ip_tables macvlan kvm_intel kvm dlm configfs vzevent ib_iser rdma_cm ib_addr iw_cm ib_cm ib_sa ib_mad ib_core iscsi_tcp libiscsi_tcp libiscsi scsi_transport_iscsi nfsd nfs nfs_acl auth_rpcgss fscache lockd sunrpc bonding 8021q garp ipv6 fuse snd_pcsp iTCO_wdt snd_pcm iTCO_vendor_support snd_page_alloc snd_timer snd soundcore lpc_ich dcdbas sb_edac edac_core mfd_core shpchp wmi power_meter ext3 mbcache jbd usb_storage sg ses enclosure megaraid_sas ahci bnx2x mdio [last unloaded: scsi_wait_scan]
Sep 12 16:06:41 trinity kernel: Pid: 0, comm: swapper veid: 0 Tainted: G W --------------- 2.6.32-29-pve #1
Sep 12 16:06:41 trinity kernel: Call Trace:
Sep 12 16:06:41 trinity kernel: <IRQ> [<ffffffff81076088>] ? warn_slowpath_common+0x88/0xc0
Sep 12 16:06:41 trinity kernel: [<ffffffff81076176>] ? warn_slowpath_fmt+0x46/0x50
Sep 12 16:06:41 trinity kernel: [<ffffffff81486482>] ? skb_warn_bad_offload+0xc2/0xf0
Sep 12 16:06:41 trinity kernel: [<ffffffff8148bb51>] ? __skb_gso_segment+0x71/0xc0
Sep 12 16:06:41 trinity kernel: [<ffffffff8148bbb3>] ? skb_gso_segment+0x13/0x20
Sep 12 16:06:41 trinity kernel: [<ffffffff8148c704>] ? dev_hard_start_xmit+0x94/0x5a0
Sep 12 16:06:41 trinity kernel: [<ffffffff814a8e7a>] ? sch_direct_xmit+0x15a/0x1d0
Sep 12 16:06:41 trinity kernel: [<ffffffff8148ce38>] ? dev_queue_xmit+0x228/0x320
Sep 12 16:06:41 trinity kernel: [<ffffffff8152afe8>] ? br_dev_queue_push_xmit+0x88/0xc0
Sep 12 16:06:41 trinity kernel: [<ffffffff8152b078>] ? br_forward_finish+0x58/0x60
Sep 12 16:06:41 trinity kernel: [<ffffffff8152b12a>] ? __br_forward+0xaa/0xd0
Sep 12 16:06:41 trinity kernel: [<ffffffff8152b1b5>] ? br_forward+0x65/0x70
Sep 12 16:06:41 trinity kernel: [<ffffffff8152c37f>] ? br_handle_frame_finish+0x21f/0x320
Sep 12 16:06:41 trinity kernel: [<ffffffff8152c642>] ? br_handle_frame+0x1c2/0x270
Sep 12 16:06:41 trinity kernel: [<ffffffff8153aa50>] ? vlan_hwaccel_do_receive+0x70/0x130
Sep 12 16:06:41 trinity kernel: [<ffffffff814869ae>] ? __netif_receive_skb+0x45e/0x7a0
Sep 12 16:06:41 trinity kernel: [<ffffffff8148a718>] ? netif_receive_skb+0x58/0x60
Sep 12 16:06:41 trinity kernel: [<ffffffff8148a830>] ? napi_skb_finish+0x50/0x70
Sep 12 16:06:41 trinity kernel: [<ffffffff8153b1d4>] ? vlan_gro_receive+0x84/0xa0
Sep 12 16:06:41 trinity kernel: [<ffffffffa00475f5>] ? bnx2x_rx_int+0x1055/0x15d0 [bnx2x]
Sep 12 16:06:41 trinity kernel: [<ffffffff813f03ca>] ? usbdev_release+0x12a/0x130
Sep 12 16:06:41 trinity kernel: [<ffffffff81400233>] ? ehci_work+0x303/0xaf0
Sep 12 16:06:41 trinity kernel: [<ffffffff81391439>] ? ftrace_profile_templ_scsi_cmd_done_timeout_templat e+0x1c9/0x250
Sep 12 16:06:41 trinity kernel: [<ffffffffa0047c1b>] ? bnx2x_poll+0xab/0x2f0 [bnx2x]
Sep 12 16:06:41 trinity kernel: [<ffffffff81399a7e>] ? scsi_io_completion+0x2ce/0x6e0
Sep 12 16:06:41 trinity kernel: [<ffffffff8148be3b>] ? net_rx_action+0x10b/0x2f0
Sep 12 16:06:41 trinity kernel: [<ffffffff8107f443>] ? __do_softirq+0x103/0x260
Sep 12 16:06:41 trinity kernel: [<ffffffff812ca85e>] ? irq_2_iommu+0xe/0x50
Sep 12 16:06:41 trinity kernel: [<ffffffff8100c44c>] ? call_softirq+0x1c/0x30
Sep 12 16:06:41 trinity kernel: [<ffffffff81010195>] ? do_softirq+0x65/0xa0
Sep 12 16:06:41 trinity kernel: [<ffffffff8107f26d>] ? irq_exit+0xcd/0xd0
Sep 12 16:06:41 trinity kernel: [<ffffffff81565af5>] ? do_IRQ+0x75/0xf0
Sep 12 16:06:41 trinity kernel: [<ffffffff8100ba93>] ? ret_from_intr+0x0/0x11
Sep 12 16:06:41 trinity kernel: <EOI> [<ffffffff812ef95e>] ? intel_idle+0xde/0x170
Sep 12 16:06:41 trinity kernel: [<ffffffff812ef941>] ? intel_idle+0xc1/0x170
Sep 12 16:06:41 trinity kernel: [<ffffffff81450f77>] ? cpuidle_idle_call+0xa7/0x140
Sep 12 16:06:41 trinity kernel: [<ffffffff8100a013>] ? cpu_idle+0xb3/0x110
Sep 12 16:06:41 trinity kernel: [<ffffffff815414c5>] ? rest_init+0x85/0x90
Sep 12 16:06:41 trinity kernel: [<ffffffff81c34f76>] ? start_kernel+0x406/0x412
Sep 12 16:06:41 trinity kernel: [<ffffffff81c3433a>] ? x86_64_start_reservations+0x125/0x129
Sep 12 16:06:41 trinity kernel: [<ffffffff81c34453>] ? x86_64_start_kernel+0x115/0x124
Sep 12 16:06:41 trinity kernel: ---[ end trace afb55001d9fa461c ]---
Sep 12 16:06:41 trinity kernel: Tainting kernel with flag 0x9
Sep 12 16:06:41 trinity kernel: Pid: 0, comm: swapper veid: 0 Tainted: G W --------------- 2.6.32-29-pve #1
Sep 12 16:06:41 trinity kernel: Call Trace:
Sep 12 16:06:41 trinity kernel: <IRQ> [<ffffffff81075f11>] ? add_taint+0x71/0x80
Sep 12 16:06:41 trinity kernel: [<ffffffff81076095>] ? warn_slowpath_common+0x95/0xc0
Sep 12 16:06:41 trinity kernel: [<ffffffff81076176>] ? warn_slowpath_fmt+0x46/0x50
Sep 12 16:06:41 trinity kernel: [<ffffffff81486482>] ? skb_warn_bad_offload+0xc2/0xf0
Sep 12 16:06:41 trinity kernel: [<ffffffff8148bb51>] ? __skb_gso_segment+0x71/0xc0
Sep 12 16:06:41 trinity kernel: [<ffffffff8148bbb3>] ? skb_gso_segment+0x13/0x20
Sep 12 16:06:41 trinity kernel: [<ffffffff8148c704>] ? dev_hard_start_xmit+0x94/0x5a0
Sep 12 16:06:41 trinity kernel: [<ffffffff814a8e7a>] ? sch_direct_xmit+0x15a/0x1d0
Sep 12 16:06:41 trinity kernel: [<ffffffff8148ce38>] ? dev_queue_xmit+0x228/0x320
Sep 12 16:06:41 trinity kernel: [<ffffffff8152afe8>] ? br_dev_queue_push_xmit+0x88/0xc0
Sep 12 16:06:41 trinity kernel: [<ffffffff8152b078>] ? br_forward_finish+0x58/0x60
Sep 12 16:06:41 trinity kernel: [<ffffffff8152b12a>] ? __br_forward+0xaa/0xd0
Sep 12 16:06:41 trinity kernel: [<ffffffff8152b1b5>] ? br_forward+0x65/0x70
Sep 12 16:06:41 trinity kernel: [<ffffffff8152c37f>] ? br_handle_frame_finish+0x21f/0x320
Sep 12 16:06:41 trinity kernel: [<ffffffff8152c642>] ? br_handle_frame+0x1c2/0x270
Sep 12 16:06:41 trinity kernel: [<ffffffff8153aa50>] ? vlan_hwaccel_do_receive+0x70/0x130
Sep 12 16:06:41 trinity kernel: [<ffffffff814869ae>] ? __netif_receive_skb+0x45e/0x7a0
Sep 12 16:06:41 trinity kernel: [<ffffffff8148a718>] ? netif_receive_skb+0x58/0x60
Sep 12 16:06:41 trinity kernel: [<ffffffff8148a830>] ? napi_skb_finish+0x50/0x70
Sep 12 16:06:41 trinity kernel: [<ffffffff8153b1d4>] ? vlan_gro_receive+0x84/0xa0
Sep 12 16:06:41 trinity kernel: [<ffffffffa00475f5>] ? bnx2x_rx_int+0x1055/0x15d0 [bnx2x]
Sep 12 16:06:41 trinity kernel: [<ffffffff813f03ca>] ? usbdev_release+0x12a/0x130
Sep 12 16:06:41 trinity kernel: [<ffffffff81400233>] ? ehci_work+0x303/0xaf0
Sep 12 16:06:41 trinity kernel: [<ffffffff81391439>] ? ftrace_profile_templ_scsi_cmd_done_timeout_templat e+0x1c9/0x250
Sep 12 16:06:41 trinity kernel: [<ffffffffa0047c1b>] ? bnx2x_poll+0xab/0x2f0 [bnx2x]
Sep 12 16:06:41 trinity kernel: [<ffffffff81399a7e>] ? scsi_io_completion+0x2ce/0x6e0
Sep 12 16:06:41 trinity kernel: [<ffffffff8148be3b>] ? net_rx_action+0x10b/0x2f0
Sep 12 16:06:41 trinity kernel: [<ffffffff8107f443>] ? __do_softirq+0x103/0x260
Sep 12 16:06:41 trinity kernel: [<ffffffff812ca85e>] ? irq_2_iommu+0xe/0x50
Sep 12 16:06:41 trinity kernel: [<ffffffff8100c44c>] ? call_softirq+0x1c/0x30
Sep 12 16:06:41 trinity kernel: [<ffffffff81010195>] ? do_softirq+0x65/0xa0
Sep 12 16:06:41 trinity kernel: [<ffffffff8107f26d>] ? irq_exit+0xcd/0xd0
Sep 12 16:06:41 trinity kernel: [<ffffffff81565af5>] ? do_IRQ+0x75/0xf0
Sep 12 16:06:41 trinity kernel: [<ffffffff8100ba93>] ? ret_from_intr+0x0/0x11
Sep 12 16:06:41 trinity kernel: <EOI> [<ffffffff812ef95e>] ? intel_idle+0xde/0x170
Sep 12 16:06:41 trinity kernel: [<ffffffff812ef941>] ? intel_idle+0xc1/0x170
Sep 12 16:06:41 trinity kernel: [<ffffffff81450f77>] ? cpuidle_idle_call+0xa7/0x140
Sep 12 16:06:41 trinity kernel: [<ffffffff8100a013>] ? cpu_idle+0xb3/0x110
Sep 12 16:06:41 trinity kernel: [<ffffffff815414c5>] ? rest_init+0x85/0x90
Sep 12 16:06:41 trinity kernel: [<ffffffff81c34f76>] ? start_kernel+0x406/0x412
Sep 12 16:06:41 trinity kernel: [<ffffffff81c3433a>] ? x86_64_start_reservations+0x125/0x129
Sep 12 16:06:41 trinity kernel: [<ffffffff81c34453>] ? x86_64_start_kernel+0x115/0x124
Sep 12 16:06:41 trinity kernel: ------------[ cut here ]------------
Sep 12 16:06:41 trinity kernel: WARNING: at net/core/dev.c:1917 skb_warn_bad_offload+0xc2/0xf0() (Tainted: G W --------------- )
Sep 12 16:06:41 trinity kernel: Hardware name: PowerEdge M620
Sep 12 16:06:41 trinity kernel: tun: caps=(0x80000049, 0x0) len=2802 data_len=1368 ip_summed=1
Sep 12 16:06:41 trinity kernel: Modules linked in: vzethdev vznetdev pio_nfs pio_direct pfmt_raw pfmt_ploop1 ploop simfs vzrst nf_nat nf_conntrack_ipv4 nf_defrag_ipv4 vzcpt nf_conntrack vzdquota vzmon vzdev ip6t_REJECT ip6table_mangle ip6table_filter ip6_tables xt_length xt_hl xt_tcpmss xt_TCPMSS iptable_mangle iptable_filter xt_multiport xt_limit xt_dscp ipt_REJECT vhost_net tun macvtap ip_tables macvlan kvm_intel kvm dlm configfs vzevent ib_iser rdma_cm ib_addr iw_cm ib_cm ib_sa ib_mad ib_core iscsi_tcp libiscsi_tcp libiscsi scsi_transport_iscsi nfsd nfs nfs_acl auth_rpcgss fscache lockd sunrpc bonding 8021q garp ipv6 fuse snd_pcsp iTCO_wdt snd_pcm iTCO_vendor_support snd_page_alloc snd_timer snd soundcore lpc_ich dcdbas sb_edac edac_core mfd_core shpchp wmi power_meter ext3 mbcache jbd usb_storage sg ses enclosure megaraid_sas ahci bnx2x mdio [last unloaded: scsi_wait_scan]
Sep 12 16:06:41 trinity kernel: Pid: 0, comm: swapper veid: 0 Tainted: G W --------------- 2.6.32-29-pve #1
Sep 12 16:06:41 trinity kernel: Call Trace:
Sep 12 16:06:41 trinity kernel: <IRQ> [<ffffffff81076088>] ? warn_slowpath_common+0x88/0xc0
Sep 12 16:06:41 trinity kernel: [<ffffffff81076176>] ? warn_slowpath_fmt+0x46/0x50
Sep 12 16:06:41 trinity kernel: [<ffffffff810627d5>] ? try_to_wake_up+0xb5/0x4c0
Sep 12 16:06:41 trinity kernel: [<ffffffff81486482>] ? skb_warn_bad_offload+0xc2/0xf0
Sep 12 16:06:41 trinity kernel: [<ffffffff8148bb51>] ? __skb_gso_segment+0x71/0xc0
Sep 12 16:06:41 trinity kernel: [<ffffffff8148bbb3>] ? skb_gso_segment+0x13/0x20
Sep 12 16:06:41 trinity kernel: [<ffffffff8148c704>] ? dev_hard_start_xmit+0x94/0x5a0
Sep 12 16:06:41 trinity kernel: [<ffffffff814a8e7a>] ? sch_direct_xmit+0x15a/0x1d0
Sep 12 16:06:41 trinity kernel: [<ffffffff8148ce38>] ? dev_queue_xmit+0x228/0x320
Sep 12 16:06:41 trinity kernel: [<ffffffff8152afe8>] ? br_dev_queue_push_xmit+0x88/0xc0
Sep 12 16:06:41 trinity kernel: [<ffffffff8152b078>] ? br_forward_finish+0x58/0x60
Sep 12 16:06:41 trinity kernel: [<ffffffff8152b12a>] ? __br_forward+0xaa/0xd0
Sep 12 16:06:41 trinity kernel: [<ffffffff8152b1b5>] ? br_forward+0x65/0x70
Sep 12 16:06:41 trinity kernel: [<ffffffff8152c37f>] ? br_handle_frame_finish+0x21f/0x320
Sep 12 16:06:41 trinity kernel: [<ffffffff8152c642>] ? br_handle_frame+0x1c2/0x270
Sep 12 16:06:41 trinity kernel: [<ffffffff8153aa50>] ? vlan_hwaccel_do_receive+0x70/0x130
Sep 12 16:06:41 trinity kernel: [<ffffffff814869ae>] ? __netif_receive_skb+0x45e/0x7a0
Sep 12 16:06:41 trinity kernel: [<ffffffff8148a718>] ? netif_receive_skb+0x58/0x60
Sep 12 16:06:41 trinity kernel: [<ffffffff8148a830>] ? napi_skb_finish+0x50/0x70
Sep 12 16:06:41 trinity kernel: [<ffffffff8153b1d4>] ? vlan_gro_receive+0x84/0xa0
Sep 12 16:06:41 trinity kernel: [<ffffffffa00475f5>] ? bnx2x_rx_int+0x1055/0x15d0 [bnx2x]
Sep 12 16:06:41 trinity kernel: [<ffffffff813f03cb>] ? usbdev_release+0x12b/0x130
Sep 12 16:06:41 trinity kernel: [<ffffffff81400234>] ? ehci_work+0x304/0xaf0
Sep 12 16:06:41 trinity kernel: [<ffffffff8139143b>] ? ftrace_profile_templ_scsi_cmd_done_timeout_templat e+0x1cb/0x250
Sep 12 16:06:41 trinity kernel: [<ffffffffa0047c1b>] ? bnx2x_poll+0xab/0x2f0 [bnx2x]
Sep 12 16:06:41 trinity kernel: [<ffffffff81399a7e>] ? scsi_io_completion+0x2ce/0x6e0
Sep 12 16:06:41 trinity kernel: [<ffffffff8148be3b>] ? net_rx_action+0x10b/0x2f0
Sep 12 16:06:41 trinity kernel: [<ffffffff8107f443>] ? __do_softirq+0x103/0x260
Sep 12 16:06:41 trinity kernel: [<ffffffff812ca85e>] ? irq_2_iommu+0xe/0x50
Sep 12 16:06:41 trinity kernel: [<ffffffff8100c44c>] ? call_softirq+0x1c/0x30
Sep 12 16:06:41 trinity kernel: [<ffffffff81010195>] ? do_softirq+0x65/0xa0
Sep 12 16:06:41 trinity kernel: [<ffffffff8107f26d>] ? irq_exit+0xcd/0xd0
Sep 12 16:06:41 trinity kernel: [<ffffffff81565af5>] ? do_IRQ+0x75/0xf0
Sep 12 16:06:41 trinity kernel: [<ffffffff8100ba93>] ? ret_from_intr+0x0/0x11
Sep 12 16:06:41 trinity kernel: <EOI> [<ffffffff812ef95e>] ? intel_idle+0xde/0x170
Sep 12 16:06:41 trinity kernel: [<ffffffff812ef941>] ? intel_idle+0xc1/0x170
Sep 12 16:06:41 trinity kernel: [<ffffffff81450f77>] ? cpuidle_idle_call+0xa7/0x140
Sep 12 16:06:41 trinity kernel: [<ffffffff8100a013>] ? cpu_idle+0xb3/0x110
Sep 12 16:06:41 trinity kernel: [<ffffffff815414c5>] ? rest_init+0x85/0x90
Sep 12 16:06:41 trinity kernel: [<ffffffff81c34f76>] ? start_kernel+0x406/0x412
Sep 12 16:06:41 trinity kernel: [<ffffffff81c3433a>] ? x86_64_start_reservations+0x125/0x129
Sep 12 16:06:41 trinity kernel: [<ffffffff81c34453>] ? x86_64_start_kernel+0x115/0x124
Sep 12 16:06:41 trinity kernel: ---[ end trace afb55001d9fa461d ]---
Sep 12 16:06:41 trinity kernel: Tainting kernel with flag 0x9
Sep 12 16:06:41 trinity kernel: Pid: 0, comm: swapper veid: 0 Tainted: G W --------------- 2.6.32-29-pve #1
Sep 12 16:06:41 trinity kernel: Call Trace:
Sep 12 16:06:41 trinity kernel: <IRQ> [<ffffffff81075f11>] ? add_taint+0x71/0x80
Sep 12 16:06:41 trinity kernel: [<ffffffff81076095>] ? warn_slowpath_common+0x95/0xc0
Sep 12 16:06:41 trinity kernel: [<ffffffff81076176>] ? warn_slowpath_fmt+0x46/0x50
Sep 12 16:06:41 trinity kernel: [<ffffffff810627d5>] ? try_to_wake_up+0xb5/0x4c0
Sep 12 16:06:41 trinity kernel: [<ffffffff81486482>] ? skb_warn_bad_offload+0xc2/0xf0
Sep 12 16:06:41 trinity kernel: [<ffffffff8148bb51>] ? __skb_gso_segment+0x71/0xc0
Sep 12 16:06:41 trinity kernel: [<ffffffff8148bbb3>] ? skb_gso_segment+0x13/0x20
Sep 12 16:06:41 trinity kernel: [<ffffffff8148c704>] ? dev_hard_start_xmit+0x94/0x5a0
Sep 12 16:06:41 trinity kernel: [<ffffffff814a8e7a>] ? sch_direct_xmit+0x15a/0x1d0
Sep 12 16:06:41 trinity kernel: [<ffffffff8148ce38>] ? dev_queue_xmit+0x228/0x320
Sep 12 16:06:41 trinity kernel: [<ffffffff8152afe8>] ? br_dev_queue_push_xmit+0x88/0xc0
Sep 12 16:06:41 trinity kernel: [<ffffffff8152b078>] ? br_forward_finish+0x58/0x60
Sep 12 16:06:41 trinity kernel: [<ffffffff8152b12a>] ? __br_forward+0xaa/0xd0
Sep 12 16:06:41 trinity kernel: [<ffffffff8152b1b5>] ? br_forward+0x65/0x70
Sep 12 16:06:41 trinity kernel: [<ffffffff8152c37f>] ? br_handle_frame_finish+0x21f/0x320
Sep 12 16:06:41 trinity kernel: [<ffffffff8152c642>] ? br_handle_frame+0x1c2/0x270
Sep 12 16:06:41 trinity kernel: [<ffffffff8153aa50>] ? vlan_hwaccel_do_receive+0x70/0x130
Sep 12 16:06:41 trinity kernel: [<ffffffff814869ae>] ? __netif_receive_skb+0x45e/0x7a0
Sep 12 16:06:41 trinity kernel: [<ffffffff8148a718>] ? netif_receive_skb+0x58/0x60
Sep 12 16:06:41 trinity kernel: [<ffffffff8148a830>] ? napi_skb_finish+0x50/0x70
Sep 12 16:06:41 trinity kernel: [<ffffffff8153b1d4>] ? vlan_gro_receive+0x84/0xa0
Sep 12 16:06:41 trinity kernel: [<ffffffffa00475f5>] ? bnx2x_rx_int+0x1055/0x15d0 [bnx2x]
Sep 12 16:06:41 trinity kernel: [<ffffffff813f03cb>] ? usbdev_release+0x12b/0x130
Sep 12 16:06:41 trinity kernel: [<ffffffff81400234>] ? ehci_work+0x304/0xaf0
Sep 12 16:06:41 trinity kernel: [<ffffffff8139143b>] ? ftrace_profile_templ_scsi_cmd_done_timeout_templat e+0x1cb/0x250
Sep 12 16:06:41 trinity kernel: [<ffffffffa0047c1b>] ? bnx2x_poll+0xab/0x2f0 [bnx2x]
Sep 12 16:06:41 trinity kernel: [<ffffffff81399a7e>] ? scsi_io_completion+0x2ce/0x6e0
Sep 12 16:06:41 trinity kernel: [<ffffffff8148be3b>] ? net_rx_action+0x10b/0x2f0
Sep 12 16:06:41 trinity kernel: [<ffffffff8107f443>] ? __do_softirq+0x103/0x260
Sep 12 16:06:41 trinity kernel: [<ffffffff812ca85e>] ? irq_2_iommu+0xe/0x50
Sep 12 16:06:41 trinity kernel: [<ffffffff8100c44c>] ? call_softirq+0x1c/0x30
Sep 12 16:06:41 trinity kernel: [<ffffffff81010195>] ? do_softirq+0x65/0xa0
Sep 12 16:06:41 trinity kernel: [<ffffffff8107f26d>] ? irq_exit+0xcd/0xd0
Sep 12 16:06:41 trinity kernel: [<ffffffff81565af5>] ? do_IRQ+0x75/0xf0
Sep 12 16:06:41 trinity kernel: [<ffffffff8100ba93>] ? ret_from_intr+0x0/0x11
Sep 12 16:06:41 trinity kernel: <EOI> [<ffffffff812ef95e>] ? intel_idle+0xde/0x170
Sep 12 16:06:41 trinity kernel: [<ffffffff812ef941>] ? intel_idle+0xc1/0x170
Sep 12 16:06:41 trinity kernel: [<ffffffff81450f77>] ? cpuidle_idle_call+0xa7/

↧

Proxmox firewall and 3rd party firewalls

September 17, 2014, 7:32 am

≫ Next: Proxmox - Backup to FTP fails

≪ Previous: proxmox 3.2 kernel issues

Quick question...

I'm running Shorewall on my Proxmox, will the new Proxmox firewall have any effect on this setup ?

I presume that both are front ends for iptables but better safe than sorry.

Thanks

↧

Proxmox - Backup to FTP fails

September 17, 2014, 9:55 am

≫ Next: NFS server over ipv6

≪ Previous: Proxmox firewall and 3rd party firewalls

Hello,

I've got a little problem. I set up a ftp-space and mounted it via curlftpfs. Well, small backups are working fine, but larger backups are failing.

Either the backup task quits with messages like "broken pipe" or the backup is not completed and hangs at 100%.

A small excerpt from the backup logs:

Quote:

INFO: starting new backup job: vzdump 102 --remove 0 --mode snapshot --compress lzo --storage ftpdir --node mynode
INFO: Starting Backup of VM 102 (qemu)
INFO: status = running
INFO: update VM 102: -lock backup
INFO: backup mode: snapshot
INFO: ionice priority: 7
INFO: creating archive '/ftpdir/dump/vzdump-qemu-102-2014_09_17-08_27_03.vma.lzo'
INFO: started backup task 'db004854-f8e3-4f26-b4bd-6b73460d1835'
INFO: status: 0% (335413248/536870912000), sparse 0% (297332736), duration 3, 111/12 MB/s
INFO: status: 1% (5433589760/536870912000), sparse 0% (2610274304), duration 57, 94/51 MB/s
INFO: status: 2% (10856038400/536870912000), sparse 1% (8030154752), duration 87, 180/0 MB/s
INFO: status: 3% (16229597184/536870912000), sparse 2% (13402165248), duration 118, 173/0 MB/s
INFO: status: 4% (21485256704/536870912000), sparse 3% (18655227904), duration 147, 181/0 MB/s
INFO: status: 5% (26863796224/536870912000), sparse 4% (24031535104), duration 178, 173/0 MB/s
INFO: status: 6% (32346210304/536870912000), sparse 5% (29494026240), duration 211, 166/0 MB/s
INFO: status: 7% (37698011136/536870912000), sparse 6% (34844483584), duration 240, 184/0 MB/s
INFO: status: 8% (43081728000/536870912000), sparse 7% (40226127872), duration 269, 185/0 MB/s
INFO: status: 9% (48338436096/536870912000), sparse 7% (40738893824), duration 352, 63/57 MB/s
INFO: status: 10% (53694169088/536870912000), sparse 7% (40904134656), duration 451, 54/52 MB/s
INFO: status: 11% (59091714048/536870912000), sparse 7% (41179566080), duration 550, 54/51 MB/s
INFO: status: 12% (64457015296/536870912000), sparse 7% (41400152064), duration 651, 53/50 MB/s
INFO: status: 13% (69801607168/536870912000), sparse 7% (41797697536), duration 740, 60/55 MB/s
INFO: status: 14% (75174117376/536870912000), sparse 7% (42182352896), duration 835, 56/52 MB/s
INFO: status: 15% (80537452544/536870912000), sparse 7% (42547998720), duration 935, 53/49 MB/s
INFO: status: 16% (85915992064/536870912000), sparse 7% (42738003968), duration 1035, 53/51 MB/s
INFO: status: 17% (91321139200/536870912000), sparse 8% (43017158656), duration 1132, 55/52 MB/s
INFO: status: 18% (96651051008/536870912000), sparse 8% (43217596416), duration 1249, 45/43 MB/s
INFO: status: 19% (102013599744/536870912000), sparse 8% (43499094016), duration 1362, 47/44 MB/s
INFO: status: 20% (107419860992/536870912000), sparse 8% (43753431040), duration 1467, 51/49 MB/s
INFO: status: 21% (112778280960/536870912000), sparse 8% (44048039936), duration 1574, 50/47 MB/s
INFO: status: 22% (118141616128/536870912000), sparse 8% (44218261504), duration 1682, 49/48 MB/s
INFO: status: 23% (123535228928/536870912000), sparse 8% (45944676352), duration 1768, 62/42 MB/s
INFO: status: 24% (128887816192/536870912000), sparse 9% (51267166208), duration 1796, 191/1 MB/s
INFO: status: 25% (134286409728/536870912000), sparse 10% (56620920832), duration 1825, 186/1 MB/s
INFO: status: 26% (139655380992/536870912000), sparse 11% (61961695232), duration 1856, 173/0 MB/s
INFO: status: 27% (145001349120/536870912000), sparse 12% (67288346624), duration 1885, 184/0 MB/s
INFO: status: 28% (150469148672/536870912000), sparse 13% (72738787328), duration 1914, 188/0 MB/s
INFO: status: 29% (155745976320/536870912000), sparse 14% (77923852288), duration 1943, 181/3 MB/s
INFO: status: 30% (161111080960/536870912000), sparse 15% (83272171520), duration 1973, 178/0 MB/s
INFO: status: 31% (166470877184/536870912000), sparse 16% (88296599552), duration 2013, 133/8 MB/s
INFO: status: 32% (171854069760/536870912000), sparse 17% (93080211456), duration 2087, 72/8 MB/s
INFO: status: 33% (177185292288/536870912000), sparse 18% (97192013824), duration 2454, 14/3 MB/s
INFO: status: 34% (182636511232/536870912000), sparse 18% (101347700736), duration 2556, 53/12 MB/s
INFO: status: 35% (187913338880/536870912000), sparse 19% (105332109312), duration 2622, 79/19 MB/s
INFO: status: 36% (193334804480/536870912000), sparse 20% (110643994624), duration 2655, 164/3 MB/s
INFO: status: 37% (198743949312/536870912000), sparse 21% (115582738432), duration 2689, 159/13 MB/s
INFO: status: 38% (204038602752/536870912000), sparse 21% (117158789120), duration 2768, 67/47 MB/s
INFO: status: 39% (209390600192/536870912000), sparse 21% (117547835392), duration 2960, 27/25 MB/s
INFO: status: 40% (214791880704/536870912000), sparse 21% (117856653312), duration 3164, 26/24 MB/s
INFO: status: 41% (220139880448/536870912000), sparse 22% (120890351616), duration 3226, 86/37 MB/s
INFO: status: 42% (225579630592/536870912000), sparse 23% (126154579968), duration 3256, 181/5 MB/s
INFO: status: 43% (230923042816/536870912000), sparse 24% (131286851584), duration 3287, 172/6 MB/s
INFO: status: 44% (236427083776/536870912000), sparse 25% (136665313280), duration 3318, 177/4 MB/s
INFO: status: 45% (241598070784/536870912000), sparse 26% (141613797376), duration 3350, 161/6 MB/s
INFO: status: 46% (247007215616/536870912000), sparse 27% (146869805056), duration 3380, 180/5 MB/s
INFO: status: 47% (252505423872/536870912000), sparse 28% (152125591552), duration 3412, 171/7 MB/s
INFO: status: 48% (257769472000/536870912000), sparse 29% (157195251712), duration 3444, 164/6 MB/s
INFO: status: 49% (263218397184/536870912000), sparse 30% (162491424768), duration 3476, 170/4 MB/s
INFO: status: 50% (268459900928/536870912000), sparse 31% (167616516096), duration 3508, 163/3 MB/s
INFO: status: 51% (273832673280/536870912000), sparse 32% (172691595264), duration 3542, 158/8 MB/s
INFO: status: 52% (279273734144/536870912000), sparse 33% (178039771136), duration 3573, 175/2 MB/s
INFO: status: 53% (284541845504/536870912000), sparse 33% (180453138432), duration 3643, 75/40 MB/s
INFO: status: 54% (290062008320/536870912000), sparse 34% (183768432640), duration 3705, 89/35 MB/s
INFO: status: 55% (295376715776/536870912000), sparse 35% (188776476672), duration 3736, 171/9 MB/s
INFO: status: 56% (300763971584/536870912000), sparse 36% (194061975552), duration 3769, 163/3 MB/s
INFO: status: 57% (306169184256/536870912000), sparse 37% (198805082112), duration 3812, 125/15 MB/s
INFO: status: 58% (311497129984/536870912000), sparse 37% (203661250560), duration 3845, 161/14 MB/s
INFO: status: 59% (316771270656/536870912000), sparse 38% (204311359488), duration 3938, 56/49 MB/s
INFO: status: 60% (322134605824/536870912000), sparse 38% (204532088832), duration 4042, 51/49 MB/s
INFO: status: 61% (327524548608/536870912000), sparse 38% (204918095872), duration 4145, 52/48 MB/s
INFO: status: 62% (332887293952/536870912000), sparse 38% (205172236288), duration 4247, 52/50 MB/s
INFO: status: 63% (338257575936/536870912000), sparse 38% (205547540480), duration 4349, 52/48 MB/s
INFO: status: 64% (343641161728/536870912000), sparse 38% (205812187136), duration 4450, 53/50 MB/s
INFO: status: 65% (348981690368/536870912000), sparse 38% (206346125312), duration 4553, 51/46 MB/s
INFO: status: 66% (354360229888/536870912000), sparse 38% (206713057280), duration 4654, 53/49 MB/s
INFO: status: 67% (359738769408/536870912000), sparse 38% (207159644160), duration 4754, 53/49 MB/s
INFO: status: 68% (365106954240/536870912000), sparse 38% (207598256128), duration 4860, 50/46 MB/s
INFO: status: 69% (370587926528/536870912000), sparse 39% (212911906816), duration 4901, 133/4 MB/s
INFO: status: 70% (375914299392/536870912000), sparse 40% (218073939968), duration 4931, 177/5 MB/s
INFO: status: 71% (381368664064/536870912000), sparse 41% (223436660736), duration 4966, 155/2 MB/s
INFO: status: 72% (386617638912/536870912000), sparse 42% (228685627392), duration 4996, 174/0 MB/s
INFO: status: 73% (392028946432/536870912000), sparse 43% (234090192896), duration 5028, 169/0 MB/s
INFO: status: 74% (397305708544/536870912000), sparse 44% (237779759104), duration 5078, 105/31 MB/s
INFO: status: 75% (402659475456/536870912000), sparse 45% (242087669760), duration 5118, 133/26 MB/s
INFO: status: 76% (408099553280/536870912000), sparse 46% (247449858048), duration 5154, 151/2 MB/s
INFO: status: 77% (413436149760/536870912000), sparse 47% (252779569152), duration 5189, 152/0 MB/s
INFO: status: 78% (418861809664/536870912000), sparse 48% (258205200384), duration 5223, 159/0 MB/s
INFO: status: 79% (424277835776/536870912000), sparse 49% (263621083136), duration 5258, 154/0 MB/s
INFO: status: 80% (429614497792/536870912000), sparse 50% (268846039040), duration 5290, 166/3 MB/s
INFO: status: 81% (434908889088/536870912000), sparse 51% (273875795968), duration 5324, 155/7 MB/s
INFO: status: 82% (440259837952/536870912000), sparse 51% (279059091456), duration 5356, 167/5 MB/s
INFO: status: 83% (445628678144/536870912000), sparse 52% (284231143424), duration 5388, 167/6 MB/s
INFO: status: 84% (450983165952/536870912000), sparse 53% (289464160256), duration 5421, 162/3 MB/s
INFO: status: 85% (456447229952/536870912000), sparse 54% (294778748928), duration 5456, 156/4 MB/s
INFO: status: 86% (461727727616/536870912000), sparse 55% (299924303872), duration 5487, 170/4 MB/s
INFO: status: 87% (467196837888/536870912000), sparse 56% (305070489600), duration 5522, 156/9 MB/s
INFO: status: 88% (472510300160/536870912000), sparse 57% (310342737920), duration 5556, 156/1 MB/s
INFO: status: 89% (477833265152/536870912000), sparse 58% (315593289728), duration 5593, 143/1 MB/s
INFO: status: 90% (483234545664/536870912000), sparse 59% (320994549760), duration 5626, 163/0 MB/s
INFO: status: 91% (488556199936/536870912000), sparse 60% (326316191744), duration 5657, 171/0 MB/s
INFO: status: 92% (493954007040/536870912000), sparse 61% (331709288448), duration 5689, 168/0 MB/s
INFO: status: 93% (499395395584/536870912000), sparse 62% (337085497344), duration 5722, 164/1 MB/s
INFO: status: 94% (504806375424/536870912000), sparse 63% (342496456704), duration 5757, 154/0 MB/s
INFO: status: 95% (510125015040/536870912000), sparse 64% (347814014976), duration 5791, 156/0 MB/s
INFO: status: 96% (515531538432/536870912000), sparse 65% (353121525760), duration 5825, 159/2 MB/s
INFO: status: 97% (520817147904/536870912000), sparse 66% (358407135232), duration 5856, 170/0 MB/s
INFO: status: 98% (526294450176/536870912000), sparse 67% (363884437504), duration 5886, 182/0 MB/s
INFO: status: 99% (531537854464/536870912000), sparse 68% (369127841792), duration 5918, 163/0 MB/s
INFO: status: 100% (536870912000/536870912000), sparse 69% (374460899328), duration 5948, 177/0 MB/s
INFO: transferred 536870 MB in 5948 seconds (90 MB/s)

(the last Info remains for hours and hours. I can't even cancel the task. I have to unmount the ftp and kill vzdump-task.)

Another error:

Quote:

INFO: starting new backup job: vzdump 101 102 103 104 --quiet 1 --mode snapshot --compress lzo --storage ftpdir --node mynode
INFO: Starting Backup of VM 101 (qemu)
INFO: status = running
INFO: update VM 101: -lock backup
INFO: backup mode: snapshot
INFO: ionice priority: 7
INFO: snapshots found (not included into backup)
INFO: creating archive '/ftpdir/dump/vzdump-qemu-101-2014_09_17-02_30_01.vma.lzo'
ERROR: got timeout
INFO: aborting backup job
ERROR: Backup of VM 101 failed - got timeout
INFO: Starting Backup of VM 102 (qemu)
INFO: status = running
INFO: update VM 102: -lock backup
INFO: backup mode: snapshot
INFO: ionice priority: 7
INFO: creating archive '/ftpdir/dump/vzdump-qemu-102-2014_09_17-02_30_36.vma.lzo'
INFO: started backup task 'f75c5b2d-f0c7-46a8-ae1c-eddec9a7097c'
INFO: status: 0% (11403264/536870912000), sparse 0% (2129920), duration 3, 3/3 MB/s
INFO: status: 1% (5504565248/536870912000), sparse 0% (2626834432), duration 664, 8/4 MB/s
INFO: status: 2% (10750066688/536870912000), sparse 1% (7871606784), duration 692, 187/0 MB/s
INFO: status: 3% (16173236224/536870912000), sparse 2% (13293895680), duration 723, 174/0 MB/s
INFO: status: 4% (21586247680/536870912000), sparse 3% (18704199680), duration 752, 186/0 MB/s
INFO: status: 5% (26886733824/536870912000), sparse 4% (24003768320), duration 780, 189/0 MB/s
INFO: status: 6% (32220446720/536870912000), sparse 5% (29335113728), duration 808, 190/0 MB/s
INFO: status: 7% (37700894720/536870912000), sparse 6% (34813890560), duration 839, 176/0 MB/s
INFO: status: 8% (43095359488/536870912000), sparse 7% (40207466496), duration 868, 186/0 MB/s
INFO: status: 9% (48319430656/536870912000), sparse 7% (40742154240), duration 2857, 2/2 MB/s
lzop: Input/output error:
INFO: status: 9% (49243160576/536870912000), sparse 7% (40745463808), duration 3982, 0/0 MB/s
ERROR: vma_queue_write: write error - Broken pipe
INFO: aborting backup job
ERROR: Backup of VM 102 failed - vma_queue_write: write error - Broken pipe
INFO: Starting Backup of VM 103 (qemu)
INFO: status = running
INFO: update VM 103: -lock backup
INFO: backup mode: snapshot
INFO: ionice priority: 7
INFO: creating archive '/ftpdir/dump/vzdump-qemu-103-2014_09_17-03_40_33.vma.lzo'
INFO: started backup task '44baf251-65eb-4f3e-a2b8-3cc52ee916c4'
INFO: status: 0% (3801088/536870912000), sparse 0% (1503232), duration 3, 1/0 MB/s
lzop: Input/output error:
INFO: status: 0% (4492951552/536870912000), sparse 0% (897368064), duration 3577, 1/1 MB/s
ERROR: vma_queue_write: write error - Broken pipe
INFO: aborting backup job

The ftp-server is alright, I was able to upload 100GB file without problems via terminal.

What can I do here?

↧

NFS server over ipv6

September 17, 2014, 10:10 am

≫ Next: OVMF support

≪ Previous: Proxmox - Backup to FTP fails

Hi,

i'm still using proxmox 3.2 and i have 2 servers, (one host with proxmox V3.2 and another one with debian 7.0)
Both of them have one ipv 4 ans one ipv6 configured.

I have installed a NFS serveur on my debian 7.0 server.
i can add via the web interface of proxmox my NFS server with the ipv4 address but i can't with the ipv6 address.
but i can do in SSH via
mount -t nfs '[2001:41d0:*:7**8::1]':/var/lib/vz/copy_hard /mnt/pve/copy_backup and the NFS server is well mounted.
so as i can do it in SSH, my firewall / NFS configuration is OK i think.

So is it possible to use a NFS serveur over ipv6 with the web interface of proxmox ? What do i have to do better ?

Thanks you in advance,
Sorry for my english, it's not my native language.

↧

OVMF support

September 17, 2014, 10:46 am

≫ Next: can't boot, modprobe stuck on "acpi:IPI0001"

≪ Previous: NFS server over ipv6

Any chance to see OVMF support?

Can be a game changer in VGA passthrough...

↧

can't boot, modprobe stuck on "acpi:IPI0001"

September 17, 2014, 10:48 am

≫ Next: Proxmox 3.3 NO-VNC with port 443

≪ Previous: OVMF support

I noticed that one server in my cluster - the one I typically test updates on first - has been down for a little while.
(Kudos to Proxmox for making a technology where 25% of my cluster has been down for days or possibly weeks without me even noticing.)

The reason it's dead in the water is that the boot process is stuck on:
"udevd[676]: timeout: killing '/sbin/modprobe -b acpi:IPI0001:' [716]"

over and over and over and over... it never stops.

The last thing I remember doing on this server was switching from the linux bridging stuff to openvswitch, but it was working fine (even after a reboot) after I did that.
The only references I can find online to this device are a Dell R300, which is not at all what I have - these are Dell C-series blade servers, with literally nothing in common with the (much newer) R300 servers. I've tried all the various power management options in the BIOS anyway, to no avail.

I am running a 3.x kernel on this system and have been for some time...

Any ideas? I'm going to try booting a 2.x kernel next and see if I can at least get the system back up so I can update it.

-Adam

↧

Proxmox 3.3 NO-VNC with port 443

September 17, 2014, 2:46 pm

≫ Next: Ceph stopped talking after 3.3 upgrade

≪ Previous: can't boot, modprobe stuck on "acpi:IPI0001"

Hi,

In my test environment I tested no-vnc on proxmox 3.3-1 and I noticed that it doesnot work over a reverse proxy 443 --> 8006. On proxmox I use a iptables rule: -A PREROUTING -d <IP> -p tcp --dport 443 -j DNAT --to-destination <IP>:8006. Connecting to the proxmox server over 443 / 8006 and using the VNC console it is working fine. If I connect a VM on the proxmox server over port 8006 using no-vnc the connection is Ok. But when I connect a VM on the proxmox server over port 443 using no-vnc I get a pop-up from no-vnc to provide host/port/password.

Is there a way to keep using port 443 (much less blocked by firewalls) and to use no-vnc?

Regards...

↧

Ceph stopped talking after 3.3 upgrade

September 17, 2014, 11:38 pm

≫ Next: Install proxmox 3.3 IBM BLADE problem

≪ Previous: Proxmox 3.3 NO-VNC with port 443

I just upgraded all 6 proxmox nodes and now Ceph cluster stopped talking to each other. I had Ceph 0.72 previously. After upgrade it is 0.80. Did i miss a upgrade step??

↧

Install proxmox 3.3 IBM BLADE problem

September 18, 2014, 12:25 am

≫ Next: ProxMox 3.2 to 3.3, impressions and a problem

≪ Previous: Ceph stopped talking after 3.3 upgrade

I installed proxmox on IBM Bladecenter H . Installation work good, sucessfylly installed . After reset serwer proxmox not start
and serwer reseting.
Its possible install proxmox on this hardware with uefi ?
Kris

↧

ProxMox 3.2 to 3.3, impressions and a problem

September 18, 2014, 1:12 am

≫ Next: Can't install proxmox on debian 7

≪ Previous: Install proxmox 3.3 IBM BLADE problem

So I've started the upgrade process to take our nodes from 3.2 to 3.3, and thus far, I have a few impressions to share.

noVNC performs markedly faster than VNC over medium-to-long network distances/remote tunnels
upgrade process was quick and painless (as expected)
the system as a whole shows a small, but distinct, performance improvement

One problem we've had, though, is that a lot of our Windows-based VMs, but disturbingly not ALL, have deactivated their Windows licencing after the upgrade. Microsoft are going to be receiving 3.7 metric tonnes of calls from us, trying to reactivate them all... so. My question as to this problem would, I guess, be: is there any way we can avoid that problem? Short of not upgrading, which isn't really to be considered a viable option... the improved performance is just TOO worth it.

↧

Can't install proxmox on debian 7

September 18, 2014, 1:16 am

≫ Next: Proxmox WebGUI - AD User Login / Invalid Username Format

≪ Previous: ProxMox 3.2 to 3.3, impressions and a problem

I made a new installation of debian 7 x64 minimal

then began to install proxmox on this manual
https://pve.proxmox.com/wiki/Install..._Debian_Wheezy

cat /etc/hosts

127.0.0.1 localhost
# 127.0.1.1 SHODAN.TEKNIPASS.LOC SHODAN
192.168.0.13 SHODAN.TEKNIPASS.LOC SHODAN

# The following lines are desirable for IPv6 capable hosts

::1 ip6-localhost ip6-loopback
fe00::0 ip6-localnet
ff00::0 ip6-mcastprefix
ff02::1 ip6-allnodes
ff02::2 ip6-allrouters
ff02::3 ip6-allhostS

cat /etc/apt/sources.list

# Debian Wheezy
deb http://ftp.at.debian.org/debian wheezy main contrib
# PVE packages provided by proxmox.com
deb http://download.proxmox.com/debian wheezy pve
# Debian Wheezy security updates
deb http://security.debian.org/ wheezy/updates main contrib

wget -O- "http://download.proxmox.com/debian/key.asc" | apt-key add -
apt-get update && apt-get dist-upgrade
apt-get install pve-firmware pve-kernel-2.6.32-24-pve
uname -a (Linux 2.6.32-24-pve...)
apt-get remove linux-image-amd64 linux-image-3.2.0-4-amd64 linux-base
update-grub
reboot

apt-get install proxmox-ve-2.6.32 ntp ssh lvm2 postfix ksm-control-daemon vzprocps open-iscsi bootlogd

at the end of the installation package the following errors
l-daemon vzprocps open-iscsi bootlogd
Lecture des listes de paquets... Fait
Construction de l'arbre des dÃ©pendances
Lecture des informations d'Ã©tat... Fait
ntp est dÃ©jÃ la plus rÃ©cente version disponible.
open-iscsi est dÃ©jÃ la plus rÃ©cente version disponible.
ssh est dÃ©jÃ la plus rÃ©cente version disponible.
postfix est dÃ©jÃ la plus rÃ©cente version disponible.
bootlogd est dÃ©jÃ la plus rÃ©cente version disponible.
proxmox-ve-2.6.32 est dÃ©jÃ la plus rÃ©cente version disponible.
lvm2 est dÃ©jÃ la plus rÃ©cente version disponible.
ksm-control-daemon est dÃ©jÃ la plus rÃ©cente version disponible.
vzprocps est dÃ©jÃ la plus rÃ©cente version disponible.
Vous pouvez lancer Â«Â apt-get -f installÂ Â» pour corriger ces problÃ¨mesÂ :
Les paquets suivants contiennent des dÃ©pendances non satisfaitesÂ :
proxmox-ve-2.6.32 : DÃ©pend: pve-qemu-kvm mais ne sera pas installÃ©
qemu-server : DÃ©pend: pve-qemu-kvm (>= 1.4-16) mais ne sera pas installÃ©
E: DÃ©pendances non satisfaites. Essayez Â«Â apt-get -f installÂ Â» sans paquet
(ou indiquez une solution).

please help to solve the problem

↧

Latest Images