Project

General

Profile

Actions
Copy link

Bug #55307

closed

bluefs fsync doesn't respect file truncate

Added by Igor Fedotov about 2 years ago. Updated 6 months ago.

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

0%

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

Description

So truncate + fsync sequence doesn't result in file's metadata update in BlueFS log.

Related issues 1 (0 open — 1 closed)

Copied to bluestore - Backport #57458: quincy: bluefs fsync doesn't respect file truncateResolvedIgor FedotovActions
Actions
Copy link
 #1

Updated by Igor Fedotov about 2 years ago

  • Status changed from New to Fix Under Review
  • Pull request ID set to 45883
Actions
Copy link
 #2

Updated by Igor Fedotov over 1 year ago

  • Status changed from Fix Under Review to Pending Backport
Actions
Copy link
 #3

Updated by Backport Bot over 1 year ago

  • Copied to Backport #57458: quincy: bluefs fsync doesn't respect file truncate added
Actions
Copy link
 #4

Updated by Backport Bot over 1 year ago

  • Tags set to backport_processed
Actions
Copy link
 #5

Updated by Igor Fedotov 6 months ago

  • Status changed from Pending Backport to Resolved
Actions
Copy link

Also available in: Atom PDF