Displaying 3 results from an estimated 3 matches for "smb2maperror".
2019 Feb 14
3
32 seconds vs 72 minutes -- expected performance difference?
Saurabh Nanda <saurabhnanda at gmail.com> writes:
> I found something interesting in /proc/fs/cifs/Stats. Notice the
> "QueryDirectories > Failed" number. This keeps increasing as along as `ls
> -lR` is running.
That's interesting indeed. The verbose logs and network trace would tell
us more.
--
Aurélien Aptel / SUSE Labs Samba Team
GPG: 1839 CB5F 9F5B FB9B AA97
2019 Feb 15
3
32 seconds vs 72 minutes -- expected performance difference?
...uffer passed to
> cifs_small_buf_release
That can be ignored
> 4) Is this normal --
> fs/cifs/readdir.c: index not in buffer - could not findnext into
> it
> fs/cifs/readdir.c: could not find entry
> 5) This definitely seems like some error, right? -- fs/cifs/smb2maperror.c:
> Mapping SMB2 status code 0x80000006 to POSIX err -61
0x80000006 is STATUS_NO_MORE_FILES, returned by the server at the end of
a listing. Can be ignored, its not added to the stats as it's the
expected "error" for the last listing packet.
> There is also another data point...
2019 Feb 15
0
32 seconds vs 72 minutes -- expected performance difference?
...id 11907
3) Is this normal -- fs/cifs/misc.c: Null buffer passed to
cifs_small_buf_release
4) Is this normal --
fs/cifs/readdir.c: index not in buffer - could not findnext into
it
fs/cifs/readdir.c: could not find entry
5) This definitely seems like some error, right? -- fs/cifs/smb2maperror.c:
Mapping SMB2 status code 0x80000006 to POSIX err -61
There is also another data point which _might_ be relevant. It _seems_ that
"systemd-resolved" is randomly crashing on the server , possibly because of
the mounted samba share. Caveat: I am not completely sure about the
correlation...