On Wed, Jun 17, 2009 at 02:39:06PM +0400, Michael Tokarev wrote:Justin Piszcz wrote:Very similar load was here -- not xfsdump but tar and dump of an ext3
On Wed, 17 Jun 2009, Michael Tokarev wrote:
Michael Tokarev wrote:Hello, I am also running XFS on 2.6.29.x x86-64.Justin Piszcz wrote:...
Justin, by the way, what's the underlying filesystem on the server?
I've seen this error on 2 machines already (both running 2.6.29.x x86-64),
and in both cases the filesystem on the server was xfs. May this be
related somehow to http://bugzilla.kernel.org/show_bug.cgi?id=13375 ?
That one is different, but also about xfs and nfs. I'm trying to
reproduce the problem on different filesystem...
For me, the error happened when I was running an XFSDUMP from a client (and dumping) the stream over NFS to the XFS server/filesystem. This is typically when the error occurs or during heavy I/O.
And no, it's NOT xfs-related: I can trigger the same issue easily on
ext4 as well. About 20 minutes of running 'dump' of another fs
to the nfs mount and voila, nfs server reports the same page allocation
failure. Note that all file operations are still working, i.e. it
produces good (not corrupted) files on the server.
There's a possibly related report for 2.6.30 here: