Bug 1719971 - [ceph-volume] NVME disk with wal/db does not mount after node reboot
Summary: [ceph-volume] NVME disk with wal/db does not mount after node reboot
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Ceph Storage
Classification: Red Hat Storage
Component: Ceph-Volume
Version: 3.2
Hardware: Unspecified
OS: Linux
high
high
Target Milestone: z1
: 3.3
Assignee: Andrew Schoen
QA Contact: Vasishta
Bara Ancincova
URL:
Whiteboard:
Depends On:
Blocks: 1726135
TreeView+ depends on / blocked
 
Reported: 2019-06-12 20:49 UTC by mamccoma
Modified: 2019-10-22 13:29 UTC (History)
10 users (show)

Fixed In Version: RHEL: ceph-12.2.12-70.el7cp Ubuntu: ceph_12.2.12-63redhat1
Doc Type: Bug Fix
Doc Text:
.An error is now returned when the WAL and DB partitions are defined but not present Due to a race condition, after restarting a Nonvolatile Memory Express (NVMe) device containing the WAL and DB devices, the symbolic links for WAL and DB were missing. Consequently, the NVMe node could not be mounted. The underlying source code has been modified to return an error if WAL or DB devices are defined but the symbolic links are missing on the system, which allows trying for up to 30 times at 5 second intervals and increasing the chances of finding the devices as the system boots.
Clone Of:
Environment:
Last Closed: 2019-10-22 13:29:00 UTC
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Ceph Project Bug Tracker 40100 0 None None None 2019-06-19 19:07:59 UTC
Github ceph ceph pull 28791 0 'None' closed Return an error, for Bluestore OSD, if WAL or DB are defined in the tags of the OSD but not present on the system 2020-08-18 18:46:37 UTC
Red Hat Product Errata RHBA-2019:3173 0 None None None 2019-10-22 13:29:14 UTC

Comment 22 errata-xmlrpc 2019-10-22 13:29:00 UTC 
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHBA-2019:3173
Note You need to log in before you can comment on or make changes to this bug.