Project

General

Profile

Actions

Bug #20944

closed

OSD metadata 'backend_filestore_dev_node' is "unknown" even for simple deployment

Added by John Spray over 6 years ago. Updated over 6 years ago.

Status:
Resolved
Priority:
Normal
Assignee:
-
Category:
Administration/Usability
Target version:
-
% Done:

0%

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

Description

OSD created using ceph-deploy "ceph-deploy osd create --filestore", metadata after starting up is:

{
    "id": 9,
    "arch": "x86_64",
    "back_addr": "192.168.19.6:6802/2738",
    "backend_filestore_dev_node": "unknown",
    "backend_filestore_partition_path": "unknown",
    "ceph_version": "ceph version 12.1.2 (b661348f156f148d764b998b65b90451f096cb27) luminous (rc)",
    "cpu": "Intel(R) Celeron(R) CPU G1610T @ 2.30GHz",
    "default_device_class": "hdd",
    "distro": "centos",
    "distro_description": "CentOS Linux 7 (Core)",
    "distro_version": "7",
    "filestore_backend": "xfs",
    "filestore_f_type": "0x58465342",
    "front_addr": "192.168.18.6:6803/2738",
    "hb_back_addr": "192.168.19.6:6803/2738",
    "hb_front_addr": "192.168.18.6:6804/2738",
    "hostname": "gravel6.rockery",
    "kernel_description": "#1 SMP Tue Jul 4 15:04:05 UTC 2017",
    "kernel_version": "3.10.0-514.26.2.el7.x86_64",
    "mem_swap_kb": "4063228",
    "mem_total_kb": "7965928",
    "os": "Linux",
    "osd_data": "/var/lib/ceph/osd/ceph-9",
    "osd_journal": "/var/lib/ceph/osd/ceph-9/journal",
    "osd_objectstore": "filestore",
    "rotational": "1" 
}

While our code can't be expected to work out block devices in absolutely all cases, this seems like pretty much the simplest case we have for creating filestore OSDs, on a centos 7 node using bare SATA drives, so I'm thinking this is a bug if we're not finding the device node even in this case.


Related issues 1 (0 open1 closed)

Copied to RADOS - Backport #21465: luminous: OSD metadata 'backend_filestore_dev_node' is "unknown" even for simple deploymentResolvedNathan CutlerActions
Actions #1

Updated by John Spray over 6 years ago

Should have also said: bluestore was populating its bluestore_bdev_dev_node correctly on the same server and drive -- this was a filestore OSD deliberately created to check it was working too.

Actions #2

Updated by Sage Weil over 6 years ago

  • Status changed from New to Fix Under Review
  • Backport set to luminous
Actions #3

Updated by Sage Weil over 6 years ago

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

Updated by Nathan Cutler over 6 years ago

  • Copied to Backport #21465: luminous: OSD metadata 'backend_filestore_dev_node' is "unknown" even for simple deployment added
Actions #5

Updated by Nathan Cutler over 6 years ago

  • Status changed from Pending Backport to Resolved
Actions

Also available in: Atom PDF