Thank you for your reply. I have been a long term Proxmox container user since OpenVZ so I know what containers are :)
I am trying to switch from LVM thin volumes to ZFS. Right now LVM thin volumes are perfect for me but they require hardware raid and I would like to start setting up servers...
Currently, I am using hardware raid with LVM thin volumes and LXC container which works great but I am trying to switch to ZFS.
Is it possible to hide the mount points when using ZFS? Here is what I got on my host system:
zfs list
NAME USED AVAIL REFER...
here is what worked for me
pct restore 130 my_pbs_server:backup/ct/130/2023-02-11T04:20:52Z --storage data --rootfs data:10,mountoptions=noatime,quota=0
is there a reason why the output is different for these 2 command below? letters are all caps when openssl is used.
proxmox-backup-manager cert info | grep Fingerprint | awk '{print $3}'
openssl x509 -in /etc/proxmox-backup/proxy.pem -fingerprint -noout -sha256 | awk '{print $2}' | cut -f2 -d '='
My PBS server gets a new certificate every 3 months so I have to manually get the new fingerprint from the server and then import it to the PVE servers. My idea is to automate this process with Ansible. First step is to get the fingerprint from cli. This is my idea:
proxmox-backup-manager cert...
https://forum.proxmox.com/threads/container-messed-up-after-changing-unpivileged-attribute-outside-the-gui.88400/post-387318
I think this solves, I will try.
I mounted the CT on the host like this
mount /dev/mapper/pve-vm--103--disk--0 /mnt/103/
and modified some files
after I unmounted and started the container. Now I can not change the files that were modified outside the container.
I am getting this error when initializing a disk
Disk sdc - Initialize Disk with GPT
2020-11-23T02:47:03+01:00: initialize disk sdc
2020-11-23T02:47:03+01:00: TASK ERROR: command "sgdisk" "/dev/sdc" "-U" "R" failed - status code: 2 - Caution: invalid main GPT header, but valid backup...
I have fixed this by just adding the name of the datastore and mot the mount path. So instead of /mnt/datastore/sdb_mirror_datastore just used sdb_mirror_datastore
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.