The (Almost) Great KDE Disaster Of 2013

tlu · Mar 26, 2013

http://www.phoronix.com/scan.php?page=news_item&px=MTMzNTc

There was almost "The Great KDE Disaster Of 2013" when the KDE project almost lost all of their 1,500+ Git repositories.

Last week the virtual machine running git.kde.org was taken down for security updates. When the host came back up, which handles the 1,500+ Git repositories for the project, there was EXT4 file-system corruption. The KDE back-up system mirrors the Git trees of this server, but it turns out that these mirrors were also pulling in the corrupted Git repositories.
Click to expand...

More details on

http://jefferai.org/2013/03/24/too-perfect-a-mirror/

and

http://jefferai.org/2013/03/24/screw-the-mirrors/

but at least:

I forgot to mention that we actually have tarballs of every single repository, updated every couple of days and also transferred to the anongits. These are not full, true mirrors of the repositories, simply normal clones, and they’re designed to make it easier for our contributors or users in low-bandwidth environments to fetch initial clones. They don’t contain our full repository metadata, so we would have lost all of that. And it’s not a perfect backup strategy by any means, as I’ll detail below. But it’s something.
Click to expand...

NGRhodes · Mar 27, 2013

There was a bit about not being able to back up git due to the commit activity, but I thought all commits are transactional in git, which means any partial transactions would be rolled back on restore of the backup.
The corrupt commit objects is worrying though and does not seem to be any follow up on how/why they occur.

Cheers, Nick

Log in or Sign up

The (Almost) Great KDE Disaster Of 2013

tlu Guest

NGRhodes Registered Member

Log in or Sign up

The (Almost) Great KDE Disaster Of 2013

tlu Guest

NGRhodes Registered Member

Useful Searches