Displaying 5 results from an estimated 5 matches for "smbwritebraw".
1998 Jul 27
1
Slowdown when copying large files (PR#8624)
tl@fairplay.no wrote:
> Hmm, I missed the original post, but this sounds like it could be the bug
> I reported 15 days ago to samba-bugs (PR#8316) and still haven't got any
> responses to.
>
Sorry, I'm still integrating incoming patches.
> If it's the same bug it's mainly the write performance that's bad, and in
> reality the performance is worse than
1998 Jun 04
1
Slow writes continued
...s only seems to affect Win95
clients (NT machines are fine). Doing a write of a 20mb file to the server
generates the following message:
chdir to /int-data/amx_resources
1998/06/04 14:58:49 write fnum=56 cnum=119 num=16 wrote=16
1998/06/04 14:58:49 Transaction 10834 of length 65539
switch message SMBwritebraw (pid 1646)
chdir to /
chdir to /int-data/amx_resources
1998/06/04 14:58:49 writebraw1 fnum=56 cnum=119 start=19922944 num=65475
wrote=6
5475 sync=0
1998/06/04 14:58:49 writebraw2 fnum=56 cnum=119 start=19922944 num=45
wrote=6552
0
1998/06/04 14:58:49 Transaction 10835 of length 68
switch message SM...
1999 Apr 13
0
Printers now don't work - what can I check?
...trans2 call
[1999/04/13 12:37:20, 3] smbd/error.c:error_packet(138)
error packet at line 2129 cmd=50 (SMBtrans2) eclass=2 ecode=1
[1999/04/13 12:37:20, 3] smbd/process.c:process_smb(565)
Transaction 676 of length 4160
[1999/04/13 12:37:20, 3] smbd/process.c:switch_message(402)
switch message SMBwritebraw (pid 1042)
[1999/04/13 12:37:20, 3] smbd/reply.c:reply_writebraw(2254)
writebraw1 fnum=4160 start=0 num=4096 wrote=4096 sync=0
[1999/04/13 12:37:20, 3] smbd/reply.c:reply_writebraw(2300)
writebraw2 fnum=4160 start=0 num=2108 wrote=6204
[1999/04/13 12:37:20, 3] smbd/process.c:process_smb(565)...
2003 Dec 01
0
No subject
...t; samba server and winME client.
>
> >From what I read in samba-technical, this doesn't seem to depend on the
> server machine or OS, just the samba stuff and some interaction with 98/ME
> and apparently 2000 in my testing.
That's interesting. The rabbit pellet fix was for SMBwritebraw,
where Win98 needed a SMBkeepalive sent after the last raw write
packet to force the tcp ack.
For readbraw this shouldn't be needed as the last reply packet
from the server will contain the current tcp stream ack number.
A tcp packet trace would be most welcome.
Jeremy.
--
----------------...
2003 Nov 27
2
File corrupted when copy one large file(10G) from NT4.0 to samba
Hi All,
When I copied one file from NT4.0 to Linux through samba with 'copy'
command in NT4.0, the file was always corrupted. Size of the file copied
into Linux was always about 4G. If I copied it through Windows Explorer,
it was OK. It seems samba cannot process the "Write Raw" request sent by
'copy' command correctly when file size is larger than 4G bytes. Thanks