Recent content by Nemo

PVE is 6.1.7 meanwhile, and glusterfs 7.1. We stilll have images showing fresh corruption, but my belief atm is, that they only start to show up whenever one of the zeroed blocks is written to, so they are not really new errors. Atm we're much too busy saving operations to make further tests...

BIOS versions are of 2017 and 2018, five machines, two different sets of hardware. Would be improbable that all show the same symptoms at the same time. But still something to keep in mind.

As an update: We switched off discard on all guests. We could provoke corruption creating machines with discard on, but it became more difficult and rare. So it might be depending on the load, or the number of parrallel vms with discard on. Hard to say. That being said, we started recreating...

I reproduced the issue on glusterfs and local storage with ext4. Nothing in the logs. ~# pveversion -v: Since the issue is also in the customer support (ticket 9253328), it's probably more oeconomic to put it on hold here. Of course I'll follow up if something comes up. For the time being, it...

Hello, We are experiencing massive issues with file corruption on qemu vms. It started about one month ago it seems; it might correspond with our last pve upgrade. The files can be detected via debsums -c on the Debian guests, also qemu-img check <image.qcow2> show massive corruption. On the...

Like I wrote: Not even a full reboot. What helped, however, was (probably) emptying the browser cache. So, cosmetic problem solved. Thanks.

Hm. I updated, have the versions listed. I did a full reboot. The web frontend now shows me "Version undefined" whereas before, it showed "Version 2.1-1/f9b0f63a". Might be just cosmetic.

Thanks a lot! That was quick. (Funny none of these posts showed up when I searched the forum for "cifs mount". You just have to get lucky with your search terms I guess.) Anyway, I'm on my way, thanks again.

It would be nice if you could explain your reasoning behind your selections. Especially for more obscure ones, like virtio/bus types/cache/cpu type etc. Without explanations, I'd prefer reading the manuals; with explanations I could decide if your decision is valid for me too. That could be...

Hello, I have a container based on a debian 6.0.4 template. Both Proxmox VE 2.0 and Debian are updated with apt. Both have cifs and smbclient installed (samba-common, smbfs, cifs-utils). Also, the Proxmox server can mount cifs shares. However, the container gives me: # mount -t cifs -o guest...

So, I have set up Proxmox ve 2.0b. It has a configured interface vmbr0 and is reachable trough that. It also has interfaces venet0 and eth0, which look unconfigured but eth0 seems to work under the bridge. eth0 Link encap:Ethernet HWaddr 00:0a:e4:86:e2:ea inet6 addr...

You are right. Clearing the browser cache did the trick. Thanks and regards, Nemo

I have the same problem: "Not implemented" - window when I try to create CT with Firefox 7.0.1 (Win7 64). Google Chrome works.