On Mi, 15.10.25 06:15, Stephen Smoogen ([email protected]) wrote: > decisions when dealing with server hardware. Using non-raid ends up with > dozens of bad 'Poor Man Raid' solutions where you are trying to keep > multiple partitions in sync with each other which invariably end up running > into some consistency problem at the worst time. I have had to 'maintain' > several of these before mdadm RAID1 boot via grub was widely available.. > and most of them made the nightmare of sysV scripts look pleasant. Why did > drive 5 say it was in sync when it is clearly holding 2 month old boot > entries? Why is drive 2 on a dozen systems full when they are all the same > size partition? Why did the firmware decide it could boot from drive 3 only > when it is in slot 5 (oh its because the kernel is not in the right spot on > this drive??? ) > > I remember a lot of different kernel issues coming up where to get help was > 'make the drives all raid1 and if it happens then we can fix it.' Because > these were oddities.. usually the cargo cult fix of making them all raid1 > would make it go away. > > Is there a way that there could be a new tool in the systemd family which > keeps multiple boot partitions in sync for booting purposes? I say this > because we need a tool which does this, checks on the validity regularly > and keeps up with 'drive A has new content, we need to deal with N other > drives' in a common way. [Where N is going to be set by the various > oddities of the server hardware and business logic someone has to follow > even if it looks insane.] > > If there is something like that, then one of the biggest reasons for RAID1 > (keep N drives in sync without manual interaction or my-poor-man-raid.sh > not working today) goes away.
Well, you'd first come up with a strategy on where to mount the various ESPs/XBOOTLDRs, i.e. introduce /boot.mirror.d/ and /efi.mirror.d/ or so, with one mount in it for each ESP/XBOOTLDR on each disk. Teaching kernel-install+bootctl to then do their stuff on all of them one by one on each invocation, sounds totally fine to me. But my personal interest in RAID is at zero. Somebody with an actual interest in this needs to do the work. For a seasoned C dev shouldn't take more than a few days to implement. Lennart -- _______________________________________________ devel mailing list -- [email protected] To unsubscribe send an email to [email protected] Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/[email protected] Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
