headers
Tom Peters | 1 Apr 2006 03:02

Re: 3.0.21c and big wmv or mpg files

At 10:40 PM 3/29/2006 +0200, you wrote:
>Hi  <at> all,
>
>are there any problems known with 3.0.21c and bigger video files (mpg and 
>wmv greater than 700 MB)?
>
>Received the information that these files cannot copied from XP to Samba 
>(W2K is okay). Error message is the well known:
>
>[2006/03/28 18:03:36, 0] lib/util_sock.c:get_peer_addr(1225)getpeername 
>failed. Error was Transport endpoint is not connected

I chased this elusive problem for a year. I'm still running 3.09-2.3 but I 
see it on other versions.

Tell me, do you get this problem when you drag/n/drop a file into a folder 
on the samba share? And can you prevent this problem from occurring by the 
following procedure?

Click in the target window on the samba machine (this is on the XP 
desktop). Press F5 to refresh the view. Wait about a second. Immediately 
start your copy. When I do this, the errors, previously reported to the 
desktop and to my server log, don't occur.

I've been told that it's a WinXP only issue, that it attempts to connect on 
ports 445 and 139 nearly simultaneously, and then proceeds to talk over 
whichever one answers first. I'm told that Win2k clients won't have this 
problem, and Win98 clients don't use port 445 so it doesn't arise there.

Anyone have evidence to the contrary (so far)?
(Continue reading)

Permalink | Reply |
headers
Thomas Bork | 1 Apr 2006 15:15
Picon

Re: 3.0.21c and big wmv or mpg files

Tom Peters wrote:

> Tell me, do you get this problem when you drag/n/drop a file into a 
> folder on the samba share? And can you prevent this problem from 
> occurring by the following procedure?

I cannot see the problem here but heared from 2 users of 3.0.21c with 
this problem.

Downloaded a file with 843 MB which reproducable triggered the error by 
one of the users - but not on my system.

We are using the _same_ samba version (built by me) on the same 
distribution:

http://www.eisfair.org/
http://www.pack-eis.de/index.php?p=samba

I'm the maintainer of this samba package and therefore interested in to 
correct this.

> Click in the target window on the samba machine (this is on the XP 
> desktop). Press F5 to refresh the view. Wait about a second. Immediately 
> start your copy. When I do this, the errors, previously reported to the 
> desktop and to my server log, don't occur.

The user copies the file with:

- right click to the local file and 'copy'
- right click in the share and 'insert'
(Continue reading)

Permalink | Reply |
headers
Tom Peters | 3 Apr 2006 02:51

Re: 3.0.21c and big wmv or mpg files

At 03:15 PM 4/1/2006 +0200, Thomas Bork wrote:
>Tom Peters wrote:
>
>>Tell me, do you get this problem when you drag/n/drop a file into a 
>>folder on the samba share? And can you prevent this problem from 
>>occurring by the following procedure?
>
>I cannot see the problem here but heared from 2 users of 3.0.21c with this 
>problem.
>
>Downloaded a file with 843 MB which reproducable triggered the error by 
>one of the users - but not on my system.
>
>We are using the _same_ samba version (built by me) on the same distribution:
>
>http://www.eisfair.org/
>http://www.pack-eis.de/index.php?p=samba
>
>I'm the maintainer of this samba package and therefore interested in to 
>correct this.
>
>>Click in the target window on the samba machine (this is on the XP 
>>desktop). Press F5 to refresh the view. Wait about a second. Immediately 
>>start your copy. When I do this, the errors, previously reported to the 
>>desktop and to my server log, don't occur.
>
>The user copies the file with:
>
>- right click to the local file and 'copy'
>- right click in the share and 'insert'
(Continue reading)

Permalink | Reply |
headers
Thomas Bork | 5 Apr 2006 23:16
Picon

Re: 3.0.21c and big wmv or mpg files

Tom Peters wrote:

>> While copying the wmv test file a have a cpu utilization of 95! 
>> percent (top) of smbd at the time, samba creates the sparse (?) file 
>> in the size needed for the test file.
> I don't believe this happens in my case. I am not certain. I know that 
> when it fails, Windows clients see a 0 bytes file with the name of the 
> destination in the target share. You have to erase or overwrite it when 
> you try again.

The high cpu utilization in our test case is caused of using quotas and 
an correspondending entry in smb.conf:

strict allocate = yes

Received a partially log from a user with a lot of

[2006/04/05 16:51:58, 3] smbd/error.c:error_packet(146)
   error packet at smbd/notify.c(55) cmd=160 (SMBnttrans) NT code 0x0000010c

>> Maybe this is problematical on smaller systems. Samba is running here 
>> on an VMWARE on top of XP (the test client) with P4 3,2 GHz:

One user tested without

strict allocate = yes

and can copy the file now.
Another user tested with more memory in his machine (celeron 1GHz, at 
first with 128 MB, then with 512 MB) and with
(Continue reading)

