Search results

Hi, currently migrating a local testing server from PVE7 (LVM) to PVE8 ZFS. We have: a new 2TB NVMe disk (blank) 3x1Tb NVMe disks (data including hybrid raid on one partition and PVE vgroup) 1x1Tb SSD disk (data, same as above) Additional HDDs for backup My objective is to create one or two...

I am buiding my first PVE with ZFS with a somehow personalised structure and would like to be sure about the ZFS flags recommended for each type of data. I am particularly concerned about: atime relatime dnodesize overlay In this thread you mention this I guess as correct as far as relatime...

Yes, done that already, but I'm assuming they will not take any notice (is OVH!) Tried the ISO rescue option too, but did not seem to take me to a rescue console and tried to boot directly. I guess I will have to try with a rescue ISO that supports... ZFS, LVM and Linux Raid in our case to test...

Ok just testing the rescue console in OVH I find another reason to perhaps avoid ISO installation or at least maintaining /root in ZFS... Learning my way around ZFS I understand I would need to import my pools and mount them on my rescue console to access those files in case of a major issue...

Thanks. I've tried the ISO install and had some issues with the network configuration. Solved them by changing the bridge-ports of net config to eno1 But I am not sure how safe this is with OVHs rescue options. The iso install created this: Number Start (sector) End (sector) Size...

Thanks. We tend to change server every two years, so I would rather control a quicker installation method also in the case we ever needed a quick server reinstall. How does the ISO partition disks? I mean... is /boot and / (root) running under a zpool? swap?

I am currently at exactly the same point with a new server on OVH. I was expecting OVHs template for PVE8 to be updated for a full ZFS support as official ISO but just noticed is still as usual with md raid + lvm. I have so far tried this conf on installation with what seems a correct boot...

Just found some updated threads regarding virtiofs (https://forum.proxmox.com/threads/virtiofs-support.77889/page-2) and @Drallas guide (https://gist.github.com/Drallas/7e4a6f6f36610eeb0bbb5d011c8ca0be). Did I read somewhere that virtiofs support is expected to be included in PVE UI?

Wondering if there has been any change in this or what is the current best recommend solution to efficiently bind certain host directory or partition to a KVM. Is NFS or similar network filesystem the only supported option?

Thanks, but any documentation for that? Do i understand that is a general script that gets executed for every scheduled backup or do I need to identify a job ID there?

How about "pre" scripts. I was hoping to be able to do some preparation of data for backups before executing it. I've seen some feature requests for pre and post backup scripts but understand they are not being considered. I am guessing I would have do them as my own script and cron on the host...

Answering my on question (sort of!) the issue got solved partially at least but not sure how. Maybe rechecking the flags of the "clone" partitions on gdisk or after a reboot, suddenly allowed us to correctly use proxmox-boot-tool init and now the 3 partitions are correctly been updating when...

Some additional clarifications to my previous question, which we still can't figure out. pve-manager/7.4-17/513c62be (running kernel: 5.15.143-1-pve) this is not a ZFS system as it was upgraded from previous installations, I guess will have to move to ZFS on next upgrade I've checked the...

Hi, we are having issues with a local server running various NVMe drives and SSDs. The UEFI boot partitions were installed originally to the SSD drives that have been superseeded now by NVMe disks. We just realised that removing the SSD drive leaves the system unbootable as booting from any of...

We use this command on a cron on the host to monitor the total real used space on the thin-pools pvesm status |grep lvmthin | awk ' $7 >=70 {print $1,$7}' Values over (>=70) are returned, "lvmthin" is the "type" reported by the command

We are trying to optimize a KVM qm VM by using two assigned thin provisioned disks, one of which we'll not be included in the regular backups so we can speed them up and reduce required space. For this to work we need the KVM to either be able to boot without it, as when we restore the backup...

Noted then, thank you. From my point of view, considering the way ACL is built... root should have access to all namespaces. Not being the case I would suggest at least a feature to allow to "duplicate" an already defined storage so one can just add one per each namespace you want to have...

Yes I assummed that "root" access to a storage implies inheriting all the bellow namespaces. Is this not the case? Is it configurable on the connection, ACL or storage definition? Thanks.

Hi. New to PBS we are trying to configure a server that syncs backups from two others and retains them for long term. We have created two namespaces as production and staging on that server named "pve-archive" which is syncing correctly. We would now like to be able to access from one of those...

Rootless docker causes us an additional limitation regarding having a full firewall working as we wanted. The docker0 network becomes unavailable to root, so we've stopped testing it under unprivileged LXC for the moment, so can not provide any other info, sorry.