linux-kernel - megaraid_sas module, no /dev entries for partitions

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [day] [month] [year] [list]

Message-ID: <CADNH=7E-FQtx21AYTs5MVELdZWAWeWPMOwU-zoEvrnXuLn-LaQ@mail.gmail.com>
Date:	Thu, 1 Oct 2015 19:14:01 +0100
From:	Mathias Burén <mathias.buren@...il.com>
To:	"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>
Subject: megaraid_sas module, no /dev entries for partitions

Hi,

I'm using megaraid_sas 06.807.10.00-rc1 from Linux 4.3.0-rc3. The /dev
entries get created for the devices, but not for the partitions on the
devices. I'm using systemd 226 The LSI card is a

02:0e.0 RAID bus controller: LSI Logic / Symbios Logic MegaRAID SAS 1068

which is being used in JBOD mode. Here are the /dev entries:

brw-rw---- 1 root disk 8, 64 Oct  1 20:03 /dev/sde
brw-rw---- 1 root disk 8, 80 Oct  1 20:03 /dev/sdf

As you can see with fdisk they have partitions:

Disk /dev/sde: 1.8 TiB, 1998998994944 bytes, 3904294912 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disklabel type: dos
Disk identifier: 0x056cc1c0

Device     Boot Start        End    Sectors  Size Id Type
/dev/sde1        2048 3904294911 3904292864  1.8T fd Linux raid autodetect

Disk /dev/sdf: 1.8 TiB, 1998998994944 bytes, 3904294912 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disklabel type: dos
Disk identifier: 0x9fb14a5c

Device     Boot Start        End    Sectors  Size Id Type
/dev/sdf1        2048 3904294911 3904292864  1.8T fd Linux raid autodetect

Any idea why the partition entries don't get created in /dev? Is it
because I had partitions on the block devices before and since moved
on to partitions without erasing the old MD superblocks, causing udev
to find the superblock on the block device, and skipping the partition
check(s)?

(below showing out of date info on block device for a long gone MD
array, the MD array now resides on the partitions, which aren't
getting created in /dev/)

~]$ udevadm info /dev/sdf
P: /devices/pci0000:00/0000:00:01.0/0000:01:00.0/0000:02:0e.0/host7/target7:2:1/7:2:1:0/block/sdf
N: sdf
S: disk/by-id/scsi-3600605b0025eff50ff000027c46c9336
S: disk/by-id/wwn-0x600605b0025eff50ff000027c46c9336
S: disk/by-path/pci-0000:02:0e.0-scsi-0:2:1:0
E: DEVLINKS=/dev/disk/by-id/scsi-3600605b0025eff50ff000027c46c9336
/dev/disk/by-path/pci-0000:02:0e.0-scsi-0:2:1:0
/dev/disk/by-id/wwn-0x600605b0025eff50ff000027c46c9336
E: DEVNAME=/dev/sdf
E: DEVPATH=/devices/pci0000:00/0000:00:01.0/0000:01:00.0/0000:02:0e.0/host7/target7:2:1/7:2:1:0/block/sdf
E: DEVTYPE=disk
E: ID_BUS=scsi
E: ID_FS_LABEL=ion:md0
E: ID_FS_LABEL_ENC=ion:md0
E: ID_FS_TYPE=linux_raid_member
E: ID_FS_USAGE=raid
E: ID_FS_UUID=0ad2603e-e432-83ee-0218-077398e716ef
E: ID_FS_UUID_ENC=0ad2603e-e432-83ee-0218-077398e716ef
E: ID_FS_UUID_SUB=93568b01-6323-95bf-7d00-82a5db9b6ff9
E: ID_FS_UUID_SUB_ENC=93568b01-6323-95bf-7d00-82a5db9b6ff9
E: ID_FS_VERSION=1.2
E: ID_MODEL=MegaRAID_84016E
E: ID_MODEL_ENC=MegaRAID\x2084016E\x20
E: ID_PATH=pci-0000:02:0e.0-scsi-0:2:1:0
E: ID_PATH_TAG=pci-0000_02_0e_0-scsi-0_2_1_0
E: ID_REVISION=1.12
E: ID_SCSI=1
E: ID_SCSI_SERIAL=0036936cc4270000ff50ff5e02b00506
E: ID_SERIAL=3600605b0025eff50ff000027c46c9336
E: ID_SERIAL_SHORT=600605b0025eff50ff000027c46c9336
E: ID_TYPE=disk
E: ID_VENDOR=LSI
E: ID_VENDOR_ENC=LSI\x20\x20\x20\x20\x20
E: ID_WWN=0x600605b0025eff50
E: ID_WWN_VENDOR_EXTENSION=0xff000027c46c9336
E: ID_WWN_WITH_EXTENSION=0x600605b0025eff50ff000027c46c9336
E: MAJOR=8
E: MINOR=80
E: SUBSYSTEM=block
E: TAGS=:systemd:
E: UDISKS_MD_MEMBER_ARRAY_SIZE=8001.06GB
E: UDISKS_MD_MEMBER_DEVICES=6
E: UDISKS_MD_MEMBER_DEV_UUID=93568b01:632395bf:7d0082a5:db9b6ff9
E: UDISKS_MD_MEMBER_EVENTS=97557
E: UDISKS_MD_MEMBER_LEVEL=raid6
E: UDISKS_MD_MEMBER_NAME=ion:md0
E: UDISKS_MD_MEMBER_UPDATE_TIME=1415137429
E: UDISKS_MD_MEMBER_UUID=0ad2603e:e43283ee:02180773:98e716ef
E: USEC_INITIALIZED=79065504833



Cheers,
Mathias
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/