Hello,
I saw this posting by Christopher Robert Woods. I am having the identical
problem with Samba on Suse Linux 7.2 (OS/390). Is there any known
workaround?
----------------------------------------------------------------------------
--------------------
To: Multiple recipients of list SAMBA <samba@samba.org>
Subject: Symantec Ghost and Samba
From: Christopher Robert Woods <woodsch@forum-financial.com>
Date: Thu, 1 Jun 2000 22:29:43 +1000
Reply-To: woodsch@forum-financial.com
Sender: samba@samba.org
Hello all. Trying to save the lone linux box in the organization. Any
help would be appreciated.
Our desktop support team makes extensive use of Symantec Ghost to make
images of NT desktops for recovery purposes. I managed to talk them into
using our lone linux server as the Ghost repository.
The way the process works is that you boot the about to be imaged machine
via a DOS boot disk, then run Ghost off of the network, and choose a drive
mapped to a share on the linux server as the destination for the ghost
image.
To any NT box, the average ghost time takes about 20 minutes. But to the
linux/samba machine doing the above takes an hour and a half!!
I am at a loss as to what to do. Copying a large file to the linux server
goes no slower than copying to an NT box. However Ghost just seems to
choke when writing to the Samba box.
Attached below is our smb.conf. Any thoughts would be much appreciated.
Please help me stop the EVIL desktop group from getting Linux
excommunicated from our NT network.
FWIW, the share that they are trying to connect to is either [Images] or
[Images1]. Both of which are on different physical drives.
THANKS!!
-------------------
[global]
workgroup = FFG
server string = Linux Profile Server
printcap name = /etc/printcap
load printers = yes
log file = /var/log/samba/log.%m
max log size = 50
security = share
socket options = TCP_NODELAY
local master = no
name resolve order = wins lmhosts bcast
wins server = 10.0.128.50
dns proxy = no
#============================ Share Definitions
[Profiles]
comment = Temporary space for Profiles
path = /ts/profiles
read only = no
public = yes
browseable = yes
[Images]
comment = Image Repository
path = /ts/images
read only = no
public = yes
browseable = yes
[Images1]
comment = 2nd Image Repository
path = /ts/images1
read only = no
public = yes
browseable = yes
[Logs]
comment = Syslog Logs
path = /var/log
read only = no
public = yes
browseable = yes
Brian Mays - CCNP
Director of Network Computing
Boscov's Department Store, LLC
3135 Marion Ave.
Laureldale, PA 19605
610-929-7312 (Phone)
610-929-7336 (Fax)
bmays@boscovs.com
At 09:16 AM 5/20/02 -0400, you wrote:>Hello, > >I saw this posting by Christopher Robert Woods. I am having the identical >problem with Samba on Suse Linux 7.2 (OS/390). Is there any known >workaround?I never managed to get a DOS bootable floppy to do this, in the end, I got a copy of NFSDOS, which works fabulously. I don't know the specifics of your situation, but I would be happy to send you an image of the two diskettes I use. I would appreciate a copy of the DOS bootable disk you use, as I would prefer to use the samba shares to nfs (if of course it doesn't slow the whole thing down as it is on yours). You may find that it is the DOS filesystem symantecs that are slowing samba down, although I can't understand why that would be. multitasking dos would enable you to see if it's client cpu, top on the samba server would show you if it's server cpu. -------------- Martyn Ranyard I am not a member of the samba team, and anything that I say may not be as accurate as a response from one of the team. I reply to save those more qualified time, which can more usefully be spent developing SAMBA further.
Try starting ghost with the -slowfile switch I've seem performance go from 2 MB / min to 100+ MB / min writing an image to a samba share. (seen with Ghost 5.1d / samba 2.2.4) Adam At 09:16 AM 5/20/2002 -0400, Brian Mays wrote:>Hello, > >I saw this posting by Christopher Robert Woods. I am having the identical >problem with Samba on Suse Linux 7.2 (OS/390). Is there any known >workaround? > >---------------------------------------------------------------------------- >-------------------- > >To: Multiple recipients of list SAMBA <samba@samba.org> >Subject: Symantec Ghost and Samba >From: Christopher Robert Woods <woodsch@forum-financial.com> >Date: Thu, 1 Jun 2000 22:29:43 +1000 >Reply-To: woodsch@forum-financial.com >Sender: samba@samba.org > >Hello all. Trying to save the lone linux box in the organization. Any >help would be appreciated. > >Our desktop support team makes extensive use of Symantec Ghost to make >images of NT desktops for recovery purposes. I managed to talk them into >using our lone linux server as the Ghost repository. > >The way the process works is that you boot the about to be imaged machine >via a DOS boot disk, then run Ghost off of the network, and choose a drive >mapped to a share on the linux server as the destination for the ghost >image. > >To any NT box, the average ghost time takes about 20 minutes. But to the >linux/samba machine doing the above takes an hour and a half!! > >I am at a loss as to what to do. Copying a large file to the linux server >goes no slower than copying to an NT box. However Ghost just seems to >choke when writing to the Samba box. > >Attached below is our smb.conf. Any thoughts would be much appreciated. >Please help me stop the EVIL desktop group from getting Linux >excommunicated from our NT network. > >FWIW, the share that they are trying to connect to is either [Images] or >[Images1]. Both of which are on different physical drives. > >THANKS!! > >------------------- >[global] > > workgroup = FFG > server string = Linux Profile Server > printcap name = /etc/printcap > load printers = yes > log file = /var/log/samba/log.%m > max log size = 50 > security = share > socket options = TCP_NODELAY > local master = no > name resolve order = wins lmhosts bcast > wins server = 10.0.128.50 > dns proxy = no > >#============================ Share Definitions > >[Profiles] > comment = Temporary space for Profiles > path = /ts/profiles > read only = no > public = yes > browseable = yes > >[Images] > comment = Image Repository > path = /ts/images > read only = no > public = yes > browseable = yes > >[Images1] > comment = 2nd Image Repository > path = /ts/images1 > read only = no > public = yes > browseable = yes > >[Logs] > comment = Syslog Logs > path = /var/log > read only = no > public = yes > browseable = yes > > > >Brian Mays - CCNP >Director of Network Computing >Boscov's Department Store, LLC >3135 Marion Ave. >Laureldale, PA 19605 >610-929-7312 (Phone) >610-929-7336 (Fax) >bmays@boscovs.com > > >-- >To unsubscribe from this list go to the following URL and read the >instructions: http://lists.samba.org/mailman/listinfo/samba
We do this but we have Mars, the netware server daemon running and it works great. On Mon, 2002-05-20 at 06:16, Brian Mays wrote:> Hello, > > I saw this posting by Christopher Robert Woods. I am having the identical > problem with Samba on Suse Linux 7.2 (OS/390). Is there any known > workaround? > > ---------------------------------------------------------------------------- > -------------------- > > To: Multiple recipients of list SAMBA <samba@samba.org> > Subject: Symantec Ghost and Samba > From: Christopher Robert Woods <woodsch@forum-financial.com> > Date: Thu, 1 Jun 2000 22:29:43 +1000 > Reply-To: woodsch@forum-financial.com > Sender: samba@samba.org > > Hello all. Trying to save the lone linux box in the organization. Any > help would be appreciated. > > Our desktop support team makes extensive use of Symantec Ghost to make > images of NT desktops for recovery purposes. I managed to talk them into > using our lone linux server as the Ghost repository. > > The way the process works is that you boot the about to be imaged machine > via a DOS boot disk, then run Ghost off of the network, and choose a drive > mapped to a share on the linux server as the destination for the ghost > image. > > To any NT box, the average ghost time takes about 20 minutes. But to the > linux/samba machine doing the above takes an hour and a half!! > > I am at a loss as to what to do. Copying a large file to the linux server > goes no slower than copying to an NT box. However Ghost just seems to > choke when writing to the Samba box. > > Attached below is our smb.conf. Any thoughts would be much appreciated. > Please help me stop the EVIL desktop group from getting Linux > excommunicated from our NT network. > > FWIW, the share that they are trying to connect to is either [Images] or > [Images1]. Both of which are on different physical drives. > > THANKS!! > > ------------------- > [global] > > workgroup = FFG > server string = Linux Profile Server > printcap name = /etc/printcap > load printers = yes > log file = /var/log/samba/log.%m > max log size = 50 > security = share > socket options = TCP_NODELAY > local master = no > name resolve order = wins lmhosts bcast > wins server = 10.0.128.50 > dns proxy = no > > #============================ Share Definitions > > [Profiles] > comment = Temporary space for Profiles > path = /ts/profiles > read only = no > public = yes > browseable = yes > > [Images] > comment = Image Repository > path = /ts/images > read only = no > public = yes > browseable = yes > > [Images1] > comment = 2nd Image Repository > path = /ts/images1 > read only = no > public = yes > browseable = yes > > [Logs] > comment = Syslog Logs > path = /var/log > read only = no > public = yes > browseable = yes > > > > Brian Mays - CCNP > Director of Network Computing > Boscov's Department Store, LLC > 3135 Marion Ave. > Laureldale, PA 19605 > 610-929-7312 (Phone) > 610-929-7336 (Fax) > bmays@boscovs.com > > > -- > To unsubscribe from this list go to the following URL and read the > instructions: http://lists.samba.org/mailman/listinfo/samba-- =================================================================George Farris Computer Support Cowichan farrisg@mala.bc.ca Malaspina University-College A conclusion is simply the place where you got tired of thinking. ------- Electronic Frontier Foundation http://www.eff.org -------