[Top] [All Lists]

Re: bug in fs/xfs/xfs_aops.c:959! (kernel 3.1.5)

To: Dave Chinner <david@xxxxxxxxxxxxx>
Subject: Re: bug in fs/xfs/xfs_aops.c:959! (kernel 3.1.5)
From: Jeremy Sanders <jeremy@xxxxxxxxxxxxxxxxx>
Date: Tue, 20 Dec 2011 09:54:42 +0000
Cc: linux-xfs@xxxxxxxxxxx
In-reply-to: <20111219221137.GR23662@dastard>
References: <jcn0ip$hsk$1@xxxxxxxxxxxxxxx> <20111219221137.GR23662@dastard>
User-agent: Mozilla/5.0 (X11; Linux x86_64; rv:8.0) Gecko/20111115 Thunderbird/8.0

Dave Chinner wrote:

> There was a line above this about an assert failure? What was it?

Unfortunately there's are no other messages above this in /var/log/messages. I checked carefully for any asserts.

> If it tripped the assert I think it did, it looks like the system
> was trying to do write IO into a hole in the file. What workload
> were you running, and what are the details of your machine + storage
> config?

It's xfs (nobarrier opts) running from a Linux MD software raid device (no LVM). It uses raid6 on 11 1TB discs, using a chunk size of 32 kB. The filesystem is 88% full. The discs are on a 3ware 9650SE controller.

The array has a set of backup "snapshots" with hard links created using the rsync --link-dest feature. We also used --sparse when doing the rsyncs. We have snapshots for a set of user directories, one for each day.

The message occured while rsync was writing to the array (creating the snapshots) and it was being read by rsync or a tar to tar pipe to a second btrfs array.


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