Hello Carlos,
The thing about these documentations is that there is a lot of combinations. As you must be aware, Linux Storage is stacked up of multiple independent components, tied tightly together to work in unison. This often need a good understanding of each involved stack, as well as the overall desired solution. Documenting everything is beyond the scope, especially for a general purpose universal distribution like Debian. I have, in the past, personally relied on the Red Hat Storage Admin Guide. They do a good job of documenting all the combinations and ensuring that the documents are valid and up-to-date. https://access.redhat.com/documentation/en-us/red_hat_enterprise_linux/7/html/storage_administration_guide/index On Mon, 2021-12-20 at 16:03 +0000, BARROS FERNANDEZ, Carlos wrote: > Hi Ritessh. > > On another server I have a stranger setup :) : > 1 LVM over multipath > + > 1 LVM over mdadm-device and the mdadm-device over multipaths > > Did had problems because the mdadm-device did not setup the > multipath, just the /dev/sdX devices > In this case, mdadm was called from udev as soon as a block device > was setup, so it always started the software-raid on /dev/sdX > What I did was tell mdadm to not setup any block devices, only > devices belonging to /dev/disk/by-id/dm-name-* because of the > 'friendly-names' used un multipath. > I spent some time to figure it out. > The file /etc/mdadm/mdadm.conf should have a 'DEVICES' line that > tells mdadm to only read those devices as follows: > DEVICE /dev/disk/by-id/dm-name-* > > # definitions of existing MD arrays > ARRAY /dev/md/0 metadata=1.2 > UUID=d7285198:51ed20e4:7d1e82e6:b01569dd devices=/dev/disk/by-id/dm- > name-* name=pandora:0 > > In this case, it is simpler, but it is very different from LVM as to > where it must be set.(I find it clearer too) > > Also, the filter in LVM only takes care of the /dev/sd[b-z) disks, > but it is common to have several paths( and disks) like /dev/sda[a- > z] /dev/sdb[a-z] and so on. > That filter would not filter out /dev/sda[a-z]*, it will use them. > So I did change the rule in LVM to include those cases, one for > /dev/sda[a-z] and one for /dev/sd[b-z] that covers the extra devices. > filter = [ "a|/dev/mapper/|", "r|/block/|", "r|/disk/|", "r|/sd[b- > z].*|", "r|/sda[a-z].*|", "a|.*|" ] > > > Would you modify the info to reflect the 'modified' filter rule? Also > a note on mdadm with that info would be nicer! > > > Regards. > INFORMACIÓN BÁSICA SOBRE PROTECCIÓN DE DATOS CONFORME EL NUEVO > REGLAMENTO EUROPEO (RGPD) > > RESPONSABLE: Grupo Econocom en España (Econocom SA, Econocom > Servicios S.A., Econocom Products & Solutions S.A.U.) sitas en > Cardenal Marcelo Spínola, 4, 28016 Madrid > FINALIDAD PRINCIPAL: Mantener relaciones profesionales y/o > comerciales con la empresa en la que usted trabaja o de la que es > representante. > LEGITIMACIÓN: Consentimiento del interesado. > DESTINATARIOS: No se cederán datos a terceros, salvo autorización > expresa u obligación legal. > DERECHOS: Acceder, rectificar y suprimir los datos, portabilidad de > los datos, limitación u oposición a su tratamiento, transparencia y > derecho a no ser objeto de decisiones automatizadas. > INFORMACIÓN ADICIONAL: Puede consultar la información adicional y > detallada sobre nuestra política de privacidad > DELEGADO DE PROTECCIÓN DE DATOS (DPD): Miguel Angel Muñoz +34 93 470 > 30 00 dpo_econocom...@econocom.com > CONFIDENCIALIDAD: Si Ud. no es el destinatario y recibe este mail por > error, rogamos se ponga en contacto con nosotros y borre de inmediato > el mail por error recibido con todos sus documentos adjuntos sin > leerlos ni hacer ningún uso de los datos que en ellos figuren, > ateniéndose a las consecuencias que de un uso indebido de dichos > datos puedan derivarse. > > > BASIC INFORMATION ON DATA PROTECTION ACCORDING TO THE NEW EUROPEAN > REGULATION (GDPR) > > CONTROLLER: Grupo Econocom in Spain. (Econocom SA, Econocom Servicios > S.A., Econocom Products & Solutions S.A.U.) registered at Cardenal > Marcelo Spínola, 4, 28016 Madrid > PURPOSE: Maintain professional and / or commercial relationship with > the company which you represent or work for > LEGITIMATION: Data subject consent. > RECIPIENTS: data will not be transferred to third parties, unless > explicit consent or legal obligation. > RIGHTS: Right to Access, right to rectification and erasure, data > portability, right to restriction of processing, right to object and > not been subject to a decision based solely on automated processing, > and to be informed in a clearly and transparent way of how their > personal data are processing. > ADDITIONAL INFORMATION: you can consult the additional and detailed > information about our privacy policy > DATA PROTECTION OFFICER (DPO): Miguel Angel Muñoz +34 93 470 30 > 00 dpo_econocom...@econocom.com > CONFIDENTIALITY: If you received this email in error, please > immediately contact us and destroy the material in its entirety, > whether in electronic or hard copy format. If you are not the > intended recipient, you are hereby notified that any disclosure, > copying, distribution, or use of the information contained herein > (including any reliance thereon) is strictly prohibited, on his/her > own responsibility. -- Ritesh Raj Sarraf | http://people.debian.org/~rrs Debian - The Universal Operating System
signature.asc
Description: This is a digitally signed message part