Project

General

Profile

Actions

Bug #70919

closed

fs/misc/multiple_rsync.sh: unhandled write error (2) No such file or directory, force readonly

Added by Venky Shankar 11 months ago. Updated 3 days ago.

Status:
Resolved
Priority:
Normal
Category:
Correctness/Safety
Target version:
% Done:

0%

Source:
Q/A
Backport:
reef,squid
Regression:
No
Severity:
3 - minor
Reviewed:
Affected Versions:
ceph-qa-suite:
Component(FS):
MDS
Labels (FS):
Pull request ID:
Tags (freeform):
backport_processed
Fixed In:
v20.0.0-1803-g6c01b91860
Released In:
v20.2.0~492
Upkeep Timestamp:
2026-03-18T03:13:32+00:00

Description

Two failures from the test branch
- https://pulpito.ceph.com/vshankar-2025-04-08_07:04:57-fs-wip-vshankar-testing-20250407.170244-debug-testing-default-smithi/8230745/
- https://pulpito.ceph.com/vshankar-2025-04-08_07:04:57-fs-wip-vshankar-testing-20250407.170244-debug-testing-default-smithi/8230864/

./remote/smithi131/log/20b5d0c4-1506-11f0-bb9e-bd4984dce30f/ceph-mds.b.log.gz

2025-04-09T06:10:34.056+0000 7f4add6ae640 10 mds.0.log finish: ls=LogSegment(83280/0xbd05009~bd4ae46 events=133), r=-2
2025-04-09T06:10:34.056+0000 7f4add6ae640 -1 mds.0.14 unhandled write error (2) No such file or directory, force readonly...
2025-04-09T06:10:34.056+0000 7f4add6ae640  1 mds.0.cache force file system read-only
2025-04-09T06:10:34.056+0000 7f4add6ae640  0 log_channel(cluster) log [WRN] : force file system read-only
2025-04-09T06:10:34.056+0000 7f4add6ae640 10 mds.0.server force_clients_readonly

errno -2 (ENOENT) was hit when expiring loges LogSegment(83280/0xbd05009~bd4ae46 events=133). Didn't debug further and the failure wan't seen in subsequent runs and the PRs under test doesn't seem to be related to the failure. Need RCA.


Related issues 3 (0 open3 closed)

Related to Ceph QA - QA Run #70819: wip-vshankar-testing-20250407.170244-debugQA ClosedVenky ShankarActions
Copied to CephFS - Backport #71092: reef: fs/misc/multiple_rsync.sh: unhandled write error (2) No such file or directory, force readonlyResolvedPatrick DonnellyActions
Copied to CephFS - Backport #71093: squid: fs/misc/multiple_rsync.sh: unhandled write error (2) No such file or directory, force readonlyResolvedPatrick DonnellyActions
Actions #1

Updated by Venky Shankar 11 months ago

  • Related to QA Run #70819: wip-vshankar-testing-20250407.170244-debug added
Actions #2

Updated by Milind Changire 11 months ago

Actions #3

Updated by Venky Shankar 11 months ago

Milind Changire wrote in #note-2:

@Venky Shankar have you put mds: add ref counting to LogSegment to test yet ?

Not yet. I left some review comment on that PR and waiting for an update for re-review.

Actions #4

Updated by Venky Shankar 11 months ago

Actually, now that the use-after-free issue in C_Flush_Journal is fixed, I believe its exposing bugs in the MDS and this tracker is one instance of that.

Actions #5

Updated by Venky Shankar 11 months ago

  • Status changed from New to Triaged
  • Assignee set to Patrick Donnelly
Actions #6

Updated by Patrick Donnelly 11 months ago

  • Status changed from Triaged to Fix Under Review
  • Pull request ID set to 62901
Actions #7

Updated by Patrick Donnelly 11 months ago

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

Updated by Upkeep Bot 11 months ago

  • Copied to Backport #71092: reef: fs/misc/multiple_rsync.sh: unhandled write error (2) No such file or directory, force readonly added
Actions #9

Updated by Upkeep Bot 11 months ago

  • Copied to Backport #71093: squid: fs/misc/multiple_rsync.sh: unhandled write error (2) No such file or directory, force readonly added
Actions #10

Updated by Upkeep Bot 11 months ago

  • Tags (freeform) set to backport_processed
Actions #11

Updated by Upkeep Bot 9 months ago

  • Merge Commit set to 6c01b91860bd79f14bba8792292af5f2d853c2ea
  • Fixed In set to v20.0.0-1803-g6c01b91860b
  • Upkeep Timestamp set to 2025-07-08T14:46:45+00:00
Actions #12

Updated by Upkeep Bot 8 months ago

  • Fixed In changed from v20.0.0-1803-g6c01b91860b to v20.0.0-1803-g6c01b91860bd
  • Upkeep Timestamp changed from 2025-07-08T14:46:45+00:00 to 2025-07-14T15:20:55+00:00
Actions #13

Updated by Upkeep Bot 8 months ago

  • Fixed In changed from v20.0.0-1803-g6c01b91860bd to v20.0.0-1803-g6c01b91860
  • Upkeep Timestamp changed from 2025-07-14T15:20:55+00:00 to 2025-07-14T20:45:29+00:00
Actions #14

Updated by Upkeep Bot 5 months ago

  • Released In set to v20.2.0~492
  • Upkeep Timestamp changed from 2025-07-14T20:45:29+00:00 to 2025-11-01T00:59:55+00:00
Actions #15

Updated by Upkeep Bot 3 days ago

  • Status changed from Pending Backport to Resolved
  • Upkeep Timestamp changed from 2025-11-01T00:59:55+00:00 to 2026-03-18T03:13:32+00:00
Actions

Also available in: Atom PDF