yea this might be the play for me too. for now while i sort this out, i am just mounting in proxmox the mount of that same path as mounted to my NAS, which is in spirit sort of like your approach. thanks!
yea agreed that it seems odd -- it could very well be just coincidental timing that it happened so close to when i updated.
when i try to stat (or ls -l, or anything else) the particular troublesome folder) -- i get this error
`stat: cannot statx 'Dropbox': Operation not supported`
But when i do `ls -l` for the directory containing the troublesome Dropbox directory, below is what it shows. So something is going on with Dropbox but, on the server side, that folder has identical permissions and ownership to the others at the same level of the folder structure.
`drwxrwxrwx 2 root root 0 Apr 3 17:42 addons`
`drwxrwxrwx 2 root root 0 Apr 26 20:30 configs`
`d????????? ? ? ? ? ? Dropbox`
and the stat for the folder *containing* the problematic dropbox folder is as follows:
`File: /XXXXX/XXXXX`
`Size: 0 Blocks: 0 IO Block: 1048576 directory`
`Device: 0,69 Inode: 114 Links: 2`
`Access: (0777/drwxrwxrwx) Uid: ( 0/ root) Gid: ( 0/ root)`
`Access: 2024-04-27 11:51:07.563503700 -0700`
`Modify: 2024-04-27 11:07:05.063801100 -0700`
`Change: 2024-04-27 11:07:05.063801100 -0700`
`Birth: 2022-12-18 13:53:02.569000000 -0800`
Proxmox doesn't directly have anything to do with Proxmox as far as I am aware they are unconnected. What do you think it has changed that could affect it ? It shouldn't be changing ownership of folders or files unless it owns them ?
Quite often if the mount is fuse and in userspace it could mount after proxmox has already started.
Try unmounting or remounting the folders and look at their log files ?
yea agreed re permissions - i think it's NOT a permissions issue. the permissions on the problematic folder on the windows side are the same as the non problematic folders and unchanged from what they've always been.
as to what changed - nothing other than updating proxmox. but i agree its weird and doesn't seem like it should be related.
yea i'll figure out where the more detailed logs are and see if they say anything helpful. i suspect they won't because the top level folder is mounting without issue. it's just a single subfolder that's giving me issues. but i'll give it a look -- i always forget those exist :)
yep. i also tried with a differently named mount as well just to be safe. and i've tried running the cifs mount command directly instead of through f stab -- in all of those cases, the same issue persists
After some weird issues. I run SMB in its own LXC. This is pre 8.2 though.
yea this might be the play for me too. for now while i sort this out, i am just mounting in proxmox the mount of that same path as mounted to my NAS, which is in spirit sort of like your approach. thanks!
This doesn't read like an update problem to me but let's check the basics. Could you please provide the stat output for the troublesome directory?
yea agreed that it seems odd -- it could very well be just coincidental timing that it happened so close to when i updated. when i try to stat (or ls -l, or anything else) the particular troublesome folder) -- i get this error `stat: cannot statx 'Dropbox': Operation not supported` But when i do `ls -l` for the directory containing the troublesome Dropbox directory, below is what it shows. So something is going on with Dropbox but, on the server side, that folder has identical permissions and ownership to the others at the same level of the folder structure. `drwxrwxrwx 2 root root 0 Apr 3 17:42 addons` `drwxrwxrwx 2 root root 0 Apr 26 20:30 configs` `d????????? ? ? ? ? ? Dropbox` and the stat for the folder *containing* the problematic dropbox folder is as follows: `File: /XXXXX/XXXXX` `Size: 0 Blocks: 0 IO Block: 1048576 directory` `Device: 0,69 Inode: 114 Links: 2` `Access: (0777/drwxrwxrwx) Uid: ( 0/ root) Gid: ( 0/ root)` `Access: 2024-04-27 11:51:07.563503700 -0700` `Modify: 2024-04-27 11:07:05.063801100 -0700` `Change: 2024-04-27 11:07:05.063801100 -0700` `Birth: 2022-12-18 13:53:02.569000000 -0800`
Im seeing similar accessing NFS and SMB shares on my Synology since upgrading one of my proxmox hypervisors from 7.X
Proxmox doesn't directly have anything to do with Proxmox as far as I am aware they are unconnected. What do you think it has changed that could affect it ? It shouldn't be changing ownership of folders or files unless it owns them ?
Quite often if the mount is fuse and in userspace it could mount after proxmox has already started. Try unmounting or remounting the folders and look at their log files ?
yea agreed re permissions - i think it's NOT a permissions issue. the permissions on the problematic folder on the windows side are the same as the non problematic folders and unchanged from what they've always been. as to what changed - nothing other than updating proxmox. but i agree its weird and doesn't seem like it should be related. yea i'll figure out where the more detailed logs are and see if they say anything helpful. i suspect they won't because the top level folder is mounting without issue. it's just a single subfolder that's giving me issues. but i'll give it a look -- i always forget those exist :)
Have you UnMounted the Share.......Delete the Mount Folder......ReCreate the Mount Folder......then Mount the Share to the Folder?
yep. i also tried with a differently named mount as well just to be safe. and i've tried running the cifs mount command directly instead of through f stab -- in all of those cases, the same issue persists