Project

General

Profile

Bug #11507

object creation by write cannot use an offset on an erasure coded pool

Added by Loic Dachary over 3 years ago. Updated about 3 years ago.

Status:
Resolved
Priority:
Urgent
Assignee:
Category:
-
Target version:
-
Start date:
04/30/2015
Due date:
% Done:

0%

Source:
other
Tags:
Backport:
hammer, firefly
Regression:
No
Severity:
3 - minor
Reviewed:
Affected Versions:
ceph-qa-suite:

Description

Even if it is properly aligned. Otherwise it will crash the OSD.

https://github.com/ceph/ceph/pull/4508


Related issues

Duplicated by Ceph - Bug #11573: OSD assertion in erasure code environment Duplicate 05/08/2015 05/08/2015
Copied to Ceph - Backport #11744: object creation by write cannot use an offset on an erasure coded pool Resolved 04/30/2015
Copied to Ceph - Backport #11745: object creation by write cannot use an offset on an erasure coded pool Resolved 04/30/2015

Associated revisions

Revision a4f1256c (diff)
Added by Jianpeng Ma over 3 years ago

osd: refuse to write a new erasure coded object with an offset > 0

Even if the offset is properly aligned.

http://tracker.ceph.com/issues/11507 Fixes: #11507

Signed-off-by: Jianpeng Ma <>
Signed-off-by: Loic Dachary <>

Revision 8996907e (diff)
Added by Jianpeng Ma over 3 years ago

osd: refuse to write a new erasure coded object with an offset > 0

Even if the offset is properly aligned.

http://tracker.ceph.com/issues/11507 Fixes: #11507

Signed-off-by: Jianpeng Ma <>
Signed-off-by: Loic Dachary <>
(cherry picked from commit a4f1256c214ee0e7ebb91ac4ea8655f5d9642dc8)

Revision 8372f1d5 (diff)
Added by Jianpeng Ma over 3 years ago

osd: refuse to write a new erasure coded object with an offset > 0

Even if the offset is properly aligned.

http://tracker.ceph.com/issues/11507 Fixes: #11507

Signed-off-by: Jianpeng Ma <>
Signed-off-by: Loic Dachary <>
(cherry picked from commit a4f1256c214ee0e7ebb91ac4ea8655f5d9642dc8)

History

#3 Updated by Loic Dachary over 3 years ago

  • Status changed from Need Review to Pending Backport
  • Regression set to No

#4 Updated by Nathan Cutler about 3 years ago

  • Status changed from Pending Backport to Resolved

Also available in: Atom PDF