v21’s avatarv21’s Twitter Archive—№ 68,404

    1. CBDQ notice: apologies, the database crashed & corrupted itself. It doesn't seem possible to un-corrupt it, so I'm restoring from a backup. This will mean any edits since 7am GMT are lost, and some replies will send twice. My apologies.
  1. …in reply to @v21
    hm! i'm not having a great time with this - seems like it was already corrupted (but running fine) at 7am. think my best option is to roll all the way back to Sunday (the last previous backup)? very sorry about this!!
    1. …in reply to @v21
      if there are any MySQL experts out there... this is what i'm seeing when it tries to start. setting innodb_force_recovery=6 gets it to start, but it still crashes when attempting to dump the database to restore properly...
      1. …in reply to @v21
        okay, successfully restored to Sunday & back up live. apologies for the downtime & the data loss!!!