oracle19c asm,ASMLib or ASM Filter driver for 19C GI build ?

Thanks Dude, Markus !

As I understand, ASM Filter driver uses /dev/sd* as the default discovery string.

Below is the output of oracleasm querydisk from a server which is very similair to the one I am going to use for the upcoming build.

The physical server has multiple HBA cards. Hence, It will have lots of paths (Linux's native mulipaths) like /dev/sdab , /dev/sdgs, .. for one LUN as shown below. There are 14 of them !

But, the linux admin has asked us to use only the EMC power path device /dev/emcpowerab1 (the last one at the bottom)

# /usr/sbin/oracleasm/oracleasm querydisk -p DATA_D3

Disk "DATA_D3" is a valid ASM disk

/dev/sdab1: LABEL="DATA_D3" TYPE="oracleasm"

/dev/sdgs1: LABEL="DATA_D3" TYPE="oracleasm"

/dev/sdnj1: LABEL="DATA_D3" TYPE="oracleasm"

/dev/sdua1: LABEL="DATA_D3" TYPE="oracleasm"

/dev/sdaar1: LABEL="DATA_D3" TYPE="oracleasm"

/dev/sdahi1: LABEL="DATA_D3" TYPE="oracleasm"

/dev/sdanz1: LABEL="DATA_D3" TYPE="oracleasm"

/dev/sdauq1: LABEL="DATA_D3" TYPE="oracleasm"

/dev/sdbbk1: LABEL="DATA_D3" TYPE="oracleasm"

/dev/sdbib1: LABEL="DATA_D3" TYPE="oracleasm"

/dev/sdbos1: LABEL="DATA_D3" TYPE="oracleasm"

/dev/sdbvj1: LABEL="DATA_D3" TYPE="oracleasm"

/dev/sdcca1: LABEL="DATA_D3" TYPE="oracleasm"

/dev/sdcir1: LABEL="DATA_D3" TYPE="oracleasm"

/dev/emcpowerab1: LABEL="DATA_D3" TYPE="oracleasm"

If AFD is going to use /dev/sd* discovery string , wouldn't that create a conflict with Linux's native device naming ?