[DRBD-user] drbd network block device deadlock ?

Antonio Anselmi tony.anselmi at gmail.com
Tue Feb 1 17:44:08 CET 2011

Note: "permalinks" may not be as permanent as we would like,
direct links of old sources may well be a few messages off.


OS disk is usually a local device and not managed by drbd, i.e. is not
a backing device.
Unless I'm missing something about your question.

Antonio


--
Lo scopo del lavoro è quello di guadagnarsi il tempo libero  (Aristotele)
The purpose of the job is to gain leisure  (Aristotele)




2011/2/1 Ivan Frain <ivan.frain at euranova.eu>:
> Hi all,
>
> I am currently evaluating DRBD as a storage candidate for highly available
> storage in a virtualized environment.
> It seems like a very good alternative to expensive SAN/NAS.
> I was wondering how DRBD deals with the network block device deadlock
> problem.
> This problem (described here: http://lwn.net/Articles/195416/) can be
> summarized as follows: if the system runs short in memory, it will try to
> write dirty page to disk in order to free memory space.  if the disk is a
> network block device, the dirty page write may need to allocate some other
> memory pages which is not possible since the solution to have more memory
> available was to write the dirty page to disk.
>
> If someone has some information about that problem I'am eager to read it.
>
> Thank you in advance.
>
> BR,
> Ivan
>
>
> _______________________________________________
> drbd-user mailing list
> drbd-user at lists.linbit.com
> http://lists.linbit.com/mailman/listinfo/drbd-user
>
>



More information about the drbd-user mailing list