My Oracle Support Banner

Kernel Fails With Message "blk_integrity_compare: xx-xxx/xxxx protection interval 512 != 4096" On UEK4 Kernel System With 4K Sector Formatted Drives With DIF Enabled While SAS Cable Reconnecting (Adding Multipath Device Path) (Doc ID 2423167.1)

Last updated on AUGUST 04, 2018

Applies to:

Linux OS - Version Oracle Linux 6.0 and later
Linux x86-64

Symptoms

Linux server with UEK4 kernel has error message while reconnecting SAS cable from 4Kn (sector size) drive storage with DIF enabled to the Linux server for adding multipath device path.

The newly added path with 4Kn (sector size) drive will not work.

 

4K sector technology uses the storage surface media more efficiently by combining data that would have been stored in eight 512-byte sectors into one single sector that is 4096 bytes (4 KiB) in length. It is managed by HBA and storage side from the vendor. So please check with the storage/HBA vendors and make sure 4K sector technology is enabled.

There is a quick way to check if disk 4kn is enabled or not.
The following example shows the 4kn has been enabled on the /dev/sg001 block device.

 

The typical error messages for this kernel issue includes:
- blk_integrity_compare: xx-xxx/xxxx protection interval 512 != 4096
- conflict with existing integrity profile
- could not register integrity profile

By checking the /var/log/messages log, we can find the following error message while reconnecting SAS cable from 4Kn (sector size) drive storage with DIF enabled to the Linux server with UEK4 kernel for adding multipath device path.

# cat messages
Jan 01 00:00:00 localhost multipathd: sdgt: add path (uevent)
Jan 01 00:00:00 localhost multipathd: mpathcw: load table [0 15628053168 multipath 1 queue_if_no_path 0 1 1 round-robin 0 2 1 70:64 1 132:144 1]
Jan 01 00:00:00 localhost multipathd: sdgt [132:144]: path added to devmap mpathcw
+++ Jan 01 00:00:00 localhost kernel: [00000.341711] blk_integrity_compare: dm-109/sdcw protection interval 512 != 4096 <<< ======= Error message for adding device
+++ Jan 01 00:00:00 localhost kernel: [00000.342248] device-mapper: table: 249:109: conflict with existing integrity profile: sdcw profile mismatch <<< error message for adding device
+++ Jan 01 00:00:00 localhost kernel: [00000.342254] device-mapper: table: could not register integrity profile. <<< error message for adding device
Jan 01 00:00:00 localhost kernel: [00000.513065] mpt3sas_cm0: detecting: handle(0x00da), sas_address(0x500000000000000), phy(00)
Jan 01 00:00:00 localhost kernel: [00000.513071] mpt3sas_cm0: REPORT_LUNS: handle(0x00da), retries(0)
Jan 01 00:00:00 localhost kernel: [00000.513184] mpt3sas_cm0: TEST_UNIT_READY: handle(0x00da), lun(0)
Jan 01 00:00:00 localhost kernel: [00000.514081] scsi 10:0:305:0: Direct-Access ORACLE DDD000 TX00 PQ: 0 ANSI: 6
Jan 01 00:00:00 localhost kernel: [00000.514191] scsi 10:0:305:0: SSP: handle(0x00da), sas_addr(0x500000000000000), phy(00), device_name(0x500000000000000)
Jan 01 00:00:00 localhost kernel: [00000.514196] scsi 10:0:305:0: enclosure logical id(0x500000000000000), slot(52)
Jan 01 00:00:00 localhost kernel: [00000.514201] scsi 10:0:305:0: enclosure level(0x0000), connector name( )
Jan 01 00:00:00 localhost kernel: [00000.514206] scsi 10:0:305:0: serial_number( 00000000)
Jan 01 00:00:00 localhost kernel: [00000.528085] sd 10:0:305:0: Attached scsi generic sg206 type 0
Jan 01 00:00:00 localhost kernel: [00000.536739] sd 10:0:305:0: [sdgu] 1953506646 4096-byte logical blocks: (7.81 TB/7.27 TiB)
Jan 01 00:00:00 localhost kernel: [00000.538618] sd 10:0:305:0: [sdgu] Write Protect is off
Jan 01 00:00:00 localhost kernel: [00000.541407] sd 10:0:305:0: [sdgu] Write cache: enabled, read cache: enabled, supports DPO and FUA
Jan 01 00:00:00 localhost kernel: [00000.556336] sd 10:0:305:0: [sdgu] Enabling DIX T10-DIF-TYPE1-IP protection
Jan 01 00:00:00 localhost kernel: [00000.566164] sd 10:0:305:0: [sdgu] Attached SCSI disk
Jan 01 00:00:00 localhost multipathd: sdgu: add path (uevent)
Jan 01 00:00:00 localhost multipathd: mpathcx: load table [0 15628053168 multipath 1 queue_if_no_path 0 1 1 round-robin 0 2 1 70:80 1 132:160 1]
Jan 01 00:00:00 localhost kernel: [00000.621580] blk_integrity_compare: dm-110/sdcx protection interval 512 != 4096
Jan 01 00:00:00 localhost kernel: [00000.622199] device-mapper: table: 249:110: conflict with existing integrity profile: sdcx profile mismatch
Jan 01 00:00:00 localhost kernel: [00000.622206] device-mapper: table: could not register integrity profile.
Jan 01 00:00:00 localhost multipathd: sdgu [132:160]: path added to devmap mpathcx
Jan 01 00:00:00 localhost multipathd: mpathq: sdr - tur checker reports path is up
Jan 01 00:00:00 localhost multipathd: 65:16: reinstated
Jan 01 00:00:00 localhost multipathd: mpathq: remaining active paths: 2

 

Cause

To view full details, sign in with your My Oracle Support account.

Don't have a My Oracle Support account? Click to get started!


My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.