惯性聚合 高效追踪和阅读你感兴趣的博客、新闻、科技资讯
阅读原文 在惯性聚合中打开

推荐订阅源

Apple Machine Learning Research
Apple Machine Learning Research
M
MIT News - Artificial intelligence
罗磊的独立博客
博客园 - 【当耐特】
A
About on SuperTechFans
Last Week in AI
Last Week in AI
雷峰网
雷峰网
IT之家
IT之家
aimingoo的专栏
aimingoo的专栏
H
Hackread – Cybersecurity News, Data Breaches, AI and More
博客园_首页
博客园 - 叶小钗
Microsoft Azure Blog
Microsoft Azure Blog
博客园 - Franky
J
Java Code Geeks
Cyber Security Advisories - MS-ISAC
Cyber Security Advisories - MS-ISAC
D
Docker
Engineering at Meta
Engineering at Meta
B
Blog RSS Feed
The Cloudflare Blog
大猫的无限游戏
大猫的无限游戏
阮一峰的网络日志
阮一峰的网络日志
S
SegmentFault 最新的问题
Recent Announcements
Recent Announcements

Proxmox Support Forum

[SOLVED] - Github Auth for Mirrors-Kernel Repo? [Automation] Mass migration tool for MS Win11/Server Proxmox GUI hang - not response is it possible to reject or quarantine spam based on conditions I set ? The PVENode task list in PVE9 is partially obscured due to the terminal font being too large. About 100% error reporting due to pveproxy.service hooks Kubernetes overlay networking breaks when upgrading from PVE 9.1 to PVE 9.2.3 Zentraler Speicher No space left on device Combine datastore and direct file archival to tape Kernel panic VFS: Unable to mount root fs on unknown-block (0,0) sobald ein 7.x Kernel verwendet wird. How to migrate disk of a VM from one ZFS to another Windows Server 2025 fails to boot after PVE 9.2 / Linux 7.0 Kernel upgrade Cannot Install Proxmox on T610 Poweredge with H700 PERC card sdn Config. gateway not reachable How to safely change domain/FQDN? Welche Filterquote erreicht ihr? NFS Share status unknown on 2 of 5 nodes Can't connect to PVE9 consoles [solved] Can't connect to PVE9 consoles [solved] [SOLVED] - Use secondary network for PVE commands Created cluster, one node storage gone BUG: proxmox mail gateway FROM = null bypass spam filtering Moving existing PBS from VMWare workstation to PVE cluster Does eBGP SDN fabric support external peering? Bug: PDM 1.1 not recognizing valid license status Proxmox GUI hang - not response PVE crashes unexpectedly Proxmox Backup Server 4.2 released! Advice
LXC Backup Failure/Permissions Issue
invalid@exam · 2026-06-16 · via Proxmox Support Forum

Hello!

New proxmox, samba, and Linux user here, and I am trying to create a backup for an unprivileged LXC I have created to host samba for interfacing with windows PCs on my network, but I am running into a file permissions error during the backup process that is causing it to fail. I have already mounted an external HDD on both the host and on the lxc to use as the samba share location, and I re-mapped the ID/GID of one user so I could access the shares on windows (which I was successfully able to do). Backing up after the re-mapping, however, fails:

Code:

INFO: Starting Backup of VM 101 (lxc)
INFO: Backup started at 2025-11-02 18:36:06
INFO: status = running
INFO: CT Name: samba
INFO: including mount point rootfs ('/') in backup
INFO: excluding bind mount point mp0 ('/media/postdata1') from backup (not a volume)
INFO: backup mode: snapshot
INFO: ionice priority: 7
INFO: create storage snapshot 'vzdump'
  WARNING: You have not turned on protection against thin pools running out of space.
  WARNING: Set activation/thin_pool_autoextend_threshold below 100 to trigger automatic extension of thin pools before they get full.
  Logical volume "snap_vm-101-disk-0_vzdump" created.
  WARNING: Sum of all thin volume sizes (<1.01 TiB) exceeds the size of thin pool pve/data and the size of whole volume group (<475.00 GiB).
