Search results

Not sure if it is a typo but you're missing the "-s" parameter ? https://gitlab.com/6uellerBpanda/check_pve#smart

it's an interesting question... KSM only works with anonymous page cache which isn't the same as ARC which operates on file basis - see here https://www.kernel.org/doc/html/latest/admin-guide/mm/ksm.html to be honest I don't use ZFS with proxmox but I use it with freenas and used it with...

yes you're boot_command is a little bit different then mine: "boot_command": [ "<esc><wait>", "install <wait>", "preseed/url=http://{{ .HTTPIP }}:{{ .HTTPPort }}/{{ user `preseed` }} <wait>" ... but strange it's working for some and some not...

did you try increasing boot_wait option ?

hmm...so just to be clear: packer creates the vm on pve node starts the vm but at the boot screen you see the boot selection menu and not the debian installer ?

can you provide the packer config ?

it depends if you use async for NFS then you might get an filesystem/io error for the vm's and need to repair it with fsck at the next boot if it is recoverable - depending when dirty flush happens. with sync param you might (flush) also get io errors but filesystem will be fine at next boot...

a small update and the solution: a few weeks ago we upgraded freenas but it was still mounting with the wrong ip/interface. today we updated proxmox to 6.4-13 with 5.4.151-1 kernel and that solved the problem without any further adjustment. so I guess at the end in what was a kernel bug but...

on pve 6.4 with ansible 2.7 it's working out of the box...also with command module ansible -b -D --ask-vault-pass -vvv -m shell -a "qm resize 102 scsi0 5G" HOST HOST | CHANGED | rc=0 >> Size of logical volume elastic/vm-102-disk-0 changed from 4.00 GiB (1024 extents) to 5.00 GiB (1280...

ok I'm asking 'cause I also had problems with lxc, though not with this pve version, which also had somehow the same symptoms you're describing and the problem was the tcp window became full after some seconds even with a simple apt update and then traffic stalled.

ahhh...so this VM is a lxc and not kvm you mean ?

how does it look on netapp or switch side ? would it be possible to share the tcpdump from both sides ? is it happening when you transfer files to the nfs share or also in an idle state ?

anything in the logs ? traffic disrupted from the vm to the mounted nfs share or inside the vm itself or both ?

can you show output of mount | grep sto0 did you try any iperf test ? is it only slow from inside the VM or also from the pve host ? anything noteworthy in dmesg, syslog,etc... on pve host and sto01 ?

the fio tests are in chapter 4 and also check zvol options in chapter 6

may I ask you to provide a fio test - look here for how to do it - https://www.proxmox.com/de/downloads/item/proxmox-ve-zfs-benchmark-2020 (especially disable arc/primary cache before running test). then we've some hard values to compare :) is there anything noticable in dmesg or messages and...

ah yes the diag makes it easier now. thanks. my first thought was that's not possible with only one bridge 'cause how should the bridge handle untagged traffic from net0, net2, net3 and you want to distinguish it to vlan 2010, 2015, 2016 - the vlan tag in the frame is missing. but I'm also not...

so just to be clear the tests/fio command and setup between the 400k iops and the 170k iops are exactly the same except one with ext4? and the other with zfs ? is there any specific reason why you've --numjobs=256 configured ? seems rather high to me though not wrong :) there is also an...

may I ask you to add fast and dirty network diagram 'cause only reading your description makes it really difficult to get an overview of it. also pl show output of /etc/network/interfaces

may I ask you to provide following output: zpool status, zfs get all iotest, arc_summary