Search results

I missed the reply, but.. I was indeed pinpointing the issue that could happen without the stretch mode enabled, as it was suggested as a workaround.. But yeah.

ah, just read @ https://docs.ceph.com/en/latest/rados/operations/stretch-mode/#individual-stretch-pools that netsplit cause IO block with individual stretch pool, so, not exactly the good usecase..

Hi, Has anyone experimented with ceph stretch pools that seem to have appeared in squid? (not stretched clusters) It seems rather new, but rather interesting, as it may not require the whole cluster to be set to stretched, while still dealing with the guarantee of OSDs and monitors being on...

Hmm.. what would your pools settings be then? 4/2 for the stretched one? Problem would be that you might end up with only one replica at the other DC there (so IO block until recovery?), unless you actually set it down to 4/1... Also, I may be wrong, but in that scenario, you could have...

I guess you have enough RAM on the host to fulfill that RAM need? And that virtio_balloon is loaded on TrueNAS? (lsmod | grep virtio_balloon) Also, I'd give the VM a bit of swap, in case balloon deflation doesn't happen fast enough for process to get enough RAM... The "precise" number of 8G...

The linked articles suggests using zfs import as readonly to work around the bug/issue, maybe that can save you… It's a bit too precise / specific from this point for me to help you further…

Well, technically, it's a LV, yes, but it's not directly a mountable partition, it's a raw device, that has its own partition table and all (unless you used it directly as a filesystem, without a label nor a partition there…). So you *could* mount it, but it's not that simple. Also, it's...

Is there anything classy you guys don't do hahah! That is impressive, I think one of you mentioned it @ FOSDEM now that I think of it..

Do you see the disk as having the good size in Proxmox GUI? (or using pvesm list VM-Import | grep ' 105$' ), What does the subvolume tell you, from the host? (zfs list testzfs/subvol-105-disk-0) It's indeed not normal for the container to not have been resized by the GUI process, it might be a...

Setup a VM with a live ISO to boot and inspect all disks, and if it's the same OS as your VM, you can even install grub from there. Say it's Ubuntu, boot it (or boot it live using netboot.xyz for even more fun! ;)), then check what lsblk has to say, then try mounting partitions in /mnt to find...

It's a good suggestion, maybe open a feature request on bugzilla?

Hi, @paulsk answered that nicely, I'd say! If you have further needs in term of load balancing, and don't want to wait for the upcoming CRS evolution, there is a nice tool that can help you load balance using live metrics: ProxLB ! As for the high CPU usage, I assume you have a lot of VMs /...

Hi, I don't speak Italian, but I'll take a guess… and answer in English. PBS is quite unique, and provide a full feature backup solution for your Proxmox Cluster. Developing and maintaining it so that it stays relevant and that feature full cost a lot more than for PVE, I guess. Also you...

Hi, This probably means your ZFS storage is corrupted… Or you hit a bug in zfs, or both. That issue was mentioned on Github. And the last comment points to a way to recover the data, but for a truenas scale install, not proxmox. However, I'm guessing it could be useful, or even work in your case.

Hi, try to get an idea of what is causing the IO delay? iostat or atop should at least tell you which devices are in troubles, and what processes are impacted (though… it's probably VMs ;)) If you have another monitoring tool up, try to get insight there… And you can also use SMART to get some...

I don't know of any existing script, I'm usually assuming that if I lose a host, I'll just install a new one, and bring it in as a fresh one.. But your list seems nice… Maybe things in /var especially if you care about stats and logs. And root's SSH key if you don't want to deploy a new one…...

OK. It is rather unclear what you want. I'm guessing.. you want to resize the ZFS storage used for all your containers, right? The zfspool called VM-Import? If so, you need to have space available on the underlying device… Or is it the container volume itself?

I'm not sure what you're trying to do now.. So your first screenshot was inside the container, not on PVE right? So … can you do findmnt / inside the same container? Also, could you show us that container configuration (pct config 105 most likely), and especially the rootfs property? And…...

Haha, the workaround is actually clever!! vzdump (the command) doesn't have such a feature, probably because all the logic for that is hold in Qemu Server. The way it seems to be set is getting the list of volumes, and decide based on their properties or specific setting (backup=0/1), add them...

As a general note, I'm not sure why you're using the 169.254/16 IPs, why not using another range from RFC1918 there? and if it's for direct communication, surely something smaller than a /16 (or even a /24) would work… Which leads to my other point, why bother? Either it's full mesh, either it...