Page 1 of 5 123 ... LastLast
Results 1 to 10 of 41

Thread: KDE Almost Lost All Of Their Git Repositories

  1. #1
    Join Date
    Jan 2007
    Posts
    15,438

    Default KDE Almost Lost All Of Their Git Repositories

    Phoronix: KDE Almost Lost All Of Their Git Repositories

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

    http://www.phoronix.com/vr.php?view=MTMzNTc

  2. #2
    Join Date
    Dec 2011
    Posts
    74

    Default Poor funkSTAR

    Quote Originally Posted by phoronix View Post
    Phoronix: KDE Almost Lost All Of Their Git Repositories

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

    http://www.phoronix.com/vr.php?view=MTMzNTc
    funkSTAR was THIS CLOSE to getting everything he ever wanted!

    Actually, while it would have been a huge PITA, there are enough out-of-repository copies of the source floating around so that I'm sure they could have rebuilt the repos to at least the last-released state of the code base. Still not good, but not lost forever either.

  3. #3

    Default

    Yeah, Linux and Open Source are shaky.

    In fact I had an ext4 corruption on a partition I mount RO daily and remount RW maybe once a week to write a file or two.

  4. #4
    Join Date
    Mar 2012
    Posts
    52

    Default

    Go suck horse cocks with your mother, birdie!

    DO NOT FEED THE TROLL PLEASE

  5. #5

    Default

    This is the silent corruption that ZFS was created to prevent. Unfortunately, KDE's servers were not using it.

  6. #6

    Default

    Quote Originally Posted by ryao View Post
    This is the silent corruption that ZFS was created to prevent. Unfortunately, KDE's servers were not using it.
    The real problem KDE sysadms overlooked is that mirroring is not backing up. ZFS wouldn't have saved them if their HDDs totally failed - ZFS is good at spotting hardware errors - that's true. But ZFS is not a magic bullet.

  7. #7

    Default

    Quote Originally Posted by birdie View Post
    The real problem KDE sysadms overlooked is that mirroring is not backing up. ZFS wouldn't have saved them if their HDDs totally failed - ZFS is good at spotting hardware errors - that's true. But ZFS is not a magic bullet.
    It is possible that the backups themselves would have been corrupted had the administrators been doing proper backups and these issues predated the fsck. In this situation, silent corruption caused a problem occurred because there was no way to recover after its effects had been felt.

    ZFS is not a replacement for proper backups, but it makes doing them easier. End-to-end checksumming and self-healing would have prevented this mess before it happened had ZFS been deployed.
    Last edited by ryao; 03-25-2013 at 03:44 PM.

  8. #8
    Join Date
    Aug 2012
    Location
    Pennsylvania, United States
    Posts
    1,921

    Default

    Quote Originally Posted by phoronix View Post
    Phoronix: KDE Almost Lost All Of Their Git Repositories

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

    http://www.phoronix.com/vr.php?view=MTMzNTc
    DO NOT COMMENT ON THIS THREAD UNLESS YOU READ BOTH THE BLOG POST AND THE FOLLOWUP. A lot of questions get answered in both that michael skimmed over or didn't mention.

  9. #9

    Default

    Quote Originally Posted by Ericg View Post
    DO NOT COMMENT ON THIS THREAD UNLESS YOU READ BOTH THE BLOG POST AND THE FOLLOWUP. A lot of questions get answered in both that michael skimmed over or didn't mention.
    I've read both - they didn't have proper backups. Period.

  10. #10

    Default

    Quote Originally Posted by birdie View Post
    I've read both - they didn't have proper backups. Period.
    Unfortunately, proper backups would not have helped as much as one would think without a way to know whether or not the data was bad prior to doing them. It is not clear when the repositories became corrupted, although the blog post suggests that fsck was the trigger.

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •