Bug 197573

That's irritating, because JBOD was never directly supported by the Silicon
Image metadata format handler.

Just to be sure: which dmraid version succeded to activate it ?

Please attach the output files created with that version and command 'dmraid
-rD' tar'ed/bzip2*ed in sil-matti_arrnio-jbod.tar.bz2 to this bugzilla.

I do wonder if "dmraid -rD" really is the interesting thing..
it is so small output that packing them into a file makes no sense.


# dmraid -V
dmraid version:         1.0.0.rc8 (2005.05.19) debug 
dmraid library version: 1.0.0.rc8 (2005.05.19)
device-mapper version:  4.7.0

# dmraid -rD
ERROR: sil: zero sectors on /dev/sda
ERROR: sil: setting up RAID device /dev/sda
ERROR: sil: zero sectors on /dev/sdb
ERROR: sil: setting up RAID device /dev/sdb
/dev/sdc: sil, "sil_afbidgcaafaj", mirror, ok, 490232704 sectors, data@ 0
/dev/sdd: sil, "sil_afbidgcaafaj", mirror, ok, 490232704 sectors, data@ 0

That's fine. ATARAID metadata (e.g. sil) usually is extremely small.
Please create with .rc8 and pack as described in comment #1.
Thanks.

Created attachment 131904 [details]
two JBODs + one pair of RAID1 on SiI 3114

finally understood what gentlement did mean --- -vvv  gave
enough clue of dump-files being written..

Is this all primary partitions ?

Please attach the partition sector created by e.g. 
'dd if=/dev/sil_afbidgcaafaj bs=512 count=1 of=sil_afbidgcaafaj.partition_table'
and the 'fdisk -lu' output as well.

Created attachment 131908 [details]
SIL RAID1 disk partition table sector

Created attachment 131909 [details]
"fdisk -lu" output (sans stderr) in the system

Heads up: still investigating, why dmraid doesn't activate the partitions.

Can you try running 'kpartx -a /dev/mapper/sil_afbidgcaafaj' after 'dmraid -ay'
and see if that gives you your partition table mappings as a workaround ?

FYI: I'ld want to get rid of the partition table activation in dmraid in favour
of kpartx anyway later.

Found the bug and put
people.redhat.com/heinzm/sw/dmraid/tst/dmraid-1.0.0.rc12-pre1.static binary up
for testing.
Please download, run 'dmraid-1.0.0.rc12-pre1.static -vay' and report.

  Shrinking the output a bit with:  -f sil

# /tmp/dmraid-1.0.0.rc12-pre1.static -f sil -ay -v -v -v -v
NOTICE: checking format identifier sil
WARN: locking /var/lock/dmraid/.lock
NOTICE: skipping removable device /dev/sdg
NOTICE: skipping removable device /dev/sdf
NOTICE: skipping removable device /dev/sde
NOTICE: /dev/sda: sil     discovering
NOTICE: sil: areas 1,2,3,4[4] are valid
NOTICE: /dev/sda: sil metadata discovered
NOTICE: /dev/sdb: sil     discovering
NOTICE: sil: areas 1,2,3,4[4] are valid
NOTICE: /dev/sdb: sil metadata discovered
NOTICE: /dev/sdc: sil     discovering
NOTICE: sil: areas 1,2,3,4[4] are valid
NOTICE: /dev/sdc: sil metadata discovered
NOTICE: /dev/sdd: sil     discovering
NOTICE: sil: areas 1,2,3,4[4] are valid
NOTICE: /dev/sdd: sil metadata discovered
NOTICE: added /dev/sda to RAID set "sil_afbgdjdeddbb"
NOTICE: added /dev/sdb to RAID set "sil_afbgdjdecfbd"
NOTICE: added /dev/sdc to RAID set "sil_afbidgcaafaj"
NOTICE: added /dev/sdd to RAID set "sil_afbidgcaafaj"
INFO: Activating mirror RAID set "sil_afbidgcaafaj"
NOTICE: discovering partitions on "sil_afbgdjdeddbb"
NOTICE: /dev/mapper/sil_afbgdjdeddbb: dos     discovering
ERROR: dos: reading /dev/mapper/sil_afbgdjdeddbb[No such file or directory]
NOTICE: discovering partitions on "sil_afbgdjdecfbd"
NOTICE: /dev/mapper/sil_afbgdjdecfbd: dos     discovering
ERROR: dos: reading /dev/mapper/sil_afbgdjdecfbd[No such file or directory]
NOTICE: discovering partitions on "sil_afbidgcaafaj"
NOTICE: /dev/mapper/sil_afbidgcaafaj: dos     discovering
NOTICE: /dev/mapper/sil_afbidgcaafaj: dos metadata discovered
NOTICE: created partitioned RAID set(s) for /dev/mapper/sil_afbidgcaafaj
INFO: Activating partition RAID set "sil_afbidgcaafaj1"
INFO: Activating partition RAID set "sil_afbidgcaafaj2"
INFO: Activating partition RAID set "sil_afbidgcaafaj3"
WARN: unlocking /var/lock/dmraid/.lock


  Kernel complains a bit:

device-mapper: table: 253:0: linear: dm-linear: Device lookup failed
device-mapper: ioctl: error adding target to table
device-mapper: table: 253:1: linear: dm-linear: Device lookup failed
device-mapper: ioctl: error adding target to table


# ls -l /dev/mapper/
total 0
crw------- 1 root root  10, 63 Jul  3 22:34 control
brw-rw---- 1 root disk 253,  1 Jul  7 17:09 sil_afbgdjdecfbd
brw-rw---- 1 root disk 253,  0 Jul  7 17:09 sil_afbgdjdeddbb
brw-rw---- 1 root disk 253,  2 Jul  7 17:09 sil_afbidgcaafaj
brw-rw---- 1 root disk 253,  3 Jul  7 17:09 sil_afbidgcaafaj1
brw-rw---- 1 root disk 253,  4 Jul  7 17:09 sil_afbidgcaafaj2
brw-rw---- 1 root disk 253,  5 Jul  7 17:09 sil_afbidgcaafaj3


OK - raid1 partition works, I wonder why the "dm-linear" complains ?


About the  kpartx: is it in right place being in  device-mapper-multipath ?
I don't need multipath myself, but if that utility will be needed...

The  kpartx  is indeed able to create those partition labels,
but it isn't in default installations "'cause this machine has
no multipathing thingamajing.."

The "dm-linear"'s complaint may be because the SDA/SDB devices are
already bound to MD.

All dmraid versions since 1.0.0.rc12 should have the bug fixed now.
Closing.