Björn, 
As documented in MS-FSA (see reference), only NTFS and ReFS support stream name 
types. 
        See MS-FSA <43> Section 2.1.5.1: . . .
        Other Windows file systems do not recognize any stream type names. 

Regarding the graceful error handling on the client, one aspect is that FAT 
systems do not support more than one data stream, and the error generic the 
server returns when it doesn't support a stream type is 
STATUS_OBJECT_NAME_INVALID. ReFS is different, as it does support ADS, but has 
a limit which reports STATUS_FILE_SYSTEM_LIMITATION. I think the two error 
codes convey two different things. I will try to see whether I can provide 
further comment on this and follow-up.

I will open a document bug on MS-FSA and that we update the 128K limitation for 
ReFS ADS with error STATUS_FILE_SYSTEM_LIMITATION.

MS-FSA
2.1.5.1 Server Requests an Open of a File
§       If StreamTypeNameToOpen is non-empty and StreamTypeNameToOpen is not 
equal to one of the stream type names recognized by the object store<43> (using 
case-insensitive string comparisons), the operation MUST be failed with 
STATUS_OBJECT_NAME_INVALID.
<43> Section 2.1.5.1: NTFS and ReFS recognize the following stream type names:
§       "$STANDARD_INFORMATION"
§       "$ATTRIBUTE_LIST"
§       "$FILE_NAME"
§       "$OBJECT_ID"
§       "$SECURITY_DESCRIPTOR"
§       "$VOLUME_NAME"
§       "$VOLUME_INFORMATION"
§       "$DATA"
§       "$INDEX_ROOT"
§       "$INDEX_ALLOCATION"
§       "$BITMAP"
§       "$REPARSE_POINT"
§       "$EA_INFORMATION"
§       "$EA"
§       "$LOGGED_UTILITY_STREAM"
Other Windows file systems do not recognize any stream type names.

Thanks,
Edgar 


-----Original Message-----
From: Edgar Olougouna 
Sent: Tuesday, March 5, 2019 4:01 PM
To: Björn JACKE <b...@sernet.de>
Cc: cifs-protocol@lists.samba.org; MSSolve Case Email <casem...@microsoft.com>
Subject: RE: 119030519730578 server response for oversized alternate data 
streams

Thanks Björn, I will take a look and get back to you. 
Edgar 

-----Original Message-----
From: Björn JACKE <b...@sernet.de> 
Sent: Tuesday, March 5, 2019 3:49 PM
To: Edgar Olougouna <edg...@microsoft.com>
Cc: cifs-protocol@lists.samba.org; MSSolve Case Email <casem...@microsoft.com>
Subject: Re: 119030519730578 server response for oversized alternate data 
streams

Hello Edgar,

On 2019-03-05 at 20:24 +0000 Edgar Olougouna sent off:
> Can you please share some network captures (e.g. .cap traces ) of your test 
> cases? 
> I will investigate this and follow-up.

thanks for your answer, attached there are 2 captures of a current Windows 10 
client (explorer.exe) copying a file test.txt with a ~400kb ADS "mystream" in 
it onto a 2012R2 server.

refs-sniff-packet-487.pcap.gz:
In this capture the share is a ReFS (128k sized ADS supported) volume, see 
packet 487 ff.

vfat-sniff-packet-147.pcap.gz:
In this capture the share is a vfat volume with no ADS support, see packet 147 
ff.

There are also the screenshots of the dialogues the Windows 10 client shows 
when the ADS writes fails for both cases.

Thank you!
Björn
--
SerNet GmbH, Bahnhofsallee 1b, 37081 Göttingen
phone: 0551-370000-0, mail: kont...@sernet.de
Gesch.F.: Dr. Johannes Loxen & Reinhild Jung AG Göttingen: HR-B 2816 - 
https://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.sernet.de&amp;data=02%7C01%7Cedgaro%40microsoft.com%7C38514d342a8d4073590c08d6a1b4580e%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C1%7C636874193466020595&amp;sdata=GIVEvFxHvqwTd%2BXvtSjmpBKPfk9Px2SbfsCOTLkn6ik%3D&amp;reserved=0

Samba eXPerience 2019, Hotel Freizeit In sponsored by Google, Microsoft & Red 
Hat June, 4th - 6th 2019, 
https://nam06.safelinks.protection.outlook.com/?url=http%3A%2F%2FsambaXP.org&amp;data=02%7C01%7Cedgaro%40microsoft.com%7C38514d342a8d4073590c08d6a1b4580e%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C1%7C636874193466020595&amp;sdata=WaCKgTPFKVbKLRddYFRPkwZZzclnFPhVhksKMqcT0%2Fk%3D&amp;reserved=0

_______________________________________________
cifs-protocol mailing list
cifs-protocol@lists.samba.org
https://lists.samba.org/mailman/listinfo/cifs-protocol

Reply via email to