On Fri, Jun 28, 2013 at 02:40:25PM +0000, Daniel Shahaf wrote:
> Should it print the top-most error or the bottom-most one?
>
> Here are some traces:
>
> svnadmin: SVN_ERR_FS_CORRUPT: Corrupt node-revision '2-1.0.r1/114'
> svnadmin: SVN_ERR_FS_CORRUPT: Found malformed header 'count 0' in revision file
>
> svnadmin: SVN_ERR_FS_CORRUPT: Corrupt representation '2 0 14 1 (null) adc83b19e793491b1c6ea0fd8b46cd9f32e592fc (null)'
> svnadmin: SVN_ERR_FS_CORRUPT: Malformed svndiff data in representation
>
> svnadmin: SVN_ERR_FS_CORRUPT: Filesystem is corrupt
> svnadmin: SVN_ERR_CHECKSUM_MISMATCH: Checksum mismatch while reading representation:
> expected: 2d2977d1c96f487abe4a1e202dd03b4f
> actual: 2d2977d1c96f487abe4a1e202dd03b4e
>
> svnadmin: SVN_ERR_ATOMIC_INIT_FAILURE: Couldn't open rep-cache database
> svnadmin: SVN_ERR_ATOMIC_INIT_FAILURE: Couldn't perform atomic initialization
> svnadmin: SVN_ERR_SQLITE_ERROR: sqlite: file is encrypted or is not a database (S26), executing statement 'PRAGMA synchronous=OFF;PRAGMA recursive_triggers=ON;'
Hmmm. Perhaps it should print the entire error chain every time.
Received on 2013-06-28 17:03:34 CEST