Search results

Does it really? I found this: https://github.com/openzfs/zfs/discussions/12769 The metadata does, but not the blocks with the actual content.

Firstly, sorry about resurrecting this old thread. Does the special_small_blocks apply to zvols? I thought it only applied to datasets.

I see now. It refers to PVE and PBS running side-by-side on the same installation of Debian. You definitely don't need to upgrade a separate machine running PBS 2.4 to 3 before upgrading PVE 7 to 8.

Thank you for clearing things up. I still have a question: what does the line "Co-installed Proxmox Backup Server: see the Proxmox Backup Server 2 to 3 upgrade how-to" mean in the prerequisites section of the PVE 7-to-8 guide? At first glance it sounds like PBS needs to be upgraded to v3 before...

This thread needs to be resurrected now that we have PVE8 and PBS3. So what does the compatibility matrix look like currently?

That's because I didn't create the first partition (BIOS boot). How do you create a partition before sector 2048? Neither fdisk nor gdisk will let me. But the good news is it worked even without the first partition. There was a warning but every step proceeded fine. The only other warning I...

@Stoiko Ivanov Thank you for the advice. I am still trying out all the steps in a virtual machine. When adding the new partition to the pool, zpool complains like this: root@pvetest:~# zpool attach rpool /dev/sda3 /dev/sdb2 cannot attach /dev/sdb2 to /dev/sda3: no such device in pool I ended...

@leesteken Thank you for the advice. I'll try all the steps in a VM. However, I can't seem to find older ISO installers than 6.4 on the website. On this page it says I need an installation between 5.4 and 6.3. Does anyone know if there are at least some checksums from an official source, so I...

I need some help replacing a couple of smaller drives with another couple of bigger ones, while maintaining the same ZFS filesystem but enlarging the pool and also switching to EFI boot. This is on PVE 6.4 in preparation for upgrading to 7. This is what /dev/sda and /dev/sdb look like right...

I can confirm accessing the web interface without going through a proxy does solve the automatic logout problem. Thank you for all the support, I would not have guessed that the proxy was the culprit. Will mark thread as solved.

proxmox-ve: 7.1-1 (running kernel: 5.13.19-4-pve) pve-manager: 7.1-10 (running version: 7.1-10/6ddebafe) pve-kernel-helper: 7.1-12 pve-kernel-5.13: 7.1-7 pve-kernel-5.13.19-4-pve: 5.13.19-9 pve-kernel-5.13.19-2-pve: 5.13.19-4 ceph-fuse: 15.2.15-pve1 corosync: 3.1.5-pve2 criu: 3.15-1+pve-1...

I have tried the current Firefox version of 97.0.2 and Chrome on Windows and also Firefox on Linux. All showing the same behavior. In a Private Window, the console doesn't show that error, but it still locks me out while I'm using the interface.

I've installed the latest Proxmox VE on a new machine and the web interface keeps kicking me out. It's not the inactivity timeout, because it kicks me out even when I click something different every 3 seconds. I've looked at this problem reported in the past and most times it's been clock/time...

It worked! Thank you Fabian_E! Marking the thread as solved and posting here the outcome so it may be useful to someone looking to do the same thing. The only "problem" I encountered was that the zfs send command would not run because the dataset was mounted (even if the container was not...

Thank you Fabian_E for the information. All storages are ZFS pools. I was thinking of trying to do zfs send | zfs recv with that dataset like this: root@node1:/# zfs send pool1/subvol-ID-disk-0 | ssh node2 zfs recv pool2/subvol-ID-disk-0 Do you think this would work?

So here's the setup in a nutshell: two nodes: node1, node2 in a cluster cluster is healthy and running the latest version of PVE, all updates applied node1 storages: local, local-zfs, pool1 node2 storages: local, local-zfs, pool2 The question is: how do I move a container that runs on node1...

I think I've not explained well what I'm trying to do. The machine has a separate pool from RPOOL that's filled with data in a container. In order to add that machine to a cluster it needs to have no VMs. Since I don't have the space to move that data elsewhere, I was wondering if I could...

Is it possible to disconnect a zfs-based storage from a Proxmox machine that has containers on it and then reconnect it and restore the containers from it? I need to add the machine in question to a cluster and don't have the space to back up those containers. So I was thinking if I could...

The installer creates a third small partition at the end of the drive(s) on ZFS installs. It appears it is unused. I wonder if it can be repurposed as swap partition.

Doesn't your server have an optical drive?