Re: Anomaly of EDEV mdisk attachment in SLES12

2017-04-13 Thread Juha Vuori
On 13.04.2017 17:43, Alan Altmark wrote: One of the tenets of a secure system is the idea that you do not leave residual data on a device that has been removed from a server. It should be formatted immediately after de-provisioning, prior to placing in the 'available' pool. The primary

Re: Anomaly of EDEV mdisk attachment in SLES12

2017-04-13 Thread Juha Vuori
On 13.04.2017 14:03, Stefan Haberland wrote: You have to mention that the partition detection process is - independent of the disk type - a hierarchical process. Those partition detection parts high in the hierarchy are asked first if they would like to try and possibly take the disk as theirs.

Re: Anomaly of EDEV mdisk attachment in SLES12

2017-04-13 Thread Alan Altmark
On Thursday, 04/13/2017 at 11:05 GMT, Stefan Haberland wrote: > So you always have to take care if you recycle previously used disks. One of the tenets of a secure system is the idea that you do not leave residual data on a device that has been removed from a server.

Re: Anomaly of EDEV mdisk attachment in SLES12

2017-04-13 Thread Stefan Haberland
On 12.04.2017 20:54, juha.vu...@pp2.inet.fi wrote: 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

Re: Anomaly of EDEV mdisk attachment in SLES12

2017-04-12 Thread juha.vu...@pp2.inet.fi
>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