Hi
Being lot more used of ZFS (I have some little difficulties weth mdadm and Linux software raid so far). After having done quite some extended searches, I could not find a clear answer at my question.
Is it like ZFS and mdadm is able to find back by himself where are drives when system boots ? In ZFS, I can physically reorganise drives in bays as I want without any problems (ZFS scans all drives existing in system at boot to find back its own drives). Is it the same with mdadm ?
I ask the question as I use mdadm for software with a server having a 24 bays half full. I use extra free bays to upgrade/replace existing drives in the RAID but it implies that drive letters are going to change if I reboot machine compared to what it was at previous boot (sdb instead of sda,....).
All documentations I have seen regarding mdadm always use the sdXX and never the stable UUID identifiers.
Thanks for your help,
Vincèn
Being lot more used of ZFS (I have some little difficulties weth mdadm and Linux software raid so far). After having done quite some extended searches, I could not find a clear answer at my question.
Is it like ZFS and mdadm is able to find back by himself where are drives when system boots ? In ZFS, I can physically reorganise drives in bays as I want without any problems (ZFS scans all drives existing in system at boot to find back its own drives). Is it the same with mdadm ?
I ask the question as I use mdadm for software with a server having a 24 bays half full. I use extra free bays to upgrade/replace existing drives in the RAID but it implies that drive letters are going to change if I reboot machine compared to what it was at previous boot (sdb instead of sda,....).
All documentations I have seen regarding mdadm always use the sdXX and never the stable UUID identifiers.
Thanks for your help,
Vincèn
Statistics: Posted by vincen — 2025-01-21 10:58 — Replies 0 — Views 29