Skip to contentSkip to conversation

New: File's copied from client->linux server only copy 1st 64K data; rest is lost

Bugme-new Andrew Morton 3 participants 3 messages Apr 11, 2011 – Apr 12, 2011 3 messages not in the archive

Subsystems (4)
lore
Share & tools
lore
#1 lore raw
In reply to a message not in the archive

(switched to email. Please respond via emailed reply-to-all, not via the bugzilla web interface).

Quoted 17 lines · On Mon, 11 Apr 2011 22:12:41 GMT [email protected] wrote:

https://bugzilla.kernel.org/show_bug.cgi?id=33102

           Summary: File's copied from client->linux server only copy 1st
                    64K data;rest is lost
           Product: Networking
           Version: 2.5
    Kernel Version: 2.6.38.2
          Platform: All
        OS/Version: Linux
              Tree: Mainline
            Status: NEW
          Severity: blocking
          Priority: P1
         Component: IPV4
        AssignedTo: [email protected]
        ReportedBy: [email protected]
        Regression: Yes

Seems to be a 2.6.37->2.6.38 regression.

Quoted 37 lines

Created an attachment (id=54112)
--> (https://bugzilla.kernel.org/attachment.cgi?id=54112)
config file

I've run into a problem copying a 3.6M file from a Win7 client to the linux server via cifs.

Under 2.6.38.2, it only copies the first 64K (exactly) and the client gets a write error.

Using wireshark, in the success case, after the client sends the first 64K, the server response with 4 acks each advertising a Window size of ~48K, followed by an SMB packet acknowledging the first 64K, w/info:
"WRITE AndX Request, 65536 bytes".

In the fail case, the server responds with 4 acks, but in each of the 4 ACKS, it's advertising strange window sizes of 881, 1161, 1441 1721 and then responds with a faulty SMB packet w/info:
"[TCP Retransmission] Trans2 Response<unknown>"
Under the Trans2 section it says:

Subcommand: <Unknown> since request packet wasn't seen.

----

I originally upgraded from 2.6.35.7 -> 2.6.38.2 and encountered this prob, so successively tried the 26.35.7 config w/2.6.36, 37, 38 and finally 38.1 -- they all work.

The same config on 2.6.38.2 fails as described above.

Config attached.

#3 lore raw
In reply to a message not in the archive
Quoted 26 lines · Andrew Morton

(switched to email. Please respond via emailed reply-to-all, not via the bugzilla web interface).

Quoted 18 lines · On Mon, 11 Apr 2011 22:12:41 GMT bugzilla-daemon-590EEB7GvNiWaY/ihj7yzEB+6BGkLq…

https://bugzilla.kernel.org/show_bug.cgi?id=33102

           Summary: File's copied from client->linux server only copy 1st
                    64K data;rest is lost
           Product: Networking
           Version: 2.5
    Kernel Version: 2.6.38.2
          Platform: All
        OS/Version: Linux
              Tree: Mainline
            Status: NEW
          Severity: blocking
          Priority: P1
         Component: IPV4
        AssignedTo: shemminger-de/[email protected]
        ReportedBy: [email protected]
        Regression: Yes
Quoted 3 lines

Seems to be a 2.6.37->2.6.38 regression.

----------

Not exactly -- Please note -- I tried both 2.6.38(.0) and 2.6.38.1.

They both work.

#5 lore raw
In reply to a message not in the archive
Quoted 28 lines · Linda Walsh
Quoted 26 lines · Andrew Morton

(switched to email.  Please respond via emailed reply-to-all, not via the bugzilla web interface).

Quoted 19 lines · On Mon, 11 Apr 2011 22:12:41 GMT bugzilla-daemon-590EEB7GvNiWaY/ihj7yzEB+6BGkLq…

https://bugzilla.kernel.org/show_bug.cgi?id=33102

          Summary: File's copied from client->linux server only copy 1st 64K data;rest is lost
          Product: Networking
          Version: 2.5
   Kernel Version: 2.6.38.2
         Platform: All
       OS/Version: Linux
             Tree: Mainline
           Status: NEW
         Severity: blocking
         Priority: P1
        Component: IPV4
       AssignedTo: shemminger-de/[email protected]
       ReportedBy: [email protected]
       Regression: Yes

Quoted 7 lines
Quoted 3 lines

Seems to be a 2.6.37->2.6.38 regression.

----------

Not exactly -- Please note -- I tried both 2.6.38(.0) and 2.6.38.1.

They both work.

Any chance that we could get a wireshark trace of the failure?

https://wiki.samba.org/index.php/Capture_Packets

gives instructions. There may also be useful information on
network stack failures returned in the samba log
(often named smbd.log).

Signature · 3 lines
Thanks,

Steve