Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

OneDrive shared folder and chmod #11556

Closed
1 of 2 tasks
fredmo opened this issue May 5, 2024 · 6 comments
Closed
1 of 2 tasks

OneDrive shared folder and chmod #11556

fredmo opened this issue May 5, 2024 · 6 comments

Comments

@fredmo
Copy link

fredmo commented May 5, 2024

Windows Version

Microsoft Windows [version 10.0.22631.3527]

WSL Version

2.2.3.0

Are you using WSL 1 or WSL 2?

  • WSL 2
  • WSL 1

Kernel Version

5.15.153.1-2

Distro Version

Ubuntu 22.04

Other Software

OneDrive Windows : Build 24.076.0414.0005 (64 bits)

Repro Steps

I have a OneDrive folder in Windows.
By using this folder in WSL2, there is no support of chmod.

=> on WSL :
touch ~/OneDrive/test
chmod +x ~/OneDrive/test
chmod: changing permissions of '/home/my/OneDrive/test': Operation not permitted

=> on Native Ubuntu :
It s disturbing because on native linux/ubuntu (24.04), I am able to mount the OneDrive with rclone, and I don't have error of chmod.
chmod +x ~/OneDrive/test
ls -ltr ~/OneDrive/test
ls: /home/me/OneDrive/test: Input/output error
-rw-rw-r-- 1 sah0027 sah0027 0 May 5 17:32 /home/me/OneDrive/test
Yes, in native ubuntu the chmod is not applied , but it s not doing the error on chmod.

( ps : is there a way to have permission support enabled on a OneDrive shared folder ?)

Regards,

Expected Behavior

The issue is to have a difference of behaviour, personally i would prefer the behaviour Ubuntu native.
=> chmod ok

Actual Behavior

=> on WSL :
touch ~/OneDrive/test
chmod +x ~/OneDrive/test
chmod: changing permissions of '/home/my/OneDrive/test': Operation not permitted

Diagnostic Logs

No response

Copy link

github-actions bot commented May 5, 2024

Logs are required for review from WSL team

If this a feature request, please reply with '/feature'. If this is a question, reply with '/question'.
Otherwise please attach logs by following the instructions below, your issue will not be reviewed unless they are added. These logs will help us understand what is going on in your machine.

How to collect WSL logs

Download and execute collect-wsl-logs.ps1 in an administrative powershell prompt:

Invoke-WebRequest -UseBasicParsing "https://raw.githubusercontent.com/microsoft/WSL/master/diagnostics/collect-wsl-logs.ps1" -OutFile collect-wsl-logs.ps1
Set-ExecutionPolicy Bypass -Scope Process -Force
.\collect-wsl-logs.ps1

The scipt will output the path of the log file once done.

Once completed please upload the output files to this Github issue.

Click here for more info on logging
If you choose to email these logs instead of attaching to the bug, please send them to wsl-gh-logs@microsoft.com with the number of the github issue in the subject, and in the message a link to your comment in the github issue and reply with '/emailed-logs'.

View similar issues

Please view the issues below to see if they solve your problem, and if the issue describes your problem please consider closing this one and thumbs upping the other issue to help us prioritize it!

Closed similar issues:

Note: You can give me feedback by thumbs upping or thumbs downing this comment.

@fredmo
Copy link
Author

fredmo commented May 5, 2024

Ps:
in /etc/wsl.conf , I have :
[automount]
options = "metadata"

@fredmo
Copy link
Author

fredmo commented May 5, 2024

and with mount , I see :

C:\ on /mnt/c type 9p (rw,noatime,dirsync,aname=drvfs;path=C:;uid=0;gid=0;metadata;symlinkroot=/mnt/,mmap,access=client,msize=65536,trans=fd,rfd=11,wfd=11)

And in wsl, ~/OneDrive is a symlink to : /mnt/c/XX/OneDrive - YY/

@OneBlue
Copy link
Collaborator

OneBlue commented May 7, 2024

The error you're seeing is because Linux permissions don't really make sense for a OneDrive folder mounted on the Windows side.

Accessing the files themselves should work though. Could you capture logs of the file accesses failing ? /logs

Copy link
Contributor

Hello! Could you please provide more logs to help us better diagnose your issue?

To collect WSL logs, download and execute collect-wsl-logs.ps1 in an administrative powershell prompt:

Invoke-WebRequest -UseBasicParsing "https://raw.githubusercontent.com/microsoft/WSL/master/diagnostics/collect-wsl-logs.ps1" -OutFile collect-wsl-logs.ps1
Set-ExecutionPolicy Bypass -Scope Process -Force
.\collect-wsl-logs.ps1

The scipt will output the path of the log file once done.

Once completed please upload the output files to this Github issue.

Click here for more info on logging

If you choose to email these logs instead of attaching to the bug, please send them to wsl-gh-logs@microsoft.com with the number of the github issue in the subject, and in the message a link to your comment in the github issue.

Thank you!

Copy link
Contributor

This issue has been automatically closed since it has not had any author activity for the past 7 days. If you're still experiencing this issue please re-file it as a new issue.

Thank you!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants