Search results

also much obliged @leesteken !

The stale file handle is on the host/node, so that should probably be restarted. You can also remove any stale file handles by creating the following bat file and running it. I have it in cron, running every 5 minutes: #! /bin/bash list=$(df 2>&1 | grep 'Stale file handle' | awk '{print ""$2""...

Experiencing the same. Moving a disk from NAS to local SSD rpool. The proxmox node web interface, ssh and its vm's are no longer responding. Data transfer is still happening though, just can't monitor its progress anymore. Looks like the local filesystem on the proxmox node is fully saturated...

Interesting, I have the 'same' issue where if my Proxmox host comes up before the NFS server is ready, the NFS storage is never mounted and remains offline with a question mark indefinitely. I have to reboot the Proxmox node to get things working again. What have you done to solve this?

Probably same problem here, with the latest and greatest pve. When my NFS server goes down and comes back up again, I have to reboot the PVE nodes to get the NFS share working again. Did you ever find a better solution than rebooting?

If anyone is looking for the way to make this work for an NFS share on OpenMediaVault, use the following share options: subtree_check,insecure,no_root_squash,anonuid=100,anongid=100 and make sure the folder you are sharing is owned by group 'users' (gid 100)

I also use CIFS (on OMV on Thecus N5550 NAS) as I have always been using it for Windows. I read somewhere that NFS is slower than CIFS, but am interested in real life tests to see if there is any noticeable difference.

Also stumbled onto this 'quirk'. Is there a solution to this problem, other than using NFS or local storage? edit: this seems to have been temporary... after running pct fsck 101 again, the image stays clean and I can now stop and start the container without issue. Let's see if this sticks...

Rebooting, which also clears those temp files, helps. If it happens again I try and remedy by deleting those files by hand then running your suggested command. Yesterday I updated the box to Proxmox 7.1-7, since then the msg.lock folder has not reappeared, so I have good hope the samba bug was...

From time to time I get notified backups can't be performed of my Proxmox vm's because storage can't be found: vzdump backup status (pve.lan) : backup failed: could not activate storage 'N5550': storage 'N5550' is not online When I open Proxmox VE console the storage is shown as enabled, but...

Ok, never mind :) I was able to fix this by restoring the container as privileged, and recreating my mount_hook.sh file. After this, the container was able to start.

I had to restore my Proxmox hypervisor due to some storage corruption. I've got almost everything running again, with the exception of one LXC container. During restore I get these errors: extracting archive '/mnt/pve/N5550/dump/vzdump-lxc-103-2020_11_07-07_08_30.tar.lzo' tar...