Bug #52908: mpath devices aren't supported in all scenarios - ceph-volume - Ceph

Actions

Copy link

Bug #52908

closed

mpath devices aren't supported in all scenarios

Added by saber lehlib over 2 years ago. Updated about 2 years ago.

Status:

Resolved

Priority:

Normal

Assignee:

Guillaume Abrioux

Target version:

Ceph - v17.0.0

% Done:

Source:

Tags:

Backport:

quincy,pacific,octopus

Regression:

Severity:

3 - minor

Reviewed:

10/13/2021

Affected Versions:

Ceph - v17.0.0

ceph-qa-suite:

Pull request ID:

44304

Crash signature (v1):

Crash signature (v2):

Description

kubernetes: 1.22.2
Rook-ceph: 1.7.3
Os : Redhat 7.9

I want to deploy a new ceph cluster with rook in bare metal server with multipathd but i cannot create the osd pod
in the log i have this message:

exec: Running command: ceph-volume inventory --format json /dev/mapper/GK5CLI_1c00_CEPH01
cephosd: skipping device "dm-2": ["Device type is not acceptable. It should be raw device or partition"].exec: Running command: ceph-volume inventory --format json /dev/mapper/GK5CLI_1c00_CEPH01
cephosd: skipping device "dm-2": ["Device type is not acceptable. It should be raw device or partition"].

Ceph support multipathd ? any solution to fix it
Thanks

Files

cephs-tracker (37.2 KB) cephs-tracker

logs for osd_prepare

saber lehlib, 12/13/2021 10:50 AM

Related issues 3 (0 open — 3 closed)

Actions

Copy link

Updated by Sebastian Wagner over 2 years ago

Description updated (diff)

Actions

Copy link

Updated by Sebastian Wagner over 2 years ago

Tracker changed from Bug to Support
Status changed from New to Resolved

yes! See https://docs.ceph.com/en/latest/ceph-volume/lvm/prepare/#multipath-support

Actions

Copy link

Updated by Sébastien Han over 2 years ago

Status changed from Resolved to In Progress

This is not resolved, the issue on the c-v inventory list and the doc links the prepare step.
Re-opening for more investigation.

Actions

Copy link

Updated by Guillaume Abrioux over 2 years ago

could you provide a full log ?
what do `blkid` and `lsblk` say ?

Actions

Copy link

Updated by saber lehlib over 2 years ago

File cephs-tracker cephs-tracker added

Guillaume Abrioux wrote:

could you provide a full log ?
what do `blkid` and `lsblk` say ?

[root@node01 ~]# blkid
/dev/sdb1: SEC_TYPE="msdos" UUID="E349-1215" TYPE="vfat" PARTLABEL="EFI System Partition" PARTUUID="46c35333-dd00-4226-978c-9d4daaf795fe" 
/dev/sdb2: UUID="e0168fb6-ca82-47c3-befd-0c233373b906" TYPE="ext4" PARTUUID="fe7f6e3e-52ed-43b3-b371-5e2d834089c4" 
/dev/sdb3: UUID="kQuQSc-LfF7-35dn-qmVV-TpB8-Mf4U-STyQzo" TYPE="LVM2_member" PARTUUID="4087e748-2b32-4e6e-8238-10f65cf556cc" 
/dev/sdb4: UUID="fTrZLe-YNpM-8CeZ-Iadj-bYB2-IFhE-ALVLey" TYPE="LVM2_member" PARTUUID="caf116f4-4213-4dfb-a11e-ea605f8beb4c" 
/dev/mapper/rhel-root: UUID="9c1b4105-a1dd-47fa-96a7-1741f441e9fa" TYPE="ext4" 
/dev/mapper/rhel-usr: UUID="09e1533b-f404-493e-9564-49b51e897cad" TYPE="ext4" 
/dev/mapper/rhel-var: UUID="fc5556ad-d36d-4ede-8f65-2556774c609a" TYPE="ext4" 
/dev/mapper/rhel-tmp: UUID="674e0695-07ad-42f2-a2f5-0dc32b039dc1" TYPE="ext4" 
/dev/sdb5: PARTUUID="120118d6-2b44-4043-a385-16384a83c386" 
[root@node01 ~]# lsblk
NAME                 MAJ:MIN RM   SIZE RO TYPE  MOUNTPOINT
sdb                    8:16   0 745,2G  0 disk
├─sdb1                 8:17   0   512M  0 part  /boot/efi
├─sdb2                 8:18   0   512M  0 part  /boot
├─sdb3                 8:19   0    27G  0 part
│ ├─rhel-root        253:0    0     5G  0 lvm   /
│ ├─rhel-usr         253:1    0    10G  0 lvm   /usr
│ ├─rhel-var         253:2    0    29G  0 lvm   /var
│ └─rhel-tmp         253:3    0     2G  0 lvm   /tmp
├─sdb4                 8:20   0    20G  0 part
│ └─rhel-var         253:2    0    29G  0 lvm   /var
└─sdb5                 8:21   0   500G  0 part
sdc                    8:32   0   256G  0 disk
└─GK5CLI_1c00_CEPH01 253:4    0   256G  0 mpath
sdd                    8:48   0   256G  0 disk
└─GK5CLI_1c01_CEPH02 253:5    0   256G  0 mpath
sde                    8:64   0   256G  0 disk
└─GK5CLI_1c02_CEPH03 253:6    0   256G  0 mpath
sdf                    8:80   0   256G  0 disk
└─GK5CLI_1c03_CEPH04 253:7    0   256G  0 mpath
sdg                    8:96   0   256G  0 disk
└─GK5CLI_1c00_CEPH01 253:4    0   256G  0 mpath
sdh                    8:112  0   256G  0 disk
└─GK5CLI_1c01_CEPH02 253:5    0   256G  0 mpath
sdi                    8:128  0   256G  0 disk
└─GK5CLI_1c02_CEPH03 253:6    0   256G  0 mpath
sdj                    8:144  0   256G  0 disk
└─GK5CLI_1c03_CEPH04 253:7    0   256G  0 mpath
[root@node01 ~]#

Actions

Copy link

Updated by Guillaume Abrioux over 2 years ago

Tracker changed from Support to Bug
Project changed from Ceph to ceph-volume
Subject changed from Device type is not acceptable to mpath devices aren't supported in all scenarios
Category deleted (~~OSD~~)
Assignee set to Guillaume Abrioux
Backport set to pacific,octopus
Regression set to No
Severity set to 3 - minor