[Bug 232145] sysutils/fusefs-smbnetfs: Error when writing to share (smb_conn_srv_fstat: errno=22, Invalid argument)

bugzilla-noreply at freebsd.org bugzilla-noreply at freebsd.org
Wed Oct 10 04:03:04 UTC 2018


https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=232145

            Bug ID: 232145
           Summary: sysutils/fusefs-smbnetfs: Error when writing to share
                    (smb_conn_srv_fstat: errno=22, Invalid argument)
           Product: Ports & Packages
           Version: Latest
          Hardware: amd64
                OS: Any
            Status: New
          Severity: Affects Many People
          Priority: ---
         Component: Individual Port(s)
          Assignee: ports-bugs at FreeBSD.org
          Reporter: cvetomirconev at gmail.com
                CC: mi at ALDAN.algebra.com
                CC: mi at ALDAN.algebra.com
             Flags: maintainer-feedback?(mi at ALDAN.algebra.com)

Trying to write a file on a share with 0.6.1_1 results in an error:

  srv(24578)->smb_conn_srv_listen: process query=13, query_len=8
  srv(24578)->smb_conn_srv_fstat: errno=22, Invalid argument
  14224->process_kill_by_smb_conn_fd: closing child connection with pid=24578,
fd=7

Trace:
 18395 smbnetfs RET   write 87/0x57
 18395 smbnetfs CALL 
select(0x8,0x7fffdfdfb610,0,0x7fffdfdfb690,0x7fffdfdfb750)
 18395 smbnetfs RET   select 1
 18395 smbnetfs CALL  read(0x7,0x7fffdfdfb7c0,0x1000)
 18395 smbnetfs GIO   fd 7 read 92 bytes
       0x0000 5c00 0000 0000 0000 fdff ffff 1600 0000 f747 0000 0000 0000 1000
0000 0000 0000 7372 7628 3138 3432 3329 2d3e 736d 625f 636f 6e6e 5f73 7276 5f66
7374 6174  |\................G..............srv(18423)->smb_conn_srv_fstat|
       0x003e 3a20 6572 726e 6f3d 3232 2c20 496e 7661 6c69 6420 6172 6775 6d65
6e74 0a00                                                                      
           |: errno=22, Invalid argument..|

Listing and reading files works fine.
The problem is not present in 0.6.1 / samba46.

-- 
You are receiving this mail because:
You are the assignee for the bug.


More information about the freebsd-ports-bugs mailing list