On Tue, May 05, 2009 at 02:47:13PM +0100, Thomas Adam wrote:
> On Tue, May 05, 2009 at 03:40:15PM +0200, Volker Lendecke wrote:
> > On Tue, May 05, 2009 at 09:43:36AM +0100, Thomas Adam wrote:
> > Attaching strace to this process shows nothing -- literally, it's making
> > > no system calls whatsoever. Attaching gdb to this running process and
> > > using "next" reveals that it's doing the following:
> > >
> > > memcpy() -> tdb_read() -> tdb_find()
> > Very likely that is a corrupted tdb file, probably the
> > netsamlogon_cache.tdb. What kind of file system do you run
> > this on?
> This is in ext3.
Ok, this indicates that you're running on Linux.
> The particular file in question has an access time of Jan 23rd 2009. Are
> these files periodically removed by samba such as when it restarts, or are
> they somehow persistent? Certainly the timestamp on the
> netsamlogon_cache.tdb file suggests it's persistent. Are they meant to be
> cleared, even?
Linux has the problem that when writing to a file using
mmap, the mtime is not updated. netsamlogon_cache is a
persistent database that is not cleared, it's only
overwritten by new entries. But you can safely delete it
while Samba/winbind are shut down. If this happens
frequently, you might want to look at smbd or winbind
processes crashing hard and try to find more info on those,
or you might want to look at possibly flaky hardware.
To unsubscribe from this list go to the following URL and read the