TDB on OpenBSD problem
Jason Coene
jason at dhnw.net
Wed May 2 15:40:24 GMT 2001
Andrew and Jeremy,
I posted a response to Jeremy's origional inquiry (adding debug traces).
It seems the list did not get my message. Perhaps it was filtered for being
too large.
I have a log, and my debug source posted at
http://63.120.42.230/samba/report.txt.
Full log (38mb) available upon request, but it shouldent be necessary.
Notice the value of tdb->map_size jumping so sharply (seemingly doubling),
and lseek going along with it using lseek_val = (tdb->map_size+size-1).
lseek (fd, 536952831, SEEK_SET) = EEK!
Any idea why map size is doubling?
Jason Coene
### -----Original Message-----
### From: samba-technical-admin at lists.samba.org
### [mailto:samba-technical-admin at lists.samba.org]On Behalf Of
### tridge at samba.org
### Sent: Wednesday, May 02, 2001 8:58 AM
### To: jeremy at valinux.com
### Cc: jason at dhnw.net; crh at nts.umn.edu; samba-technical at samba.org
### Subject: Re: TDB on OpenBSD problem.
###
###
### > The code that causes a tdb to grow is in tdb_expand() in tdb/tdb.c.
### > Can you instrument this code with DEBUG level zeros to try and track
### > down what is causing the gig expansion. That level of expansion would
### > point to a bug in the interaction between tdb and mmap or fcntl.
###
### another thing to try is to disable mmap in tdb.c and see if that fixes
### it. If not then we should suspect a tdb logic bug - the non-mmap code
### is pretty portable.
###
###
More information about the samba-technical
mailing list