Project

General

Profile

Bug #47330

ceph-osd can't start when CURRENT file does not end with newline or content is empty

Added by daolong zhang over 3 years ago. Updated 12 months ago.

Status:
Closed
Priority:
Normal
Assignee:
Target version:
-
% Done:

100%

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

Description

When the machine is shutdown or reboot by IPMI, some ceph-osds cannot be started. The error message is as follows

2020-08-22 15:48:22.455 7f21be1dfd80 4 rocksdb: Fast CRC32 supported: Supported on x86
2020-08-22 15:48:22.455 7f21be1dfd80 4 rocksdb: [/root/rpmbuild/BUILD/ceph-13.2.6-4-g9537302/src/rocksdb/db/db_impl.cc:252] Shutdown: canceling all background work
2020-08-22 15:48:22.455 7f21be1dfd80 4 rocksdb: [/root/rpmbuild/BUILD/ceph-13.2.6-4-g9537302/src/rocksdb/db/db_impl.cc:397] Shutdown complete
2020-08-22 15:48:22.455 7f21be1dfd80 -1 rocksdb: Corruption: CURRENT file does not end with newline
2020-08-22 15:48:22.455 7f21be1dfd80 -1 bluestore(/var/lib/ceph/osd/ceph-8) _open_db erroring opening db:
2020-08-22 15:48:22.455 7f21be1dfd80 1 bluefs umount
2020-08-22 15:48:22.455 7f21be1dfd80 1 stupidalloc 0x0x558e34e6eba0 shutdown
2020-08-22 15:48:22.455 7f21be1dfd80 1 stupidalloc 0x0x558e34e6ec00 shutdown

I think the current file is damaged or the content is not completely written, when it is shutdown or restarted abnormally。

History

#1 Updated by Neha Ojha over 3 years ago

  • Status changed from New to Fix Under Review

#2 Updated by Kefu Chai almost 3 years ago

  • Status changed from Fix Under Review to Resolved
  • Assignee set to daolong zhang

#3 Updated by Neha Ojha over 2 years ago

  • Status changed from Resolved to New

https://github.com/ceph/ceph/pull/37016 isn't a fix for this issue, but provides a bluefs-import option for recovery.

#4 Updated by Neha Ojha over 2 years ago

Neha Ojha wrote:

https://github.com/ceph/ceph/pull/37016 isn't a fix for this issue, but provides a bluefs-import option for recovery.

https://github.com/ceph/ceph/pull/44317 is a follow-on fix.

#5 Updated by Igor Fedotov 12 months ago

  • Status changed from New to Closed

We've got means to fix the file but still know nothing about the origin of that "invalid" file... Doesn't look like a common issue though. Hence closing.

Also available in: Atom PDF