Search results

Hello, We backup some folders on our hypervisor by doing a snapshot of the root dataset zfs snapshot rpool/ROOT/pve-1@borgWe could then backup the folder /.zfs/snapshot/borg/ which contained all of our files. The issue is that since version 6.0 this snapshot folder is now empty so I was...

No I'm using ZFS now. Don't get me wrong LVM is great and using thin is perfectly fine but make sure you plan accordingly. It's just that I prefer ZFS

Not since version 6.0. I tried using it with a ZFS local storage and it worked fine. The total "downtime" was 72ms....

I have the feeling this is something related to PHP settings in your nextcloud https://docs.nextcloud.com/server/stable/admin_manual/configuration_files/big_file_upload_configuration.html?highlight=large%20file

I remember having a similar problem before when I was using LVM Thin. The way I fixed it was a last resort. I added a 64GB USB key to the pool just so I can backup the VM (since the hypervisor was not usable before that and I had no disk slot available). Once done the only thing you can do is...

The reverse proxy will act as a sort of gate where all the queries will enter there and be redirected to the appropriate backend server. It means you will only need a single public WAN IP for your proxy and for the backend servers you will use a LAN IP. Way more scalable and easier to manage...

Why not use a reverse proxy instead ? Easier to manage, more scalable and more secure

Thanks Stoiko ! Let me see if I can spin up a test server. Cheers !

Hey Stoiko, just a heads up that ZFS 0.8.2 was released https://github.com/zfsonlinux/zfs/releases/tag/zfs-0.8.2 Cheers !

Awesome thanks Stoiko !

Hello, Would it be possible to include this fix in the pve ZFS package. The bug would cause a hang/deadlock on the hypervisor when using snapshot heavily (especially the rollback) which the only way to fix the zombie processes was to reboot. Thanks

Another vote to deploy it for PVE 5. We have a petty important issue where our hypervisor sometimes lock up because of ZFS and requires a reboot. They added a new config in 0.8 that try to send the hung I/O again (since it's hard to pinpoint what is causing this).See here...

Glad I could help !

Turn out I did ! The issue was something corrupted with iDrac. Factory reset the idrac settings fixed the issue.

I've checked the video but forgot about the release notes. This was not a mission critical system so no biggies.

Well that was fast ! Thanks oguz. I'm assuming in 5.4 it's now checked by default ?

Just upgraded to 5.4 and I can no longuer create a CT. When trying I get the following error: extracting archive '/mnt/pve/nas/template/cache/ubuntu-18.04-lts_18.04-1_amd64.tar.gz' tar: ./var/spool/postfix/dev/random: Cannot mknod: Operation not permitted tar: ./var/spool/postfix/dev/urandom...

hey Stoiko, Even after disable the swap, the issue is still present. root 6073 0.0 0.0 7060 760 pts/10 D+ 09:04 0:00 | \_ sync [<0>] wb_wait_for_completion+0x64/0x90 [<0>] sync_inodes_sb+0xa6/0x280 [<0>] sync_inodes_one_sb+0x15/0x20 [<0>]...

I will disable the swap-zvol and get the latest kernel. Will report back if it happens again. Thanks for the help Stoiko

I do. I thought Proxmox set one by default during the installation ? rpool/swap 8.50G 1004G 869M - Filename Type Size Used Priority /dev/zd32 partition 8388604 0 -2 When testing. I could crash the whole...