On Thu, Sep 26, 2013 at 10:31:56AM -0700, Frank Mayhar wrote: > Uh, huh. And what about when (not if) _that_ fails? (For one thing, > what if the stuckness caused by the queued I/O prevents the binary from > being successfully pulled in from storage?) Lock the daemon in memory (or launch from ramdisk), don't allocate any new memory while it's doing critical monitoring, tell the OOM killer not to kill it, set high/real-time priority etc. lvm2 and multipath-tools use some of these techniques and seem to cope OK. Alasdair -- dm-devel mailing list dm-devel@xxxxxxxxxx https://www.redhat.com/mailman/listinfo/dm-devel
