Jump to content

WarlockSyno

Members
  • Posts

    5
  • Joined

  • Last visited

Posts posted by WarlockSyno

  1. 17 minutes ago, jtp755 said:

    I am having this issue with NFS and digging in to it as well. Ill give the no cache drive a try and see if anything changes.

    What I find odd in my case is that I can add the NFS share to my cluster, see it on both nodes, set up a backup job, run said backup job and everything works great. Leave it for a bit and come back and the storage on both nodes has a question mark and inaccessible. I have another NFS share mounted from another NAS and that has been solid.

    That is the exact issue I'm having with NFS. Like I said, I haven't tried it since then without the cache.

     

    I am using another SMB share with a cached drive no problem mounted in an Ubuntu VM. So not sure what the hang up is with Proxmox.

  2. Hello,

    I'm trying to use an Unraid SMB share as a storage for ISOs, backups, etc. The issue is I cannot set a cache drive to the share. It will immediately kick an error out in Proxmox saying it cannot find the SMB share, even though it can list it.

     

    Here is a view of Proxmox showing details about the SMB share but unable to write to it
    image.thumb.png.b5f87a3b4c2735af8a67ae50d7b68d84.png

     

    INFO: starting new backup job: vzdump 100 --prune-backups 'keep-last=2,keep-weekly=1' --all 0 --node PVE-SOL --storage UNRAID-SMB --mailnotification always --notes-template '{{guestname}}' --mode snapshot --compress zstd
    ERROR: Backup of VM 100 failed - unable to create temporary directory '/mnt/pve/UNRAID-SMB/dump/vzdump-qemu-100-2023_01_16-18_19_28.tmp' at /usr/share/perl5/PVE/VZDump.pm line 930.
    INFO: Failed at 2023-01-16 18:19:28
    INFO: Backup job finished with errors
    TASK ERROR: job errors

     

    If I remove the cache drive from the share it works perfectly fine.

     

     

    This may be related, but I tried to use NFS instead and ran into similar results, I didn't try it without the cache drive though.

     

    This may also not be related, but I turned on SMB log level to 1 and the console is being spammed with this error:

    image.thumb.png.8143c8870c7fdb7cdb77d45ce20005d4.png

×
×
  • Create New...