Obaid Farooqi <[email protected]> writes: > Please let me know if it does not answer your question.
I think it does, partially. Steve forwarded me a response he got from a previous dochelp ticket: > [MS-SMB2] Explicitly states that the two IDs you're referring to must be > the same: > > 3.3.5.9.9 Handling the SMB2_CREATE_QUERY_ON_DISK_ID Create Context > The server MUST set the DiskFileId by querying the underlying object store > in an implementation-specific manner. The DiskFileId value MUST be the same > as the value returned in an SMB2 QUERY_INFO response to an SMB2 QUERY_INFO > request with the FileInformationClass field set to the > FileInternalInformation value, as specified in section 3.3.5.20.1. The > DiskFileId value SHOULD uniquely identify the file among all other files > sharing the same VolumeId value on the server. Which gives me a more complete picture. I have a case of a (non-Windows) server where SMB2_CREATE_QUERY_ON_DISK_ID response is different than the FileId from FileInternalInformation. So I guess that's a server bug from the vendor. Thanks! -- Aurélien Aptel / SUSE Labs Samba Team GPG: 1839 CB5F 9F5B FB9B AA97 8C99 03C8 A49B 521B D5D3 SUSE Software Solutions Germany GmbH, Maxfeldstr. 5, 90409 Nürnberg, DE GF: Felix Imendörffer, Mary Higgins, Sri Rasiah HRB 247165 (AG München) _______________________________________________ cifs-protocol mailing list [email protected] https://lists.samba.org/mailman/listinfo/cifs-protocol
