Search results

My backups failed after moving them to a different directory on a zfspool. Here's what my config looks like, any ideas? () INFO: starting new backup job: vzdump 400 600 900 --quiet 1 --mailto jsalas424@gmail.com --compress zstd --mailnotification failure --mode snapshot --storage...

Yes I did include RAM. That was also my suspicion, thanks for confirming!

Hi, can someone please explain why the output of these two commands suggests that my snapshots are different sizes? My "VM State Storage" is set to a different disk than where my VMs are running from. For example, the snapshot for disk 201 shows up at 2.57G in one output but 5.87M in another...

It was the spaces in the "Adding gmail compatibility" section :cool: - problem solved!

All of my networking works fine other than this. root@TracheServ:~# ping google.com PING google.com (172.217.12.206) 56(84) bytes of data. 64 bytes from lga25s63-in-f14.1e100.net (172.217.12.206): icmp_seq=1 ttl=117 time=16.9 ms 64 bytes from lga25s63-in-f14.1e100.net (172.217.12.206)...

Another user helped me get the zfs-mount service back up and running: https://forum.proxmox.com/threads/zfs-mount-service-failed-after-latest-update-how-do-i-fix.79774/#post-353179 When I tried to create a directory mounted on /Nextcloud.Storage, it created a dump, images, private, snippets...

I followed the steps outlined here: https://www.reddit.com/r/homelab/comments/5nzmm3/setting_up_the_proxmox_email_alerts/ and these https://forum.proxmox.com/threads/proxmox-setup-for-gmail.13405/ to no avail I got a 2FA password from google as well and that is included here, but don't worry...

If I'm reading this correctly, it does reflect the used storage appropriately, so I guess we're fine? root@TracheServ:~# zfs get all Nextcloud.Storage NAME PROPERTY VALUE SOURCE Nextcloud.Storage type filesystem -...

So why does my Nextcloud.Storage now look so small? Nextcloud.Storage 960G 105G 855G 11% /Nextcloud.Storage

root@TracheServ:~# mount -a root@TracheServ:~# mount sysfs on /sys type sysfs (rw,nosuid,nodev,noexec,relatime) proc on /proc type proc (rw,relatime) udev on /dev type devtmpfs (rw,nosuid,relatime,size=24624548k,nr_inodes=6156137,mode=755) devpts on /dev/pts type devpts...

You're an MVP root@TracheServ:~# ls /Nextcloud.Storage dump images private snippets template root@TracheServ:~# rm -r /Nextcloud.Storage/dump root@TracheServ:~# rm -r /Nextcloud.Storage/images root@TracheServ:~# rm -r /Nextcloud.Storage/private root@TracheServ:~# rm -r...

Actually there seems to plenty of stuff in the .. sub-directory, not sure how to safely proceed now: root@TracheServ:~# ls /Nextcloud.Storage/.. bin dev home lib32 libx32 mnt opt root run srv sys tmp var boot etc lib lib64 media Nextcloud.Storage...

This might be related to a prior issue I had here: https://forum.proxmox.com/threads/what-is-suddenly-taking-up-so-much-space-on-local.78967/page-2#post-349804 I mounted a directory from the GUI at /Nextcloud.Storage, but that failed and ended up crashing my whole setup. The directory...

root@TracheServ:~# ls -alh /Nextcloud.Storage/ total 20K drwxr-xr-x 7 root root 7 Nov 7 08:53 . drwxr-xr-x 21 root root 27 Nov 7 23:58 .. drwxr-xr-x 2 root root 2 Nov 7 08:53 dump drwxr-xr-x 2 root root 2 Nov 13 08:17 images drwxr-xr-x 2 root root 2 Nov 7 08:53 private drwxr-xr-x 2...

Doesn't show up under df -h, but presumably a zpool wouldn't? root@TracheServ:~# df -h Filesystem Size Used Avail Use% Mounted on udev 24G 0 24G 0% /dev tmpfs 4.8G 146M 4.6G 4% /run...

Here's that output: root@TracheServ:~# zfs list NAME USED AVAIL REFER MOUNTPOINT Nextcloud.Storage 1.80T 854G 105G /Nextcloud.Storage Nextcloud.Storage/vm-400-disk-1 378M 854G 378M - Nextcloud.Storage/vm-42069-disk-0...

Sure I can give it a shot. I've haven't had to unmount a zpool yet, so just to confirm the proper code would be zpool export Nextcloud.Storage ?

root@TracheServ:~# cat /etc/pve/storage.cfg zfspool: local-zfs pool rpool/data content rootdir,images sparse 0 dir: local path /var/lib/vz content backup,rootdir,snippets,iso,vztmpl,images maxfiles 1 shared 0 zfspool: Storage.1...

I was updating to PVE 6.3-2 and saw this error pop up: Setting up zfsutils-linux (0.8.5-pve1) ... zfs-import-scan.service is a disabled or a static unit not running, not starting it. Job for zfs-mount.service failed because the control process exited with error code. See "systemctl status...

root@TracheServ:/# systemctl start zfs-mount.service Job for zfs-mount.service failed because the control process exited with error code. See "systemctl status zfs-mount.service" and "journalctl -xe" for details. root@TracheServ:/# journalctl -xe -- A start job for unit pvesr.service has begun...