| JayF | I will be there, I am giving a talk.' | 01:51 |
|---|---|---|
| FreemanBoss[m] | JayF: wow, great. I do watch your GR-OSS sessions on YouTube too. | 04:14 |
| dtantsur | guilhermesp: so at least my assumption was right: the outcome contains a /dev/md/ file. I wonder if it's an actual holder device or something else.. | 12:24 |
| TheJulia | dtantsur: the device, should be something else afaik, but it looks like it, which is why I was thinking we need to short circuit the recognition | 14:13 |
| dtantsur | TheJulia: I suspect we're too loose with our usage of regular expressions there :) | 14:26 |
| dtantsur | I wonder if we could use something like lsblk or lshw instead | 14:27 |
| TheJulia | I’m not sure, these hardware assisted software raids are weird :) | 14:35 |
| TheJulia | https://cdrdv2-public.intel.com/841442/linux-intel-vroc-userguide-333915.pdf <-- makes me think the answer is to look at the mdstat data since it is structurally diferent and that also sort of explains the ismn0 bit | 15:43 |
| TheJulia | sorry, imsm, not ismn | 18:42 |
| TheJulia | I think the thing to do is to look at mdstat, look at the entry in it, and see if it is using the external:imsm value which tags it as an external intel matrix storage manager. .. or mdadm --detail /dev/md/device and look to see if it references an imsm container | 19:45 |
Generated by irclog2html.py 4.0.0 by Marius Gedminas - find it at https://mg.pov.lt/irclog2html/!