Bug #67628
openmds goes read-only during segment expiry
0%
Description
/a/vshankar-2024-07-08_07:21:13-fs-wip-vshankar-testing-20240705.150505-debug-testing-default-smithi/7791798
2024-07-09T19:51:18.700+0000 7fdb4d750640 10 MDSContext::complete: 21C_MaybeExpiredSegment 2024-07-09T19:51:18.700+0000 7fdb4d750640 -1 mds.0.14 unhandled write error (2) No such file or directory, force readonly... 2024-07-09T19:51:18.700+0000 7fdb4d750640 1 mds.0.cache force file system read-only 2024-07-09T19:51:18.700+0000 7fdb4d750640 0 log_channel(cluster) log [WRN] : force file system read-only 2024-07-09T19:51:18.700+0000 7fdb4d750640 10 mds.0.server force_clients_readonly
This was seen in a test branch which had https://github.com/ceph/ceph/pull/55421, but the mds going read only doesn't seem to be happening due to backtrace update. II'll put https://github.com/ceph/ceph/pull/55421 to another round of test (with some additional debugging) to be extra sure that it isn't caused by the change.
Updated by Venky Shankar over 1 year ago
Leaving this unassigned until test results for https://github.com/ceph/ceph/pull/55421 are analyzed.
Updated by Venky Shankar over 1 year ago
- Category set to Correctness/Safety
- Assignee set to Venky Shankar
- Backport set to quincy,reef,squid
Venky Shankar wrote in #note-1:
Leaving this unassigned until test results for https://github.com/ceph/ceph/pull/55421 are analyzed.
Didn't see this issue again with https://github.com/ceph/ceph/pull/55421, so this issue is likely a new issue.
Updated by Venky Shankar over 1 year ago
- Related to Bug #63259: mds: failed to store backtrace and force file system read-only added
Updated by Venky Shankar about 1 year ago
Hmmm another one: /a/vshankar-2024-12-19_10:00:45-fs-wip-vshankar-testing-20241219.063429-debug-testing-default-smithi/8044410
2024-12-19T12:38:29.533+0000 7fc3a2134640 10 MDSContext::complete: 21C_MaybeExpiredSegment 2024-12-19T12:38:29.533+0000 7fc3a2134640 10 mds.0.log finish: ls=LogSegment(8056/0x19994da~19d1de4 events=107), r=-2 2024-12-19T12:38:29.533+0000 7fc3a2134640 -1 mds.0.14 unhandled write error (2) No such file or directory, force readonly... 2024-12-19T12:38:29.533+0000 7fc3a2134640 1 mds.0.cache force file system read-only 2024-12-19T12:38:29.533+0000 7fc3a2134640 0 log_channel(cluster) log [WRN] : force file system read-only 2024-12-19T12:38:29.533+0000 7fc3a2134640 10 mds.0.server force_clients_readonly
Updated by Konstantin Shalygin about 1 year ago
- Backport changed from quincy,reef,squid to reef,squid