Re: Kernel deadlock using nbd over acenic driver.

Oliver Xymoron (oxymoron@waste.org)
Thu, 16 May 2002 09:29:49 -0500 (CDT)


On Thu, 16 May 2002, Peter T. Breuer wrote:

> "Oliver Xymoron wrote:"
> > If the system runs out of memory, it may try to flush pages that are
> > queued to your NBD device. That will try to allocate more memory for
> > sending packets, which will fail, meaning the VM can never make progress
> > freeing pages. Now your box is dead.
>
> The system can avoid this by
>
> a) not flushing sync (i.e. giving up on pages that won't flush immediately)
> b) being nondeterministic about it .. not always retrying the same
> thing again and again.

Helpful but insufficient. What is to stop getting into a situation where
_all_ memory that is pageable is only pageable via network? Even if you
have a big box, if you do large streaming writes to about 20 NBD devices,
you'll discover that each device queue can hold many megabytes of dirty
data.. Try pulling out your ethernet cable for a moment and watch the
thing strangle itself.

Harder to get into this situation with NFS, but still doable.

-- 
 "Love the dolphins," she advised him. "Write by W.A.S.T.E.."

- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/