BLU Discuss list archive
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Discuss] SysVinit vs. systemd
- Subject: [Discuss] SysVinit vs. systemd
- From: bill.n1vux at gmail.com (Bill Ricker)
- Date: Wed, 17 Sep 2014 14:04:02 -0400
- In-reply-to: <5419C0A1.7000305@gmail.com>
- References: <5411058F.6010208@gmail.com> <li6a9669ml8.fsf@panix5.panix.com> <CAAbKA3UY2m42=Uzd=3FHfsskkTXfEzYq-qWf9DfA7y1P7QAOYQ@mail.gmail.com> <li67g184ybi.fsf@panix5.panix.com> <746ca932f9f04b02a7d1e57db3ec9b69@CO2PR04MB684.namprd04.prod.outlook.com> <5417215A.4020104@gmail.com> <CAJFsZ=qmo99ePLYcBgpV1PvrXK-3OxV3AAHStncCo0c+1T2GMw@mail.gmail.com> <li638bqmell.fsf@panix5.panix.com> <5419B7EB.8050105@gMail.com> <20140917164531.GQ13278@randomstring.org> <5419C0A1.7000305@gmail.com>
On Wed, Sep 17, 2014 at 1:10 PM, Richard Pieri <richard.pieri at gmail.com> wrote: > This may fail if you're using Multipath I/O. Heh, Multipath i/o can break almost anything, but particularly when in error cases. Subtle interactions between bugs in different layers that aren't *singly* a problem but ... are really hard to test for, or replicate. I've had more failures made worse by Multipath than saved by it (although not on Linux, and not a statistically significant quantity: merely plural anecdotes so far; but both with OS-vendor MPio and Storage-vendor MPio *sigh*). (E.g., in one case, OS & MPio bugs interacted when a card or controller was bad - had we not had MPio, it would have been simple HW crash to route away from and repair; with MP it behaved weirdly, badly, and required debugging, as MPio masked the problem and expressed it elsewhere.) So MPio can be (mostly) good for a critical DB server's data storage, i might use it again in similar max-uptime situation, but not as ubiquitously; for other things, other more virtual forms of disk access may be more resilient in reality. (And they're coming for our DBs too.) -- Bill Ricker bill.n1vux at gmail.com https://www.linkedin.com/in/n1vux
- Follow-Ups:
- [Discuss] SysVinit vs. systemd
- From: richard.pieri at gmail.com (Richard Pieri)
- [Discuss] SysVinit vs. systemd
- References:
- [Discuss] SysVinit vs. systemd
- From: tmetro+blu at gmail.com (Tom Metro)
- [Discuss] SysVinit vs. systemd
- From: smallm at panix.com (Mike Small)
- [Discuss] SysVinit vs. systemd
- From: bill.n1vux at gmail.com (Bill Ricker)
- [Discuss] SysVinit vs. systemd
- From: smallm at panix.com (Mike Small)
- [Discuss] SysVinit vs. systemd
- From: blu at nedharvey.com (Edward Ned Harvey (blu))
- [Discuss] SysVinit vs. systemd
- From: richard.pieri at gmail.com (Richard Pieri)
- [Discuss] SysVinit vs. systemd
- From: bogstad at pobox.com (Bill Bogstad)
- [Discuss] SysVinit vs. systemd
- From: smallm at panix.com (Mike Small)
- [Discuss] SysVinit vs. systemd
- From: michael.tiernan at gmail.com (Michael Tiernan)
- [Discuss] SysVinit vs. systemd
- From: dsr at randomstring.org (Dan Ritter)
- [Discuss] SysVinit vs. systemd
- From: richard.pieri at gmail.com (Richard Pieri)
- [Discuss] SysVinit vs. systemd
- Prev by Date: [Discuss] SysVinit vs. systemd
- Next by Date: [Discuss] SysVinit vs. systemd
- Previous by thread: [Discuss] SysVinit vs. systemd
- Next by thread: [Discuss] SysVinit vs. systemd
- Index(es):