Re: Subversion DB corruption

How does Subversion handle the journalling of its own files? Does it use
fsync() to make sure that the data is flushed to the hard drive?

BTW, even doing this might not be enough when using IDE drives. There was a
thread about this issue in the PostgreSQL users list some time ago.

On Saturday 11 September 2004 12:58, kfogel@collab.net wrote:
> Mike Scott <mike@mikescommunity.com> writes:
> > The machine hung just after committing, so my guess is that there was
> > still unflushed data in the disk cache. I would have expected a
> > journalling system to ensure that it's journal update were flushed to
> > disk before making any changes to the data.
>
> I think what Max means is that something may have corrupted existing
> journal files. For example, no journaling file system (no matter how
> good) can recover from having its journal files themselves corrupted
> by a skipping disk head.
>
> (Obviously, we don't know exactly what happened with your machine, so
> it's hard to determine the likelihood that old data got blown away.)
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
> For additional commands, e-mail: users-help@subversion.tigris.org

-- 
Juan Jose Comellas
(juanjo@comellas.com.ar)
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org