On 10/04/2017 07:23 AM, Artur Paszkiewicz wrote: > On 10/04/2017 01:02 PM, Artur Paszkiewicz wrote: >> Applications like mdadm can use this to hide/unhide their component >> devices. > > And here is an example patch for mdadm. It adds options to manually hide > or unhide the component devices: > > mdadm --hide-components /dev/md0 > mdadm --unhide-components /dev/md0 > > And an option for mdadm.conf that automatically hides the array's member > disks when assembling and when new disks are added: > > ARRAY /dev/md/0 metadata=1.2 UUID=c2c4f8c6:cd775924:9cb2cc62:88fa45bd > name=linux-ns31:0 hide-components=yes > > Hidden disks (by mdadm --hide-components or by config) should unhide > when the array is stopped or disks are removed. It only works for whole > devices, not partitions. I am not at all in favor of these patches, as they break all kinds of diagnostic tooling and certainly violate the principle of least surprise. Tools like "lsblk --tree" and my own "lsdrv" [1]. Please keep these out of the kernel, or better yet, explain to your customers that visibility into the components is a key *advantage* of software raid. Regards, Phil Turmel [1] https://github.com/pturmel/lsdrv -- To unsubscribe from this list: send the line "unsubscribe linux-raid" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
