Project

General

Profile

Bugless #32

pg fuckup: merge owncloud

Added by q3k about 3 years ago. Updated almost 3 years ago.

Status:
Resolved
Priority:
High
Assignee:
Category:
-

Description

See #30 for background.

This is about the owncloud database. It will likely require manual merging, as it's actively used.


Related issues

Related to hswaw - Bugless #30: January boston-packets postgres fuckup cleanup, master trackerAssignedimplrActions
#1

Updated by q3k about 3 years ago

  • Status changed from Assigned to Accepted
#2

Updated by q3k about 3 years ago

  • Related to Bugless #30: January boston-packets postgres fuckup cleanup, master tracker added
#3

Updated by q3k almost 3 years ago

  1. Ran occ files:scan on owncloud to make sure there weren't any orphaned files in S3. This should've taken care of the filecache in postgres.
  2. Wrote a small script to ensure we're not missing shares/mounts: https://cs.hackerspace.pl/hscloud/-/commit/2f712bf53182f1d4776f7f3c2659c019a9c019e6 . The differences found are:
    1. Group folders that are missing per-user mounts (I'm checking with potentially affected users to see if there's anything wrong in their interface)
    2. A couple of shares that have just been removed in pg9 after rolling back.
  3. Manually checked most other tables for diffs (things like other apps, etc).

We seem to generally be fine, but let's keep the backup just in case. Closing once I confirm that 2.1. is okay with potentially affected users.

#4

Updated by q3k almost 3 years ago

  • Status changed from Accepted to Resolved

Turns out 2.1 is as expected, the mounts are missing now (but they are in PG12) because those shares are only for active members (in the starving or fatty groups), and the missing mounts are from people who are not members of these groups anymore.

All fine then, closing this. I've also updated Nextcloud to 21.

Also available in: Atom PDF