On Tue, Nov 15, 2005 at 08:42:50PM +1100, Andrew Bartlett wrote:
> On Tue, 2005-11-15 at 06:54 +0100, Christian Perrier wrote:
> > > Zeus:/var/log/samba# tail /var/log/samba/log.smbd
> > > smbd version 3.0.14a-Debian started.
> > > Copyright Andrew Tridgell and the Samba Team 1992-2004
> > > [2005/11/14 19:46:20, 0] tdb/tdbutil.c:tdb_log(725)
> > > tdb(/var/cache/samba/printing/HP895cxi.tdb): rec_free_read bad
> > > magic 0xfee1dead at offset=27920

> > Have you tried deleting that specific file?

> > Such problem already happened to me on a heavy duty print server in
> > unclear conditions and it turned out that deleting this apparently
> > broken tdb file fixed the problem.

> > However, please save it before and send it to this bug
> > report. Upstream might have some use for it to debug what caused the
> > problem.

> Only if you can say the file has not been affected by abnormal program
> termination (kill -9, power failure or the like), or if you have a segv
> backtrace.

Are corrupted tdbs that result from abnormal program termination not
considered bugs by the Samba team?  If so, I guess I need to reconsider the
question of whether Debian should be providing automated backups of those
.tdb files that are used for storing persistent program state
(group_mapping.tdb, secrets.tdb,...).

If it's just a matter of "yes, there's a bug, but having the file won't help
us find it", I can understand that.

-- 
Steve Langasek                   Give me a lever long enough and a Free OS
Debian Developer                   to set it on, and I can move the world.
[EMAIL PROTECTED]                                   http://www.debian.org/

Attachment: signature.asc
Description: Digital signature

Reply via email to