Hyper-V VSS FREEZE fails with 'access denied' on /run/user/$UID/doc
I've got 4 similar Ubuntu 20.04 LTS VMs running on Server 2016 Hyper-V. One of these fails to create a successful production checkpoint in Hyper-V after the user logs into the VM GUI (using xRDP). Searching /var/log/syslog on the VM shows this:
Sep 29 03:03:46 devbuntu Hyper-V VSS: VSS: op=CHECK HOT BACKUP
Sep 29 03:03:47 devbuntu Hyper-V VSS: FREEZE of /run/user/
Sep 29 03:03:47 devbuntu Hyper-V VSS: VSS: op=FREEZE: failed
Sep 29 03:03:47 devbuntu Hyper-V VSS: op=5 failed!
Sep 29 03:03:47 devbuntu Hyper-V VSS: report it with these files:
Sep 29 03:03:47 devbuntu Hyper-V VSS: /etc/fstab and /proc/mounts
I read this as a failure caused by the Hyper-V VSS integrations in Ubuntu get 'access denied' when trying to "FREEZE" "/run/user/
A view of 'mount |grep /run/user/
Out of the four machines, this is the only one with the /run/user/
So my questions are:
How can I prevent/modify the fuse mount (or whatever is creating it) to allow Hyper-V VSS FREEZE function to succeed?
Does this conflict need to be reported as a bug in Hyper-V VSS, fuse, or xdg-desktop-portal?
Further info:
lsof /run/user/
lsof: status error on /run/user/
lsof 4.93.2
mount |grep /run/user/
/dev/fuse on /run/user/
cat /etc/fstab
# /etc/fstab: static file system information.
#
# Use 'blkid' to print the universally unique identifier for a
# device; this may be used with UUID= as a more robust way to name devices
# that works even if disks are added and removed. See fstab(5).
#
# <file system> <mount point> <type> <options> <dump> <pass>
/dev/mapper/
# /boot/efi was on /dev/sda1 during installation
UUID=3295-E5AE /boot/efi vfat umask=0077 0 1
/dev/mapper/
uname -a
Linux is-ubuntu 5.11.0-36-generic #40~20.04.1-Ubuntu SMP Sat Sep 18 02:14:19 UTC 2021 x86_64 x86_64 x86_64 GNU/Linux
Question information
- Language:
- English Edit question
- Status:
- Expired
- For:
- Ubuntu Edit question
- Assignee:
- No assignee Edit question
- Last query:
- Last reply: