>Trying to add fba mdisk from EDEVICE to sles12.2 guest, and dasd_fba driver >does not create the full partition node, /dev/dasdh1, for it for some reason: > >zlnx030:~ # vmcp link '*' 305 a305 mr >zlnx030:~ # chccwdev -e a305 >Setting device 0.0.a305 online >Done >zlnx030:~ # lsdasd a305 >Bus-ID Status Name Device Type BlkSz Size Blocks >============================================================================== >0.0.a305 active dasdh 94:28 FBA 512 10240MB 20971520 >zlnx030:~ # ll /dev/dasdh* >brw-rw---- 1 root disk 94, 28 Apr 12 13:04 /dev/dasdh > >Log for setting online: > >2017-04-12T13:04:07.613846+03:00 zlnx030 kernel: dasd-fba.f36f2f: 0.0.a305: >New FBA DASD 9336/10 (CU 6310/80) with 10240 MB and 512 B/blk > >but not partition creation happening as in SLES11.4 for the same mdisk: > >kernel: dasdk:(nonl) dasdk1
Seems that this is related to what old garbage you have in the blocks of the new mdisk. Once I dd'd /dev/zero to /dev/dasdh, put it offline and back online, dasd_fba did its magic and created the partition /dev/dasdh1. Seems that the logic in dasd drivers for recognizing the type of a dasd is not inclusive, and the latest level drivers in sles11.4 do better job in that than the ones in sles12.2. A bit annoying, but once you know it you can live with it :) I don't see a point in opening a bug report, now. (Or better, just call me lazy.) -- Regards, Juha ---------------------------------------------------------------------- For LINUX-390 subscribe / signoff / archive access instructions, send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390 ---------------------------------------------------------------------- For more information on Linux on System z, visit http://wiki.linuxvm.org/
