Bug#334430: [Pkg-db-devel] hangs on corrupted db file

[Adrian von Bidder]

Florian - thanks for your input!

On Monday 14 November 2005 22.51, Florian Weimer wrote:
> (BTW, the submitter isn't Cc:ed, is this correct?)
Right.  I guess he should've been...  And the postgrey mailing list, too.

> * Adrian von Bidder:
> > It's a case of db4.3 apparently hanging on corrupted database files,
> > despite DB_RECOVER being used on open.  Is this a known bug? 
> > Unfortunately, the bug report doesn't (yet) state what db version and
> > if the bug is reproducable.
>
> postgrey seems to use proper locking and DB_RECOVERY, so it *should*
> work.  But postgrey disables durable transactions:
>
>     my $setflags = DB_TXN_NOSYNC;
>
> On some file systems, this adversely impacts the consistency after
> system crashes.  It would be interesting to know what happens if the
> line is changed to:
>
>     my $setflags = 0;

David - might that be be a solution?  Although the documentation indicates 
that setting DB_TXN_NOSYNC shouldn't be dangerous...

Do you have any tool to drive postgrey with some test input so that I can 
quickly get a database of some size by testing?  Or perhaps Nick can test 
this?


greetings
-- vbi

-- 
featured link: http://fortytwo.ch/gpg/intro
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 388 bytes
Desc: not available
Url : http://lists.alioth.debian.org/pipermail/pkg-db-devel/attachments/20051115/65d06e13/attachment.pgp