Project

General

Profile

Actions

Bug #52730

closed

ceph-volume mis-calculates db/wal slot size for clusters that have multiple PVs in a VG

Added by Cory Snyder over 2 years ago. Updated over 2 years ago.

Status:
Resolved
Priority:
Normal
Assignee:
Target version:
% Done:

0%

Source:
Tags:
Backport:
pacific,octopus
Regression:
No
Severity:
3 - minor
Reviewed:
ceph-qa-suite:
Pull request ID:
Crash signature (v1):
Crash signature (v2):

Description

Prior to v15.2.8, ceph-volume was creating a single VG to contain multiple db/wal PVs. After v15.2.8, this was corrected so that each fast drive gets its own VG. The current logic for calculating db/wal slot sizes within ceph-volume makes the assumption that each PV has a single VG, and miscalculates required slot sizes on clusters where this isn't true. This can cause Ceph to "think" that there isn't enough space on db/wal drives to deploy new OSDs, when there actually is.


Related issues 2 (0 open2 closed)

Copied to ceph-volume - Backport #53277: octopus: ceph-volume mis-calculates db/wal slot size for clusters that have multiple PVs in a VGResolvedGuillaume AbriouxActions
Copied to ceph-volume - Backport #53278: pacific: ceph-volume mis-calculates db/wal slot size for clusters that have multiple PVs in a VGResolvedGuillaume AbriouxActions
Actions

Also available in: Atom PDF