INFO: creating vzdump archive '/var/lib/vz/dump/vzdump-lxc-101-2025_11_02-18_36_06.tar.zst'
INFO: tar: ./home/chris: Cannot open: Permission denied
INFO: Total bytes written: 1029683200 (982MiB, 151MiB/s)
INFO: tar: Exiting with failure status due to previous errors
INFO: cleanup temporary 'vzdump' snapshot
  Logical volume "snap_vm-101-disk-0_vzdump" successfully removed.
ERROR: Backup of VM 101 failed - command 'set -o pipefail && lxc-usernsexec -m u:0:100000:1000 -m g:0:100000:1000 -m u:1000:1000:1 -m g:1000:1000:1 -m u:1001:101001:64534 -m g:1001:101001:64534 -- tar cpf - --totals --one-file-system -p --sparse --numeric-owner --acls --xattrs '--xattrs-include=user.*' '--xattrs-include=security.capability' '--warning=no-file-ignored' '--warning=no-xattr-write' --one-file-system '--warning=no-file-ignored' '--directory=/tmp/vzdumptmp479701_101/' ./etc/vzdump/pct.conf ./etc/vzdump/pct.fw '--directory=/mnt/vzsnap0' --no-anchored '--exclude=lost+found' --anchored '--exclude=./tmp/?*' '--exclude=./var/tmp/?*' '--exclude=./var/run/?*.pid' ./ | zstd '--threads=1' >/var/lib/vz/dump/vzdump-lxc-101-2025_11_02-18_36_06.tar.dat' failed: exit code 2
INFO: Failed at 2025-11-02 18:36:13
INFO: Backup job finished with errors
INFO: notified via target `mail-to-root`
TASK ERROR: job errors

It seems that the user directory /home/chris is the source of the error, so I figured I would check it out. Navigating to /home within the samba lxc console and checking perms shows me:

Code:

root@samba:~# cd /home
root@samba:/home# ls -l
total 8
drwxr-x--- 2 nobody nogroup 4096 Nov  1 17:45 chris
drwxrwxrwx 2 nobody nogroup 4096 Nov  1 01:16 christine

This makes me think I have a permissions issue related to those user directories (specifically chris), so I attempted to use:
chmod -R 755 /home/chris
to change ownership, but I get:

Code:

root@samba:/home# chmod -R 755 /home/chris
chmod: changing permissions of '/home/chris': Operation not permitted
chmod: cannot read directory '/home/chris': Permission denied

Changing ownership does not seem to work either:

Code:

root@samba:/home# sudo chown -R nobody:nogroup /home
chown: cannot read directory '/home/chris': Permission denied

Notably, I can change the directory associated with christine, but not chris. I did follow this process for the UID/GIDs for mapping the host ID to the container ID:
https://pve.proxmox.com/wiki/Unprivileged_LXC_containers
which I only applied to the associated ID of chris (ID:1000).

nano /etc/pve/lxc/101.conf on the host shell yields:

Code:

arch: amd64
cores: 1
features: nesting=1
hostname: samba
memory: 1024
mp0: /media/postdata1,mp=/media/postdata1
net0: name=eth0,bridge=vmbr0,firewall=1,hwaddr=BC:24:11:09:E3:A0,ip=dhcp,type=veth
ostype: ubuntu
rootfs: local-lvm:vm-101-disk-0,size=8G
swap: 1024
unprivileged: 1
lxc.idmap: u 0 100000 1000
lxc.idmap: g 0 100000 1000
lxc.idmap: u 1000 1000 1
lxc.idmap: g 1000 1000 1
lxc.idmap: u 1001 101001 64534
lxc.idmap: g 1001 101001 64534

So it makes me think this is related. Currently I can access my mounted drive as intended from both the container and windows, but nothing I do seems to allow me access to /home/chris and it is causing my backups to fail.

Has anyone encountered this issue before, or is there something obvious I am missing here? Thank you in advance!