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

zpool shared files aren't accessible over SMBv1/SMBv2 #448

Open
0xDEADFED5 opened this issue Feb 19, 2025 · 5 comments
Open

zpool shared files aren't accessible over SMBv1/SMBv2 #448

0xDEADFED5 opened this issue Feb 19, 2025 · 5 comments

Comments

@0xDEADFED5
Copy link

0xDEADFED5 commented Feb 19, 2025

System information

zfs-windows-2.2.6-rc11
Windows 11 Education 22621.4751

Describe the problem you're observing

zpool shared files aren't accessible over the network, they're completely unable to be opened, but they're visible.

same files copied to non-zpool location are successfully accessed over shared folder.

not sure how to provide more useful information.

Describe how to reproduce the problem

right click folder -> advanced sharing -> share folder

access folder from another PC on network

Include any warning/errors/backtraces from the system logs

i can browse the shared zpool folder and see everything, but cannot access any files

it's not a permissions issue.

PS C:\Users\ANON> zpool status
  pool: tank
 state: ONLINE
  scan: resilvered 256K in 00:00:01 with 0 errors on Thu Feb  6 22:31:25 2025
config:

        NAME                STATE     READ WRITE CKSUM
        tank                ONLINE       0     0     0
          raidz2-0          ONLINE       0     0     0
            physicaldrive0  ONLINE       0     0     0
            physicaldrive1  ONLINE       0     0     0
            physicaldrive2  ONLINE       0     0     0
            physicaldrive3  ONLINE       0     0     0
            physicaldrive4  ONLINE       0     0     0
            physicaldrive5  ONLINE       0     0     0
            physicaldrive6  ONLINE       0     0     0
            physicaldrive7  ONLINE       0     0     0

errors: No known data errors
@lundman
Copy link

lundman commented Feb 19, 2025

If you have time/motivation, run FileSpy.exe on the server side, point it to the ZFS driveletter and perform a task that fails.
I will do that when I find the time.

@0xDEADFED5
Copy link
Author

is this the tool you're referring to?

https://www.osronline.com/article.cfm%5Earticle=370.htm

@lundman
Copy link

lundman commented Feb 19, 2025

That's the one, run as administrator for it to be able to capture IRPs between system and ZFS

@0xDEADFED5
Copy link
Author

FileSpy.txt

here's the log. i shared an outer folder with only a couple files to try to reduce the amount of crap in the log.

the file i tried (and failed) to load is called: WP_20141206_00_01_06_Pro.mkv

@lundman
Copy link

lundman commented Feb 19, 2025

Thank you, very helpful;

IRP_MJ_FILE_SYSTEM_CONTROL/IRP_MN_USER_FS_REQUEST	H:	STATUS_OPLOCK_NOT_GRANTED	Unknown

I am curious on this one, but it is probably not the issue. Just wondering why the oplock was rejected.

IRP_MJ_CREATE	:00000000-C01C0005Ā	STATUS_OBJECT_NAME_NOT_FOUND	FILE_SUPERSEDE CreOpts: 0 Access: 0 Share: 0 Attrib: 0
IRP_MJ_CREATE	:00000000-C01C0005ā	STATUS_OBJECT_NAME_NOT_FOUND	FILE_SUPERSEDE CreOpts: 0 Access: 0 Share: 0 Attrib: 0

Well now, this is new. I suspect this is ADS usage. Normally, we would get a request to open
WP_20141206_00_01_06_Pro.mkv:00000000-C01C0005 to open ADS 00000000-C01C0005 inside the file.

This looks to use :00000000-C01C0005 with the FileObject->RelatedFileObject set to the file as some sort of short hand.
I was unaware this was a thing, I will need to add some code for this case.

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

No branches or pull requests

2 participants