Recent content by cluck

Indeed I was considering the fact that some storage types are not as suitable as others. I was also thinking of not proposing a change which would surprisingly change behavior for other People. That's why I am proposing to introduce both a setting on the storage and on the backup job, both...

Backup fleecing is a good thing. But I'm a bit puzzled by the need to choose a fleecing storage in the backup job: I wonder if I'm the only one missing the option to configure fleecing to stick to the same storage the source is in, whatever that is. I am thinking of having two options: the...

Ich habe gerade den selber Fehler, und gleiche Voraussetzung: in meinem Server sind Festplatten dazu gekommen, die vorher in einem anderen Server Dienst taten. Die VGs auf beiden Server hiessen gleich (gleicher vg_name "pve", unterschiedliche vg_uuid): root@pbs:/# lvs -o+vg_uuid WARNING: VG...

Now that I walked into it, I have reported it in Bugzilla. I previously ended up reporting it here because I sloppily googled for "how to report bug proxmox", which led to the getting help for Proxmox page, which refers to this forum.

My corosync is working properly. I haven't posted my corosync.conf because I think I see a parser bug that is independent of the config file in /usr/share/perl5/PVE/Corosync.pm (approx line 92). The parser is just a tad too simplistic and fails to parse valid corosync.conf files when they...

# pvecm status missing ':' after key '2' Can't use an undefined value as a HASH reference at /usr/share/perl5/PVE/CLI/pvecm.pm line 486, <DATA> line 960. This is while corosync is happily running, `corosync-cfgtool -n` shows running links etc.. Looks to me like pvecm is choking on the...