Search results

I don't understand why Proxmox indicates that my SSD which I basically only used for the Proxmox OS and application (PVE) itself and not for e.g. storage of ISO, VM's or data is for 98% in use. It's a 1 TB SSD NVM disk. On the local (LVM) only two machines are stored of respectively 32 GB and 16...

Saw more NFS issues related to the upgrade to PVE 6.2.4.. But no conclusive answer or solution. What’s the status on this?

Confirmed here when upgrading from to one version ealier to 6.2-4. Strange thing is that one of my NFS shares shared on Proxmox still works and the other one not.

Very strange I had two perfect working ZFS datasets shared through NFS and one of the two suddenly says when mounting from Ubuntu Desktop 'operations permitted for root only'. ZFS properties are set the same for both datasets, except the dataset not available through NFS is an encrypted dataset...

As far as I understand if the container needs network file sharing capabilies you will need a privileged container. Regarding OMV I have not tested it, probably will in the future. There are other open source NAS solutions besides OMV as well, e.g.: - Amahi - Rockstor - FreeNAS (OMV is the Linux...

I use ZFS for my data disks on the proxmox host itself. ZFS has some SMB and NFS sharing facilities build in. I would not proceed with webmin. For now I don't need OMV, managing shares on the host itself manual is also fine. In case I want some automation in managing the shares I would install...

Does the backup solution only aim for virtual machine/ container related stuff or also for other data on your ZFS?

/zpool/edata/exproxmox/ contains directories 'dump' and 'template'. What would be the alternative opposite for mixing storages? I thought about the following but than still you have the same potential issue: - Current situation: Dataset: zpool/edata/ Dataset: zpool/edata/eproxmox (added to PVE...

UPDATE: - I tried 'zpool export zpool' - Removed the directory /zpool with 'rm -r /zpool - Rebooted, result same problem. Directory created again, but datasets remain unmounted. - Can the issue be my template directories as shown above? That somehow PVE creates these directory quicker on boot...

The default suggest by gdisk is 8300 linux filessystem so I use this. So I understand that should do as log and cache.

Now I am completely lost. I had my ZFS pool nicely working and configured as I wanted to and now there is suddenly an error 'mount is not empty'. My setup is as follow: - I have a raid-1 pool of 2 devices, which is called zpool. - I have one dataset called 'data' with a sub dataset in it called...

I am trying to create a zfs log and cache with gdisk but I am stuck with two things. But I need confirmation about my 'procedure' and I am stuck at choosing the filesystem? Your instruction says: "Add cache and log to an existing pool If you have a pool without cache and log. First partition the...

Meanwhile figured out that a container should run in privileged mode to enable NFS and CIFS options for it. But is seems you have to label a container as 'privileged' during initial build, at least I am not able to change it afterwords via het web interface Although in the end I want to get NFS...

mount -a gives: mount.nfs: Operations not permitted The client is an Ubuntu 18.04 server container. I know I can work with a local bind mount in this case for the container, but in the end NFS should work as well for VM's. Or can the issue be specifically related to the use of a container? Or...

findmnt /zpool/data gives: /zpool/data zpool/data zfs rw,xattr,noacl findmnt /mnt/zfs-data, gives: nothing I alway reboot the system after adjusting /etc/fstab, so that's should be fine.

Many thanks Fabian, I learned a lot about ZFS recently. Pretty cool stuff. Next step is the integrated NFS and SAMBA sharing build in with ZFS instead of separate NFS/ SAMBA. I assume the ZFS integrated file sharing options can be applied to datasets as well as folders? I only find Solaris...

I have succesfully created a dataset and a subdataset, i.e.: - zpool/data/ - zpool/data/proxmox But have a question whether the following I did works ok for ZFS: 1) I added zpool/data/proxmox as ZFS storage type in proxmox 2) But I also added it's mount path /zpool/data/proxmox as directory...

Great understand! Does it also mean that I don't have to encrypt the sub dataset separately. Is it encrypted by it's parent dataset, i.e. in my case /edata/ ?

I have created two datasets, one 'edata' (for encrypted data) and one 'edata-proxmox' (intended for vm images, containers, and disks) due to the notes above given regarding zvol blockdevices, but from a dataset creation point of view on the host there is nothing different between the two...

Thanks Fabian. Just rebooted and checked the properties: keystatus (unavailable), mountpoint (/zpool/edata), mounted (no). So after reboot I issued the following commands in order to issue the mount and to load the keys: 1) Load keys: zfs load-key zpool/edata 2) Mount: zfs mount zpool/edata...