search

winfsp / cgofuse

Cross-platform FUSE library for Go - Works on Windows, macOS, Linux, FreeBSD, NetBSD, OpenBSD
https://winfsp.dev
MIT License
511 stars 82 forks source link

Not able to do file listing using memfs on Windows Server 2008 R2 #42

Closed mohankumarv2005 closed 4 years ago

mohankumarv2005 commented 4 years ago

Hi,

On Windows Server 2008 R2, I tried to mount memfs.exe and after creating a folder let's say "F1", it is not allowing to browse/ls the created folder. I get an error as attached. Issue

I see this issue on other Operating Systems like Windows 2012 R2 & few Windows 10 machines as well.

Thanks, Mohan

billziss-gh commented 4 years ago

This really depends on the scenario that you want to enable, but for MEMFS the easiest might be to start the file system with the -o uid=-1,gid=-1 command line option. This will make all files to be owned by the user that launched the file system.

mohankumarv2005 commented 4 years ago

As suggested, I tried above option memfs.exe -o "uid=-1" -o "gid=-1" but no luck. Still I see same issue.

billziss-gh commented 4 years ago

Did you start memfs from the same account as the one used to access the files in it? Also Make sure that you do not start memfs from an elevated prompt and then try to access the files from a non-elevated Explorer/prompt/etc.

mohankumarv2005 commented 4 years ago

Yes, I have started memfs from non-elevated prompt and also accessing from explorer which is non-elevated too. Also, even I tried to start with elevated it is not helping.

billziss-gh commented 4 years ago

I am not able to reproduce this. See screenshot below:

Capture

mohankumarv2005 commented 4 years ago

Hi Bill,

Thank you for looking into this. I have attached debug logs of the above scenario. Can you please see if you find anything interesting? Also, is there any other logs or details that you may need to understand what could be issue behind this?

Thanks, Mohan

memfs.log

mohankumarv2005 commented 4 years ago

We found the root cause for this issue, looks like when we mount with user account whose domain is not same as Machine Domain then we see this problem.

billziss-gh commented 4 years ago

@mohankumarv2005

Glad that you have figured out the cause and sorry for being unresponsive this last week as I was away for the Thanksgiving holiday.

I am closing this, but please reopen if you still believe there is a problem.