Permalink | Reply |
headers
Jeremy Allison | 6 Apr 2006 06:58
Picon
Favicon

Re: 3.0.21c and big wmv or mpg files

On Wed, Apr 05, 2006 at 11:16:09PM +0200, Thomas Bork wrote:
> Tom Peters wrote:
> 
> >>While copying the wmv test file a have a cpu utilization of 95! 
> >>percent (top) of smbd at the time, samba creates the sparse (?) file 
> >>in the size needed for the test file.
> >I don't believe this happens in my case. I am not certain. I know that 
> >when it fails, Windows clients see a 0 bytes file with the name of the 
> >destination in the target share. You have to erase or overwrite it when 
> >you try again.
> 
> The high cpu utilization in our test case is caused of using quotas and 
> an correspondending entry in smb.conf:
> 
> strict allocate = yes
> 
> Received a partially log from a user with a lot of
> 
> [2006/04/05 16:51:58, 3] smbd/error.c:error_packet(146)
>   error packet at smbd/notify.c(55) cmd=160 (SMBnttrans) NT code 0x0000010c
> 
> >>Maybe this is problematical on smaller systems. Samba is running here 
> >>on an VMWARE on top of XP (the test client) with P4 3,2 GHz:
> 
> One user tested without
> 
> strict allocate = yes
> 
> and can copy the file now.
> Another user tested with more memory in his machine (celeron 1GHz, at
(Continue reading)

Permalink | Reply |
headers
Thomas Bork | 6 Apr 2006 21:10
Picon

Re: 3.0.21c and big wmv or mpg files

Jeremy Allison wrote:

> Well you know what "strict allocate" does, right ? It causes the space
> for the file to be allocated on disk once the "set fil allocation" is
> set from the Windows client. If the client then writes this data it'll
> write everything twice. Why are you setting this ? You should not need
> to set this in production unless you have some very specific needs.

The official documentation says:

"Setting this to yes can help Samba return out of quota messages on 
systems that are restricting the disk quota of users."

This is suggesting me, that

strict allocate = yes

is the recommended setting for systems with quotas. That seems not the 
case...

der tom
--

-- 
To unsubscribe from this list go to the following URL and read the
instructions:  https://lists.samba.org/mailman/listinfo/samba
Permalink | Reply |
headers
Jeremy Allison | 6 Apr 2006 21:22
Picon
Favicon

Re: 3.0.21c and big wmv or mpg files

On Thu, Apr 06, 2006 at 09:10:44PM +0200, Thomas Bork wrote:
> Jeremy Allison wrote:
> 
> >Well you know what "strict allocate" does, right ? It causes the space
> >for the file to be allocated on disk once the "set fil allocation" is
> >set from the Windows client. If the client then writes this data it'll
> >write everything twice. Why are you setting this ? You should not need
> >to set this in production unless you have some very specific needs.
> 
> The official documentation says:
> 
> "Setting this to yes can help Samba return out of quota messages on 
> systems that are restricting the disk quota of users."
> 
> This is suggesting me, that
> 
> strict allocate = yes
> 
> is the recommended setting for systems with quotas. That seems not the 
> case...

No, it is the case in that it will allow some (broken) Windows applications to get 
"disk full" messages at open time, rather than at write or close time. It shouldn't
(IMHO) be generically turned on just because you're using quotas unless you've
got specific need for it.

Just my 2 cents.

Jeremy.
--

--
(Continue reading)

Permalink | Reply |
headers
Doug VanLeuven | 1 Apr 2006 06:20
Favicon

Re: 3.0.21c and big wmv or mpg files

Tom Peters wrote:
> At 10:40 PM 3/29/2006 +0200, you wrote:
>> Hi  <at> all,
>>
>> are there any problems known with 3.0.21c and bigger video files (mpg 
>> and wmv greater than 700 MB)?
>>
>> Received the information that these files cannot copied from XP to 
>> Samba (W2K is okay). Error message is the well known:
>>
>> [2006/03/28 18:03:36, 0] 
>> lib/util_sock.c:get_peer_addr(1225)getpeername failed. Error was 
>> Transport endpoint is not connected
> 
> I chased this elusive problem for a year. I'm still running 3.09-2.3 but 
> I see it on other versions.
> 
> Tell me, do you get this problem when you drag/n/drop a file into a 
> folder on the samba share? And can you prevent this problem from 
> occurring by the following procedure?
> 
> Click in the target window on the samba machine (this is on the XP 
> desktop). Press F5 to refresh the view. Wait about a second. Immediately 
> start your copy. When I do this, the errors, preterviously reported to the 
> desktop and to my server log, don't occur.
> 
> I've been told that it's a WinXP only issue, that it attempts to connect 
> on ports 445 and 139 nearly simultaneously, and then proceeds to talk 
> over whichever one answers first. I'm told that Win2k clients won't have 
> this problem, and Win98 clients don't use port 445 so it doesn't arise
(Continue reading)

Permalink | Reply |

Gmane