[Top] [All Lists]

Re: reproducible xfs/vmap oops

To: Nick Piggin <nickpiggin@xxxxxxxxxxxx>
Subject: Re: reproducible xfs/vmap oops
From: Christoph Hellwig <hch@xxxxxxxxxxxxx>
Date: Wed, 4 Feb 2009 03:30:37 -0500
Cc: Christoph Hellwig <hch@xxxxxxxxxxxxx>, xfs@xxxxxxxxxxx
In-reply-to: <20090204081547.GA21487@xxxxxxxxxxxxx>
References: <20090201081224.GA22398@xxxxxxxxxxxxx> <20090203214711.GA24837@xxxxxxxxxxxxx> <20090203220808.GA9195@xxxxxxxxxxxxx> <200902041648.55603.nickpiggin@xxxxxxxxxxxx> <20090204081547.GA21487@xxxxxxxxxxxxx>
User-agent: Mutt/1.5.18 (2008-05-17)
On Wed, Feb 04, 2009 at 03:15:47AM -0500, Christoph Hellwig wrote:
> On Wed, Feb 04, 2009 at 04:48:55PM +1100, Nick Piggin wrote:
> > OK, I could reproduce this directly with a vmap test. With this patch,
> > I'm no longer able to. (not sure how this mail client goes with attaching
> > patches, sorry if it messes up)
> With that patch applies I run into a different issue:

And later on we run out of vmalloc space a lot getting warnings like

[ 5796.986579] vmap allocation for size 4194304 failed: use
vmalloc=<size> to increase size.
[ 5797.008728] xfs_buf_get_noaddr: failed to map pages

This didn't happen before.  Maybe it's a result of some of the more
lazy TLB flushing?

<Prev in Thread] Current Thread [Next in Thread>