digitalocean/pgremapper

Issues

• How to confirm that everything good after OSD reweight to 0.0 and purge after

  #53 opened 2 months ago by Badb0yBadb0y
  3

• pgremapper performance limit?

  #52 opened 2 months ago by k0ste
  5

• Cancel-backfill not progressing

  #51 opened 7 months ago by torkilt
  3

• remap: panic on source osd missing from up set

  #47 opened 8 months ago by Matt1360
  2

• `pgremapper version` does not have version data.

  #45 opened a year ago by robbat2
  0

• permit drain command to take multiple source OSDs

  #40 opened a year ago by robbat2
  4

• cancel-backfill distinguish between source and target

  #25 opened a year ago by stuartthebruce
  4

• detect a given pg belongs to an ec pool

  #33 opened 2 years ago by microyahoo
  1

• panic - multiple complete shards at index

  #27 opened 2 years ago by wyllys66
  6

• Install instructions

  #30 opened 2 years ago by jelka71
  1

• Have cancel-backfill undo conflicting upmaps

  #26 opened 2 years ago by CartCaved
  2

• drain host is not filling target OSDs evenly

  #23 opened 3 years ago by hydro-b
  3

• support for device-class

  #19 opened 3 years ago by scheuref
  6

• panic: pg 18.48: conflicting mapping(s) found when trying to map from 72 to 527

  #10 opened 3 years ago by timureh
  8

• panic runtime error index out of range [1] with length 1

  #14 opened 3 years ago by CartCaved
  17

• drain for source osdspec idea

  #9 opened 3 years ago by k0ste
  4

• min_compat_client warning is not handled by pgremapper

  #11 opened 3 years ago by k0ste
  1

• panic: pg 1.38f: conflicting mapping(s) found when trying to map from 66 to 19

  #5 opened 3 years ago by k0ste
  5

• proposal: report mode on dry-run by default

  #3 opened 3 years ago by k0ste
  2