m...@netbsd.org (Emmanuel Dreyfus) writes:
>But how does a "too large to flush" transaction can appear in the first
>place?
Currently there is the assumption that the guess for the journal size
(based on disk size but limited to 64MB) is good enough to handle all
possible transactions. But that's no guarantee.
On the other hand you need very large (possibly sparse?) files
to generate huge transactions. Did you try to remove or truncate
such a file?
--
--
Michael van Elst
Internet: mlel...@serpens.de
"A potential Snark may lurk in every tree."
