Skip to Main Content
Forums

Infrastructure Software

Announcement

For appeals, questions and feedback about Oracle Forums, please email oracle-forums-moderators_us@oracle.com. Technical questions should be asked in the appropriate category. Thank you!

OL8 partprob bug while adding shared disks Error: Partition(s):1,2,3.. /dev/sdc1 have been written,

BrokeDBAOct 30 2019 — edited Nov 8 2019

Hi guys ,

I was trying to add asm shared disks  using udev in my Ol8 vm on virtualbox (to install Rac 19c ), but I am having a problem when running partprobe on the partitions .

It's been a pain in the neck for weeks now  and no a reboot doesn't make it go.

I think it's a bug . Any one have ran into this ? any fix ? I even tried this on rhel8 and the error is similar.

Thx in advance

I partitioned each of the disks after attaching them to my vm as I used to do for my previous labs (rac on OL6/7 ) .

- It seems that ol8 doesn't allow partprobe to write the partition table info to the kernel (dynamically) after its modification. The system keeps requesting a reboot to link these modification to the kernel (see error) for each partition :

#/sbin/partprobe /dev/sdc1 
#/sbin/partprobe /dev/sdd1 
#/sbin/partprobe /dev/sde1 
#/sbin/partprobe /dev/sdf1
ERROR

default: ******************************************************************************
default: Configure udev. Fri Oct 25 20:02:46 UTC 2019
default: ******************************************************************************
default: Error: Partition(s) 1, 2, 3, 4, 5, 6, 7, 8, 9, 10, 11, 12, 13, 14, 15, 16, 17, 18, 19, 20, 21, 22, 23, 24, 25, 26, 27, 28, 29, 30, 31, 32, 33, 34, 35, 36, 37, 38, 39, 40, 41, 42, 43, 44, 45, 46, 47, 48, 49, 50, 51, 52, 53, 5
4, 55, 56, 57, 58, 59, 60, 61, 62, 63, 64 on /dev/sdc1 have been written, but we have been unable to inform the kernel of the change, probably because it/they are in use. As a result, the old partition(s) will remain in use. You should
reboot now before making further changes.
default: Error: Partition(s) 1, 2, 3, 4, 5, 6, 7, 8, 9, 10, 11, 12, 13, 14, 15, 16, 17, 18, 19, 20, 21, 22, 23, 24, 25, 26, 27, 28, 29, 30, 31, 32, 33, 34, 35, 36, 37, 38, 39, 40, 41, 42, 43, 44, 45, 46, 47, 48, 49, 50, 51, 52, 53, 5
4, 55, 56, 57, 58, 59, 60, 61, 62, 63, 64 on /dev/sdd1 have been written, but we have been unable to inform the kernel of the change, probably because it/they are in use. As a result, the old partition(s) will remain in use. You should
reboot now before making further changes.
default: Error: Partition(s) 1, 2, 3, 4, 5, 6, 7, 8, 9, 10, 11, 12, 13, 14, 15, 16, 17, 18, 19, 20, 21, 22, 23, 24, 25, 26, 27, 28, 29, 30, 31, 32, 33, 34, 35, 36, 37, 38, 39, 40, 41, 42, 43, 44, 45, 46, 47, 48, 49, 50, 51, 52, 53, 5
4, 55, 56, 57, 58, 59, 60, 61, 62, 63, 64 on /dev/sde1 have been written, but we have been unable to inform the kernel of the change, probably because it/they are in use. As a result, the old partition(s) will remain in use. You should
reboot now before making further changes.
default: Error: Partition(s) 1, 2, 3, 4, 5, 6, 7, 8, 9, 10, 11, 12, 13, 14, 15, 16, 17, 18, 19, 20, 21, 22, 23, 24, 25, 26, 27, 28, 29, 30, 31, 32, 33, 34, 35, 36, 37, 38, 39, 40, 41, 42, 43, 44, 45, 46, 47, 48, 49, 50, 51, 52, 53, 5
4, 55, 56, 57, 58, 59, 60, 61, 62, 63, 64 on /dev/sdf1 have been written, but we have been unable to inform the kernel of the change, probably because it/they are in use. As a result, the old partition(s) will remain in use. You should
reboot now before making further changes.

• udev rules :


[root@london2 vagrant]# cat /etc/udev/rules.d/99-oracle-asmdevices.rules
KERNEL=="sd?1", SUBSYSTEM=="block", PROGRAM=="/usr/lib/udev/scsi_id -g -u -d /dev/$parent", RESULT=="1ATA_VBOX_HARDDISK_VB10a62cf9-e1a4aafe", SYMLINK+="oracleasm/asm-disk1", OWNER="oracle", GROUP="dba", MODE="0660"
KERNEL=="sd?1", SUBSYSTEM=="block", PROGRAM=="/usr/lib/udev/scsi_id -g -u -d /dev/$parent", RESULT=="1ATA_VBOX_HARDDISK_VB28814cf8-c552fb1e", SYMLINK+="oracleasm/asm-disk2", OWNER="oracle", GROUP="dba", MODE="0660"
KERNEL=="sd?1", SUBSYSTEM=="block", PROGRAM=="/usr/lib/udev/scsi_id -g -u -d /dev/$parent", RESULT=="1ATA_VBOX_HARDDISK_VBd90d74ee-9d444a1a", SYMLINK+="oracleasm/asm-disk3", OWNER="oracle", GROUP="dba", MODE="0660"
KERNEL=="sd?1", SUBSYSTEM=="block", PROGRAM=="/usr/lib/udev/scsi_id -g -u -d /dev/$parent", RESULT=="1ATA_VBOX_HARDDISK_VB90ac3161-58c1b131", SYMLINK+="oracleasm/asm-disk4", OWNER="oracle", GROUP="dba", MODE="0660"

• Below is the list of disks existing in the server the newly created partitions are not mounted , just mapped (via udev) so ASM can manage them .

[root@london2 vagrant]# lsblk
NAME                MAJ:MIN RM  SIZE RO TYPE MOUNTPOINT  FSTYPE
------------------ -------- -- ----- -- ---- ---------- --------
sda                   8:0    0   32G  0 disk
+-sda1                8:1    0    1G  0 part /boot         xfs
+-sda2                8:2    0   31G  0 part               LVM2_member
  +-ol-root         253:0    0 28.9G  0 lvm  /             xfs
  +-ol-swap         253:1    0  2.1G  0 lvm  [SWAP]        swap
sdb                   8:16   0  100G  0 disk
+-sdb1                8:17   0  100G  0 part /u01
sdc                   8:32   0   20G  0 disk
+-sdc1                8:33   0   20G  0 part
sdd                   8:48   0   20G  0 disk
+-sdd1                8:49   0   20G  0 part
sde                   8:64   0   20G  0 disk
+-sde1                8:65   0   20G  0 part
sdf                   8:80   0   20G  0 disk
+-sdf1                8:81   0   20G  0 part
sr0                  11:0    1 1024M  0 rom
This post has been answered by BrokeDBA on Nov 8 2019
Jump to Answer
Comments
Post Details
Added on Oct 30 2019
#bug, #linux, #oracle-linux
5 comments
1,492 views