vonProteus
Members
-
Joined
-
I have a problem with rsync. When I run `rsync -azh --partial "$SRC" "$TARGET"` files are transferred. When I try to do it again, the same files are transferred again. when i do on new files i get ```bash stat "$SCR_ONE_FILE" 16777244 1002714 -rw-r--r-- 1 proteus staff 0 8845961 "Dec 22 15:06:26 2024" "Dec 22 10:55:54 2024" "Dec 22 10:55:54 2024" "Dec 22 10:55:54 2024" 4096 17280 0 "$SCR_ONE_FILE" ``` and ```bash stat "$TARGET_ONE_FILE" 922746886 11086197041313146704 -rw-r--r-- 1 proteus staff 0 8845961 "Dec 22 19:09:39 2024" "Dec 22 19:09:40 2024" "Dec 22 19:09:40 2024" "Dec 22 10:55:54 2024" 1024 17278 0 "$TARGET_ONE_FILE" ``` but on old files i get ```bash stat "$SCR_ONE_OLD_FILE" 16777244 81106 -rw-r--r-- 1 proteus staff 0 118819 "Jun 15 19:27:07 2024" "Jul 15 11:53:17 2023" "Jun 15 19:27:07 2024" "Jul 15 11:53:17 2023" 4096 240 0 "$SCR_ONE_OLD_FILE" ``` and ```bash stat "$TARGET_ONE_OLD_FILE" 922746886 11037371857978956400 -rw-r--r-- 1 proteus staff 0 118819 "Jul 15 13:03:03 2023" "Jul 15 11:53:17 2023" "Jul 15 11:53:17 2023" "Jul 15 11:53:17 2023" 1024 234 0 "$TARGET_ONE_OLD_FILE" ``` So, to me, it appears that the second date is different after coping in 6.12.14. A little bit about my setup on Mac I have mounted smb share exposed from vm (Docker + K3S + Debian). In K8s, the volume is backed by an NFS share which is exposed directly from Unraid. This NFS share is exposed from a ZFS pool. Before 6.12.14, I was on 6.12.13, and there was no problem, and everything worked.
-
So my problem was caused by k8s binding ports to ip from virbr0 i change from minikube to k3s and everything seems to work as expected
-
i have vm on unraid i have ASUS RT-AX86U router vm has 2 ip addreses one on br0 and one on virtbr0 i have configured router to forward port to ip from br0 and it don't work when i change configuration of forward to ip of unraid i can perform iperf3 test and it works i test from vps outside my netrork vm is a headless debian system any suggestion or advice will be greatly appreciated
-
i created 3 scripts for this problem one to regenerate shares from zfs #!/bin/bash -e zfs get sharenfs -H -o name,value,source -t filesystem | grep -v off | grep -v "inherited from" | while IFS=$'\n' read LINE; do LINE=($LINE) NAME=${LINE[0]} SHARENFS=${LINE[1]} echo regenerating share $NAME with $SHARENFS zfs set sharenfs=off $NAME zfs set sharenfs=$SHARENFS $NAME done second one to run on every shutdown of array to backup zfs nfs shares to $BACKUPLOCATION #!/bin/bash -e BACKUPLOCATION=/mnt/tank/storage/unraid/zfs-nfs/backup/ rsync --verbose --archive --human-readable --progress --partial --checksum --delete-after /etc/exports.d/ $BACKUPLOCATION and last one to restore backup on every start of array #!/bin/bash -e BACKUPLOCATION=/mnt/tank/storage/unraid/zfs-nfs/backup/ rsync --verbose --archive --human-readable --progress --partial --checksum $BACKUPLOCATION /etc/exports.d exportfs -ra
-
thanks for your help @ghost82 now in vm i have two nic one connected to br0 (with internet) from ip in 192.168.172.0/24 second one connected to virbr0 (with internet) with ip in 192.168.122.0/24 which is good enough for me because nfs server has restriction on ip in other subnet than normal one
-
hi i'm trying to create vm with linux with 2 network interfaces one for normal communication with the world (let's say 192.168.172.0/24) and another to communicate between vm and unraid host only (let's say 10.1.1.0/24) and i don't know how to do it i want something like this because i don't want to give access ip's from my normal network (192.168.172.0/24) to nfs server my vm xml
-
vonProteus changed their profile photo
-
thanks for grate plugin & feature request @steini84 can you add bash-completion support?
