Project

General

Profile

Bug #37541

[journal] max journal order is incorrectly set at 64

Added by Jason Dillaman over 5 years ago. Updated about 5 years ago.

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

0%

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

Description

RADOS cannot support an object of size "1<<64". This should have been configured to max out at 64MiB (or order 26).


Related issues

Copied to rbd - Backport #37900: mimic: [journal] max journal order is incorrectly set at 64 Resolved
Copied to rbd - Backport #37901: luminous: [journal] max journal order is incorrectly set at 64 Resolved

History

#1 Updated by Mykola Golub about 5 years ago

  • Status changed from New to In Progress
  • Assignee set to Mykola Golub

#2 Updated by Mykola Golub about 5 years ago

  • Status changed from In Progress to Fix Under Review
  • Pull request ID set to 25743

#3 Updated by Jason Dillaman about 5 years ago

  • Status changed from Fix Under Review to Pending Backport

#4 Updated by Nathan Cutler about 5 years ago

  • Copied to Backport #37900: mimic: [journal] max journal order is incorrectly set at 64 added

#5 Updated by Nathan Cutler about 5 years ago

  • Copied to Backport #37901: luminous: [journal] max journal order is incorrectly set at 64 added

#6 Updated by Nathan Cutler about 5 years ago

  • Status changed from Pending Backport to Resolved

Also available in: Atom PDF