Recent content by bazzi

Hi Aaron, I have added it and activate it.I will keep you posted! Thanks, Tim

on a backup storage server with both ip's 10.221.183.35 and 10.221.184.35 in that VLAN. No I din't change any IP's. But for the first post a collegue gived me bogus internal ip's. We was afraid for information on the web, but it are only private ip's.... I fix the first post.

ahhh shoot. I am sending you the wrong ip address. This is the correct one: 1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000 link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00 inet 127.0.0.1/8 scope host lo valid_lft forever...

Hi Aaron, Unfortinaly still. 1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000 link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00 inet 127.0.0.1/8 scope host lo valid_lft forever preferred_lft forever inet6 ::1/128 scope host...

Ok I am doing something wrong but I don't see it. The situation: 1x 10GBe uplink to internal network (same VLAN as the 1GBe internal network) 1x 1GBe uplink to internal network (same VLAN as the 10GBe internal network) 1x 1GBe uplink to external network (diffrent VLAN's) What am i tring to do...

I have the same thing with 5.1 (same versions) I have a cluster on 4.4 and those have the option PCID. (same hardware, I updated one member of that cluster to 5.1 and the option was gone) Looks like the change is in 4.4, not 5.1.

Your welcome! We have only RAID 10 (so raid 1 and 0 combined) but we experienced a slowed down system. So therefore the heads up ;-)

Yes we have done that. We first had 7 sas disks and added 7 more. Then we create a new storage pool with new shared disks. Then you have to reboot each server to show the new disks and you are good to go! A tip: don't create one great shared disk, but mutiple. Else your system will slow down...

Ok tonight I had a strange situation: 1. One of my servers was fenced during a backup of KVM VM. 2. The server was going up good. 3. The server would start all VM's on the machine. 4. All VM's where started, except the one that was backupping. 5. I needed to manualy unlock that VM and start it...

What does your logs say?

That you can safely ignore. Does the fenching work?

Sorry you are totaly right! I run the update again and the fence agents are updated!

In a fresh 3.1 install the issue is back. Please add it upstream!

Wow that was quick ;-) I have followed the wiki articale about Intel Modular Server with Multipath (http://pve.proxmox.com/wiki/Intel_Modular_Server#Optional:_Configure_Multi-Path). root@timo:~# multipath -llvmdisks (2225d0001557dd1ea) dm-1 Intel,Multi-Flex size=1000G features='1...

I have the same problem! Did you find a fix?