Project

General

Profile

Actions

Bug #37541

closed

[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 2 (0 open2 closed)

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

Updated by Mykola Golub over 5 years ago

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

Updated by Mykola Golub over 5 years ago

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

Updated by Jason Dillaman over 5 years ago

  • Status changed from Fix Under Review to Pending Backport
Actions #4

Updated by Nathan Cutler over 5 years ago

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

Updated by Nathan Cutler over 5 years ago

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

Updated by Nathan Cutler about 5 years ago

  • Status changed from Pending Backport to Resolved
Actions

Also available in: Atom PDF