[dm-devel] Re: more multipath deadlocks -- this time involving memory
Alasdair G Kergon
agk at redhat.com
Tue Mar 22 20:38:57 UTC 2005
On Mon, Mar 21, 2005 at 09:34:20PM -0500, goggin, edward wrote:
> I see three separate instances of the problem being plausible,
We went through similar issues with lvm2's pvmove (on 2.4) and eventually
fixed it such that we could no longer lock up the machine while testing
under low memory. That's not to say we covered every possible problem
though.
> The first problem scenario involves a deadlock between multipathd and
> syslogd.
By default, pvmove turns off logging during the critical sections of code.
[There's an option to turn it back on if you need it. I also did some
work on code to log to pre-allocated filespace with O_DIRECT.]
> The second scenario involves the potential for multipathd,
> multipath,
> or any of the executables invoked by multipath to be deadlocked trying doing
> synchronous page reclamation while allocating memory pages for user or
> kernel heap memory in a system with a high degree of memory contention
pvmove avoids allocating memory (incl. extending stack) in critical
sections. (It pre-allocates sufficient locked memory in advance.)
Alasdair
--
agk at redhat.com
More information about the dm-devel
mailing list