Recent content by skraw

Hm, does not sound like you understood the problem setup. Maybe I did not explain well. I have a VM backup guest. This is the destination for numerous rsync backups from _elsewhere_. The advantage in using rsync is exactly to be able to access all files in the backups as single files, e.g. for...

Ok, I did not think about that so far, is it possible that the problem is related to apparmor on proxmox?

Hi Jonas, thanks for your comment and the referenced articles. From reading them and personal experience I'd say this topic needs qualified re-programming in proxmox. To me it seems obvious that hotplugging is a key-feature in virtualised environments. It should be very simple to add or remove...

Hello, recently I had some troubles with client vms that needed a lot more memory than expected. This brought up the idea to switch on memory hotplug for such vms. So I enabled numa and mem hotplug and tried to give the vm a bit more memory from the start. I though 128GiB are ok, so I entered...

And now the problem came back, again for no obvious reason. rsync on nfs-mounted zfs and the mtime is set to current time, which it is not if I do the same rsync on a local drive with ext4. Any ideas?

First of all let me say thank you for the time you take to answer in this thread. Unfortunately this does not quite make it to a point where I want to go. Since the backup host is exactly the same as it was when using a local ext4 drive. So I would think that there must be some way to let it do...

Well, in fact I am coming from another side to this problem. I take backup by rsync from a lot of hosts. when the backup drive was built into the backup server (with ext4 fs) everything went without problems. Now I virtualised the backup server and replaced this drive with an nfs-mounted zfs...

Hello, I just came across a problem with zfs handling of xattrs. My zfs has xattr=sa and is mounted with xattr. But using setfattr on a file results in "operation not supported". Why is this?

Ok, i found another thread with quite the same problem showing up: https://forum.proxmox.com/threads/trying-to-shrink-qcow2-image-to-make-space-for-another-one-on-the-proxmox-host-image-gets-corrupted-after-resize.119920/ Only he tries to enlarge the disk. With the hints he gave I found that...

sometimes the real problem hides behind a simple question. In the meantime I found out that qemu-img resize does not work but shoots the disk resized, no matter how few bytes you shrink it. How about that?

Hello all, I have to move around some physical boxes and virtualise them later on. So I came across this question about qcow2 images and cannot find a conveniant solution for it. Lets assume having a qcow2 disk image with a big virtual size and a relatively small partition size inside. How can...

Now, I investigated the problem further and got the impression that the kernel on client and server side must have some influence. The problem arose after a proxmox kernel update. My client kernel with problems was 6.12.something. I had another box that nfs-mounted another zfs volume from the...

Ok, to make the story a bit simpler. You are right, the problem turns around mtime. But you seem wrong about the rest. If I do an "ls -l"' on the source dir of the rsync I see some dates/times for every file. These are of course mtimes. If I do the rsync as stated (-avxAHX) I see (before last...

Hello, it seems I see a problem with my proxmox based nfs server (on host) on a zfs volume in conjunction with a nfs-client using rsync. Once a month I copy some files with rsync -avxAHX from some place to a nfs-mounted fs coming from a proxmox nfs-server exporting a zfs volume. This has never...

No, I don't have a fine-grained monitoring, and really, this is not exactly the point. I am very sure that all your working nodes are built on an empty network, just like the proxmox doc for corosync says. The thing is this: if I have even an 5-min-average throughput of about 400 MBit, a GBit...