Project

General

Profile

Actions
Copy link

Bug #55307

closed

bluefs fsync doesn't respect file truncate

Added by Igor Fedotov almost 4 years ago. Updated 8 months ago.

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

0%

Source:
Backport:
quincy
Regression:
No
Severity:
3 - minor
Reviewed:
Affected Versions:
ceph-qa-suite:
Pull request ID:
45883
Tags (freeform):
Merge Commit:
747d1d39bba8d81c830db40cfd612cb97f318860
Fixed In:
v17.0.0-14830-g747d1d39bba
Released In:
v18.2.0~1390
Upkeep Timestamp:
2025-07-14T00:38:40+00:00

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 almost 4 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 3 years ago

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

Updated by Upkeep Bot over 3 years ago

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

Updated by Igor Fedotov over 2 years ago

  • Status changed from Pending Backport to Resolved
Actions
Copy link
 #6

Updated by Upkeep Bot 8 months ago

  • Merge Commit set to 747d1d39bba8d81c830db40cfd612cb97f318860
  • Fixed In set to v17.0.0-14830-g747d1d39bba
  • Released In set to v18.2.0~1390
  • Upkeep Timestamp set to 2025-07-14T00:38:40+00:00
Actions
Copy link

Also available in: Atom PDF