search for: chiller3

..._FILE_POSIX_INFO. On Thu, Nov 28, 2024, at 04:53, Ralph Boehme wrote: > can you grab a network trace when it happens? Sure thing! I disabled SMB encryption first since it seemed to make the pcaps useless. 1. pcap when running `cat <file>`, which fails with EINVAL: https://files.pub.chiller3.com/issues/samba/posix_extensions/2024-11-28/posix_enabled_broken.pcap 2. pcap when running `ls $(dirname <file>); cat <file>`, which seems to temporarily (but consistently) allow the file to be opened for a short time: https://files.pub.chiller3.com/issues/samba/posix_extensio...

...at 04:53, Ralph Boehme wrote: >> can you grab a network trace when it happens? > > Sure thing! I disabled SMB encryption first since it seemed to make the pcaps > useless. > > 1. pcap when running `cat <file>`, which fails with EINVAL: > > https://files.pub.chiller3.com/issues/samba/posix_extensions/2024-11-28/posix_enabled_broken.pcap > it's a client problem. See packet 30: the client issues an POSIX SMB2-CREATE with a pathname starting with a "/" which is not allowed. If you check the working cases there the pathnames are relative and do...

...ssage like this in the client's dmesg: [ 4295.972953] CIFS: enabling forceuid mount option implicitly because uid= option is specified [ 4295.972958] CIFS: enabling forcegid mount option implicitly because gid= option is specified [ 4295.972961] CIFS: Attempting to mount //sm-1.int.chiller3.com/home/Documents/Notes/Linux/Shells.txt [ 4295.974221] CIFS: VFS: cifs_mount failed w/return code = -22 (The `log level = 3` samba logs are included at the end of this email.) If I turn off SMB3 POSIX extensions, then this issue never occurs. On the server side, there isn't really anyt...