skraw's latest activity
-
Sskraw reacted to meyergru's post in the thread Problem with rsync mtime preservation since update to kernel 6.17.13-6-pve (solved by avoidance of nfs 4.2) with
Like.
Me too, similar situation: an "rsync -a" syncs the timestamps of the original files first and after a short while the mtime of the file switches to the time of copy. Falling back to NFS version 4.1 on the mount fixes the problem. -
Sskraw reacted to EAnushan's post in the thread Problem with rsync mtime preservation since update to kernel 6.17.13-6-pve (solved by avoidance of nfs 4.2) with Like.
I can confirm I'm running into the same bug. root@proxmox:~# pveversion pve-manager/9.2.4/5e5ae681198514d4 (running kernel: 7.0.14-4-pve) I was using rclone to sync some files to an NFS share hosted on my Proxmox node. After a sync, running a...
-
Sskraw reacted to raipvs's post in the thread Problem with rsync mtime preservation since update to kernel 6.17.13-6-pve (solved by avoidance of nfs 4.2) with Like.
I have the same problem on Proxmox 9.2.4 with kernel 7.0.14-3-pve as NFS-Server and NFS-clients running 7.x kernels. A workarround for me is to mount the filesystem with NFS version 4.1: mount -o vers=4.1 SERVER:/DIR /mnt I guess it is a kernel bug.
-
Sskraw replied to the thread Problem with rsync mtime preservation since update to kernel 6.17.13-6-pve (solved by avoidance of nfs 4.2).Many thanks for commenting on this! Until now there was a chance I did something wrong and hadn't found it yet. But if you experience the same problem, there maybe really is a problem. I will check out with vers=4.1 and come back with a result...
-
Sskraw replied to the thread Problem with zfs and setfattr.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...
-
Sskraw replied to the thread Problem with zfs and setfattr.Ok, I did not think about that so far, is it possible that the problem is related to apparmor on proxmox?
-
Sskraw replied to the thread Question regarding memory hotplug and numa.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...
-
Sskraw posted the thread Question regarding memory hotplug and numa in Proxmox VE: Installation and configuration.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...
-
Sskraw replied to the thread Problem with rsync mtime preservation since update to kernel 6.17.13-6-pve (solved by avoidance of nfs 4.2).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?
-
Sskraw replied to the thread Problem with zfs and setfattr.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...
-
Sskraw replied to the thread Problem with zfs and setfattr.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...
-
Sskraw posted the thread Problem with zfs and setfattr in Proxmox VE: Installation and configuration.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?
-
Sskraw replied to the thread shrinking qcow2 image virtual size.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...
-
Sskraw replied to the thread shrinking qcow2 image virtual size.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?
-
Sskraw posted the thread shrinking qcow2 image virtual size in Proxmox VE: Installation and configuration.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...
-
Sskraw replied to the thread Problem with rsync mtime preservation since update to kernel 6.17.13-6-pve (solved by avoidance of nfs 4.2).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...
-
Sskraw replied to the thread Problem with rsync mtime preservation since update to kernel 6.17.13-6-pve (solved by avoidance of nfs 4.2).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...
-
Sskraw posted the thread Problem with rsync mtime preservation since update to kernel 6.17.13-6-pve (solved by avoidance of nfs 4.2) in Proxmox VE: Installation and configuration.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...