Thank you for reporting this. If anyone has easy setup instructions, please feel free to share, that is not a configuration I have tried. I did find the reparse tag in the protocol specifications (see MS-FSCC section 2.1.21) and it does indicate that it should be ignored. Presumably the workaround would be to move this onedrive link down one directory, but we will need to investigate ASAP how to fix this. IO_REPARSE_TAG_CLOUD_6 0x9000601A "Used by the Cloud Files filter, for files managed by a sync engine such as OneDrive. Server-side interpretation only, not meaningful over the wire." On Mon, Aug 19, 2024 at 8:15 PM Marc <1marc1@xxxxxxxxx> wrote: > > Dear all, > > First time posting here. Let me know if this is not the right location > for this message: I am happy to redirect it elsewhere. > > I have the following setup: Windows 11 machine running in VirtualBox, > hosted on Ubuntu 22.04. > > The Windows machine uses MS OneDrive to connect to our corporate > OneDrive for SharePoint. Inside the OneDrive directory structure, I > have created a Windows share. Let's call it "mydata". > > Whenever the Windows 11 machine is running, on my Ubuntu host, I then > run `sudo mount.cifs //192.168.56.2/mydata /mnt/mydata -o > username=marc,uid=1000,gid=1000`. This will then mount the Windows > share and I can work with the files on Ubuntu. > > This has been working great for many years. Yesterday, this stopped > working. When I tried mounting the share, I would get the following > error: "mount error(95): Operation not supported". In dmesg I see: > "VFS: parse_reparse_point: unhandled reparse tag: 0x9000601a" and > "VFS: cifs_read_super: get root inode failed". > > My Ubuntu host machine is completely up to date, running kernel > 6.8.0-40-generic. From this machine I am able to mount other shares on > the same Windows 11 box. It seems that as long as the shares have > nothing to do with OneDrive, it works. > > When I booted my Ubuntu machine on kernel 6.5.0-45-generic, I am able > to mount the OneDrive-related shares again. > > Hopefully someone can have a look into this situation. > > Regards, /|/|arc. > -- Thanks, Steve
