From: Stan Hoeppner on
Lars Bensmann put forth on 3/5/2010 7:12 PM:

> Thanks for the hint. I should have thought about this earlier. I did copy
> everything to one of the Windows 7 clients, set up a share and everything
> works fine. I really don't like this as a permanent solution but at least
> it's a (temporary?) workaround and it shows that it is indeed a Samba
> problem.

You're welcome. This is a great step to take and seems to confirm the
problem is indeed with Samba, or at least the version you're running, and
will hopefully help in nailing down exactly where the problem lies within Samba.

--
Stan
--
To unsubscribe from this list go to the following URL and read the
instructions: https://lists.samba.org/mailman/options/samba
From: Volker Lendecke on
On Sat, Mar 06, 2010 at 02:50:25PM +0100, Lars Bensmann wrote:
> And here are two new traces. One for the first client against Windows 7
> serving the files:
> http://almosthappy.de/duhLd6Tm1GQoC3j0YyiJ637IS/capture.win7.first_client (11MB)
> And then for the second client (although it does not have a noticable
> performance impact):
> http://almosthappy.de/duhLd6Tm1GQoC3j0YyiJ637IS/capture.win7.second_client (13MB)
>
> Unfortunately, I have no clue what I should be looking for in these
> traces.

Do you still have Windows XP around to serve files? The Win7
traces are naturally SMB2 which is not comparable to the
traces against Samba that only does SMB1.

You might also try the latest Samba code from git and enable
our experimental SMB2 support with "max protocol = smb2" and
see if it's also fast against that.

Volker
From: Lars Bensmann on
On Sun, Mar 07, 2010 at 08:49:49AM +0100, Volker Lendecke wrote:
> Do you still have Windows XP around to serve files? The Win7
> traces are naturally SMB2 which is not comparable to the
> traces against Samba that only does SMB1.

Unfortunately not. Would disabling SMB2 on Windows 7 be comparable?

> You might also try the latest Samba code from git and enable
> our experimental SMB2 support with "max protocol = smb2" and
> see if it's also fast against that.

I just checked out the git repository and compiled it. But I don't know
how to properly use upgrade_from_s3. I tried it with
# setup/upgrade_from_s3 /var/lib/samba /etc/samba/smb.conf
but I got the following error:
Reading Samba3 databases and smb.conf
Provisioning
No realm specified in smb.conf file, assuming 'PRAXIS'
Traceback (most recent call last):
File "setup/upgrade_from_s3", line 86, in <module>
targetdir=opts.targetdir)
File "bin/python/samba/upgrade.py", line 415, in upgrade_provision
serverrole=serverrole)
File "bin/python/samba/provision.py", line 1069, in provision
domainsid = security.dom_sid(domainsid)
TypeError: argument 1 must be string without null bytes, not str

I did not find any documentation for the script and the source code itself
also didn't give me any clues if I supplied the correct arguments.

I would really prefer using the upgrade script to provisioning a new user
database as this would probably mean I would have to change domains an all
clients when I want to switch back and forth between Samba 3 and 4.

Lars

--
Accept people for what they are -- completely unacceptable.
--
To unsubscribe from this list go to the following URL and read the
instructions: https://lists.samba.org/mailman/options/samba
From: Volker Lendecke on
On Sun, Mar 07, 2010 at 05:09:51PM +0100, Lars Bensmann wrote:
> On Sun, Mar 07, 2010 at 08:49:49AM +0100, Volker Lendecke wrote:
> > Do you still have Windows XP around to serve files? The Win7
> > traces are naturally SMB2 which is not comparable to the
> > traces against Samba that only does SMB1.
>
> Unfortunately not. Would disabling SMB2 on Windows 7 be comparable?

Sure. I just did not know how to do that...

> > You might also try the latest Samba code from git and enable
> > our experimental SMB2 support with "max protocol = smb2" and
> > see if it's also fast against that.
>
> I just checked out the git repository and compiled it. But I don't know
> how to properly use upgrade_from_s3. I tried it with
> # setup/upgrade_from_s3 /var/lib/samba /etc/samba/smb.conf

Well, we have SMB2 in 3.5.0 as well as experimental. No need
to go 4 :-)

Volker
From: Lars Bensmann on
On Sun, Mar 07, 2010 at 06:48:47PM +0100, Volker Lendecke wrote:
> On Sun, Mar 07, 2010 at 05:09:51PM +0100, Lars Bensmann wrote:
> > Unfortunately not. Would disabling SMB2 on Windows 7 be comparable?
>
> Sure. I just did not know how to do that...

That's what I found regarding disabling SMB2:
On clients:
sc config lanmanworkstation depend= bowser/mrxsmb10/nsi
sc config mrxsmb20 start= disabled

On the server:
HKLM\System\CurrentControlSet\Services\LanmanServer\Parameters
Value name: Smb2
Value type: REG_DWORD
0 = disabled
1 = enabled

To enable it again on the client:
sc config lanmanworkstation depend= bowser/mrxsmb10/mrxsmb20/nsi
sc config mrxsmb20 start= auto

I restarted the computers to be on the safe side.

The result:
http://almosthappy.de/duhLd6Tm1GQoC3j0YyiJ637IS/capture.win7.smb1.first_client (15MB)
http://almosthappy.de/duhLd6Tm1GQoC3j0YyiJ637IS/capture.win7.smb1.second_client (15MB)
(Where "second_client" means: The same computer but another client already
had the application open.)

There was no noticeble delay. So it does not seem to be related to SMB2.

> > I just checked out the git repository and compiled it. But I don't know
> > how to properly use upgrade_from_s3. I tried it with
> > # setup/upgrade_from_s3 /var/lib/samba /etc/samba/smb.conf
>
> Well, we have SMB2 in 3.5.0 as well as experimental. No need
> to go 4 :-)

I was a bit lazy and installed the packages from Debian experimental
(2:3.5.0dfsg-1). Unfortunately the upgrade made some problems. It kind of
worked, but the application did not. I was glad when I successfully
reverted all the changes. But as the problem does not seem to be SMB2
related, I did not persue this any further.

If it was helpful I could try again with 3.5.0 from the git repository.

Lars

--
Hard work often pays off after time, but laziness always pays off now.
-- Despair INC (http://www.despair.com/)
--
To unsubscribe from this list go to the following URL and read the
instructions: https://lists.samba.org/mailman/options/samba