SAMBA_2_2 creates huge connections.tdb

root lists at gecko.math.ualberta.ca
Wed Mar 14 21:30:22 GMT 2001


i posted something about this before, but heard nothing back. i have an
OpenBSD server that seems to do something like dumping core fairly
frequently. for whatever reason, connections.tdb will suddenly begin to
grow at about 1.1MB/s until it consumes all available disk space. below
are the machine's dmesg and smb.conf.  (/dist is mounted read-only)

i thought that this might be related to the os (i first noticed it on an
hp/ux machine) or the version of code (snapshot tarball versus cvs grab)
but it's not. both hp/ux and openbsd display this behaviour.

suggestions?

########################################################################
[global]
	workgroup = MADMIN
	netbios name = DISTRIBUTOR
	security = SHARE
	log level = 1
	syslog = 0
	announce version = 5.0
	dns proxy = No
	kernel oplocks = No
	guest account = browser
	hosts allow = 172.25.206. 172.25.207. 127

[cdrom]
	path = /cdrom
	username = browser
	read only = Yes
	guest only = Yes
	guest ok = Yes
	hosts allow = 172.25.206. 172.25.207. 127
	fake oplocks = Yes

[install]
	path = /dist
	username = browser
	read only = Yes
	guest only = Yes
	guest ok = Yes
	hosts allow = 172.25.206. 172.25.207. 127
	fake oplocks = Yes

####################################################################

OpenBSD 2.8-current (KAITAIN) #0: Fri Mar  9 13:17:58 MST 2001
    root at kaitain:/sys/arch/i386/compile/KAITAIN
cpu0: F00F bug workaround installed
cpu0: Intel Pentium/MMX ("GenuineIntel" 586-class) 200 MHz
cpu0: FPU,V86,DE,PSE,TSC,MSR,MCE,CX8,MMX
real mem  = 133808128 (130672K)
avail mem = 122056704 (119196K)
using 1659 buffers containing 6795264 bytes (6636K) of memory
mainbus0 (root)
bios0 at mainbus0: AT/286+(6c) BIOS, date 07/08/98, BIOS32 rev. 0 @ 0xf0400
pcibios0 at bios0: rev. 2.1 @ 0xf0000/0xa22
pcibios0: PCI IRQ Routing Table rev. 1.0 @ 0xf09b0/112 (5 entries)
pcibios0: PCI Interrupt Router at 000:07:0 (vendor 0x8086 product 0x122e rev 0x00)
pcibios0: PCI bus #0 is the last bus
bios0: ROM list: 0xc0000/0x8000
pci0 at mainbus0 bus 0: configuration mode 1 (bios)
pchb0 at pci0 dev 0 function 0 vendor 0x8086 product 0x1250 rev 0x03
pcib0 at pci0 dev 7 function 0 vendor 0x8086 product 0x7000 rev 0x01
pciide0 at pci0 dev 7 function 1 vendor 0x8086 product 0x7010 rev 0x00: DMA, channel 0 wired to compatibility, channel 1 wired to compatibility
atapiscsi0 at pciide0 channel 0
scsibus0 at atapiscsi0: 2 targets
cd0 at scsibus0 targ 1 lun 0: <E-IDE, CD-ROM 52X/AKH, T5B> SCSI0 5/cdrom removable
wd0 at pciide0 channel 0 drive 0: <Maxtor 71084 A>
wd0: 16-sector PIO, LBA, 1036MB, 2105 cyl, 16 head, 63 sec, 2122780 sectors
pciide0: channel 0 interrupting at irq 14
wd0(pciide0:0:0): using PIO mode 4, DMA mode 2
cd0(pciide0:0:1): using PIO mode 0, DMA mode 1
wd1 at pciide0 channel 1 drive 0: <Maxtor 53073H6>
wd1: 16-sector PIO, LBA, 29311MB, 16383 cyl, 16 head, 63 sec, 60030432 sectors
pciide0: channel 1 interrupting at irq 15
wd1(pciide0:1:0): using PIO mode 4, DMA mode 2
vga1 at pci0 dev 11 function 0 vendor 0x102b product 0x0519 rev 0x01
wsdisplay0 at vga1: console (80x25, vt100 emulation)
wsdisplay0: screen 1-5 added (80x25, vt100 emulation)
xl0 at pci0 dev 12 function 0 vendor 0x10b7 product 0x9055 rev 0x30: irq 11 address 00:10:5a:9c:91:94
exphy0 at xl0 phy 24: 3Com internal media interface
isa0 at pcib0
isadma0 at isa0
pckbc0 at isa0 port 0x60/5
pckbd0 at pckbc0 (kbd slot)
pckbc0: using irq 1 for kbd slot
wskbd0 at pckbd0: console keyboard, using wsdisplay0
npx0 at isa0 port 0xf0/16: using exception 16
biomask c000 netmask c800 ttymask c802
pctr: 586-class performance counters and user-level cycle counter enabled
root on wd0a
rootdev=0x0 rrootdev=0x300 rawdev=0x302

-- 
Chris Kuethe:  System Administrator  -   U of A Math Dept.

cell: 780.903.9475                    office: CAB553, 780.492.1704    
wargames@{edmc.net,hackcanada.com}    ckuethe@[[gecko.]math.]ualberta.ca

Opinions expressed herein are solely the responsibility of
the author. And the author wouldn't have it any other way.





More information about the samba-technical mailing list