search for: smbtran2

...t 0x8, what Samba calls SMBgetattr). > This doesn't have the links or expanded time information > (it only returns one date) so the client isn't then able > to synthesize this information. > Also the client isn't caching the fact that the server > doesn't understand SMBtran2:QPATHINFO:263 and so it > keeps issuing these and doing the fallback on every > query. This will significantly damage performance. Whose performance, client's? Server's? Both? Only between the two? Do you have an recommendations that don't involve abandoning the only acceptable m...

Jeremy Allison via samba composed on 2020-04-23 09:24 (UTC-0700): > On Thu, Apr 23, 2020 at 02:59:18AM -0400, Felix Miata via samba wrote: >> Items in dmesg when FAT share's are accessed from web browser: >> CIFS VFS: bogus file nlink value 0 > nlink should never be zero. If an SMB server > returns that, then the CIFSFS client will have > to fake it to 1 at least.

...tion Request (SMB1 request 0x8, what Samba calls SMBgetattr). This doesn't have the links or expanded time information (it only returns one date) so the client isn't then able to synthesize this information. Also the client isn't caching the fact that the server doesn't understand SMBtran2:QPATHINFO:263 and so it keeps issuing these and doing the fallback on every query. This will significantly damage performance.

.... > > > This doesn't have the links or expanded time information > > (it only returns one date) so the client isn't then able > > to synthesize this information. > > > Also the client isn't caching the fact that the server > > doesn't understand SMBtran2:QPATHINFO:263 and so it > > keeps issuing these and doing the fallback on every > > query. This will significantly damage performance. > > Whose performance, client's? Server's? Both? Only between the two? Do you have an > recommendations that don't involve abandon...