Actions
Bug #42675
closedmds: tolerate no snaprealm encoded in on-disk root inode
% Done:
0%
Source:
Development
Tags:
Backport:
nautilus,mimic
Regression:
No
Severity:
3 - minor
Reviewed:
Affected Versions:
ceph-qa-suite:
Component(FS):
MDS
Labels (FS):
snapshots
Pull request ID:
Crash signature (v1):
Crash signature (v2):
Description
cephfs-data-scan of luminous and prior versions may update on-disk root inode without encoding snaprealm (cephfs-data-scan init). This can cause mimic and later mds crash.
crash looks like:
ceph version 13.2.6 (7b695f835b03642f85998b2ae7b6dd093d9fbce4) mimic (stable)
1: (()+0x12e70) [0x7fffeea46e70]
2: (operator<<(std::ostream&, SnapRealm const&)+0x42) [0x5555558c2f02]
3: (SnapRealm::merge_to(SnapRealm*)+0x2f8) [0x5555558c56f8]
4: (CInode::decode_snap_blob(ceph::buffer::list&)+0x53) [0x55555587af53]
5: (CInode::decode_store(ceph::buffer::list::iterator&)+0x76) [0x55555589a5f6]
6: (CInode::_fetched(ceph::buffer::list&, ceph::buffer::list&, Context*)+0x314) [0x55555589a954]
7: (MDSIOContextBase::complete(int)+0x11d) [0x5555558e533d]
8: (Finisher::finisher_thread_entry()+0x135) [0x7fffef79f115]
9: (()+0x84aa) [0x7fffeea3c4aa]
10: (clone()+0x43) [0x7fffee4033f3]
NOTE: a copy of the executable, or `objdump -rdS <executable>` is needed to interpret this.
Updated by Zheng Yan over 4 years ago
- Status changed from New to Fix Under Review
- Pull request ID set to 31455
Updated by Patrick Donnelly over 4 years ago
- Status changed from Fix Under Review to Pending Backport
- Assignee set to Zheng Yan
- Target version set to v15.0.0
- Source set to Development
- Component(FS) MDS added
- Labels (FS) snapshots added
Updated by Nathan Cutler over 4 years ago
- Copied to Backport #43143: nautilus: mds: tolerate no snaprealm encoded in on-disk root inode added
Updated by Nathan Cutler over 4 years ago
- Copied to Backport #43144: mimic: mds: tolerate no snaprealm encoded in on-disk root inode added
Updated by Nathan Cutler almost 4 years ago
- Status changed from Pending Backport to Resolved
While running with --resolve-parent, the script "backport-create-issue" noticed that all backports of this issue are in status "Resolved" or "Rejected".
Actions