Search results

Hey, I recently add a FreeNAS storage to my cluster (3 Nodes, newest 4.2, full updated) and connected the nodes via iSCSI to it. Now I have tons of that error messages: Read Capacity(16) failed: Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE I have seen, that other users have those errors...

I have the same issue, the same message. Have you found a solution for it?

Hi, I recently got a lot of 10k SAS disk. One of my cluster nodes (3 node cluster 4.2) uses SSD as a mirror. For me somehow waste of resources. So my idea is to change that raid1 to raid10 (node has 4 slots). Can I manage it somehow with zfs tools or is it safer ans easier to just remove that...

Neither nor... all 3 hosts are connected via fibre channel.

I use Open-E DSS6, and no I don't use a clustered LVM.

Hi, I have to solve that problem: https://forum.proxmox.com/threads/all-vms-stuck-after-restore-other-vm-over-fc-storage.27430/#post-138025 Is it possible to pay for support without taking a subscription? Thanks

Well I have to run a filesystemcheck on the VMs otherwise they can't start. But I need a solution for prevent the VMs of blocking during/after a restore.

Hey Guys, I have a really stupid issue, I hope you can help me. My setup: I have 3 proxmox hosts (all 4.1) they use a shared storage connected over FC, backup is made to another NFS storage. All VMs running like a charm except I have to restore a VM. In that case the other VM's get errors...

Well I installed that 2 patches on my 3 hosts, since that day I can run backups on nfs storage like a charm. BUT already a third time it happens that 1 host cant quit processes and start more and more until it stuck. I can't stop container or migrate them, just got a timeout. I even can't...

...please have a look at our problems with backup of lxc containers. In that thread you will find all necessary information: https://forum.proxmox.com/threads/lxc-backup-randomly-hangs-at-suspend.25345/ Please give us some feedback, we count on you. Thanks Steve

So in the end I can choose between 3 things: 1) No Backups 2) Backup mode "stop" with the risk of not starting VM's 3) Backup mode "suspend" with the risk of no backup I feel like in "Herzblatt"...

I tried this too, but I had once the situation that vzdump didn't start the lxc after it backuped it.

Hmm...to be honest, I am confused ;-) Can you explain it different?

I have exactly the same problem. My workaround, until Proxmox team can fix this, was to schedule every single CT in a single backup job, in 15min steps. But tomorrow after I checked backup logs my plan was destroyed. The very first backup job stuck at "suspend vm", and of course the other jobs...

Ah is it possible that ionice only influence backup but not restoring?

Great, workes like a charm!! The Proxmox guys should include that to their zfs troubleshooting wiki.

mount | grep tmp: udev on /dev type devtmpfs (rw,relatime,size=10240k,nr_inodes=2049440,mode=755) tmpfs on /run type tmpfs (rw,nosuid,relatime,size=3284760k,mode=755) tmpfs on /dev/shm type tmpfs (rw,nosuid,nodev) tmpfs on /run/lock type tmpfs (rw,nosuid,nodev,noexec,relatime,size=5120k) tmpfs...

Well I can't change it, but a second NFS storage with FreeNAS works quite fine.

its the default folder from root. I just set the vzdump.conf to use /tmp, but even when I comment it out, it produces the same error messages...

If I want to make a backup from my LXC container on local storage I got this error message: INFO: starting new backup job: vzdump 118 --compress lzo --node vmbase3 --remove 0 --mode snapshot --storage local INFO: Starting Backup of VM 118 (lxc) INFO: status = running INFO: mode failure - some...