Search results

I appreciate the extra tidbit .. thanks I can't set tunables to jewel because I need krbd for containers... so for now, I will set tunables to hammer until we get direction otherwise that krbd is supported at the jewel level I have Proxmox updates to do on the nodes that run VMs so I'll update...

Thank you much!

Is that link recommended? Is it considered stable I mean or in other words, production ready? Would it now change to ... deb http://gitbuilder.ceph.com/ceph-deb-jessie-x86_64-basic/ref/v10.2.5/ jessie main for the Jewel release of Ceph?

I think I'm being thoroughly misunderstood. The point isn't whether or not it's a QEMU problem or not. The point is that Proxmox IS Proxmox because of what it does and how it does it, and this is accomplished by means of the software components utilized. QEMU is an integrative part of Proxmox...

Someone from Proxmox's team needs to answer this and with a more valid answer than, "this is by design in qemu" ... instead, what is being done about it is what's needed to be known. You can't talk "Enterprise" and leave something like this alone. No offense to anyone, it's just that this is...

So, what's the status of this at this time? We've been seeing bad backup performance since before Ceph, but since Ceph, is abysmal. Any news on when this will be working without using some homebrew scripting? In other words, using the standard Qemu backup method ... is there something in the...

Something of note: I just had the same issue after reconfiguring the Bridges to use Openvswitch instead of Linux bridging Nothing I did would bring up the corosync service so as a last ditch effort, I checked the /etc/network/interfaces files and found that vmbr1 was first and vmbr0 was second...

Please post your setup How many servers make up the Ceph cluster? How many OSDs per node? How many monitors do you have running? At this point, the only thing that can be abstracted from your post is that you have a failed OSD, as the error says "ceph-disk: Error: One or more partitions...

Ok, but was openvswitch so problematic before Systemd? Or are the problems more now that Systemd is involved? I mean, I'm sure it's not for no reason that Devuan exists ...

I removed the openvswitch-switch package with apt-get remove --purge I rebooted the server and networking is coming up fine now ... I'm not using openvswitch right now so I'll leave it uninstalled for now Thank you very much What gave you the clue that that package might be the issue?

Output of Journalctl -alb ---- where the problem starts Aug 24 16:15:02 PMX-72-CN4 systemd-sysv-generator[1003]: Ignoring creation of an alias umountiscsi.service for itself Aug 24 16:15:02 PMX-72-CN4 systemd[1]: Cannot add dependency job for unit display-manager.service, ignoring: Unit...

Any ideas?

Just installed Proxmox VE 4.0 fresh on a Dell R720 dual Octo Core 192GB Memory server with 6 Network Interface cards 2 10Gb Intel, 2 1Gb Intel, and 2 10Gb Broadcom First thing I did was to re-order the NICs via the /etc/udev/rules.d/70-persistent-net.rules file. I then re-applied the Proxmox VE...

Thanks for the explanation. I had already looked up LVM-Thin provisioning before you replied so was at least aware of that. Yes, I know there isn't a filesystem by default ... I guess the biggest problem is that there isn't anything in the Proxmox 4.2 announcement that says LVM-Thin becomes the...

What do you mean by "cannot be mounted directly"? What then becomes the default workable local storage? Also, what exactly is "LVM-Thin" storage? What's it useful for?

This has happened a number of times now. I've used the Proxmox 4.2 ISO to do a fresh server install. After finished I find that /dev/mapper/pve-data has not been formatted nor is in fstab to be mounted. Local storage ends up on the root filesystem which typical is only around 97GB big which...

For anyone that is tracking this as we are, please note this URL here http://osdir.com/ml/general/2015-05/msg26656.html This shows that Debian has known about this for a year at this point and although it's in unstable and testing, unfortunately, it's still not in stable (Jessie) so apparently...

Ok ... thanks again for clarifying ... very much appreciated I looked it up and it seems it's not just in "unstable" but also "testing" a.k.a "Stretch" ... hopefully it won't be too far off and perhaps because it's in Stretch repos it'd be easier for you guys to include? Just thinking out loud...

So, it's IPv6 related within that particular Debian library? Just to be able to understand it ... Thanks Dominik As always, excellent work by the Proxmox staff and developers

I was having 5 to 10 minute delays with the 70-persistent-net.rules file so I consider 30 seconds to bring up the network reasonable (it's a server after all and once it's up stays up in production for very long periods of time). I read up on the .link files and didn't see a means of doing the...