From: Jeremy Sanders <jeremy@jeremysanders.net>
To: Dave Chinner <david@fromorbit.com>
Cc: linux-xfs@oss.sgi.com
Subject: Re: bug in fs/xfs/xfs_aops.c:959! (kernel 3.1.5)
Date: Tue, 20 Dec 2011 09:54:42 +0000 [thread overview]
Message-ID: <4EF05B62.7020903@jeremysanders.net> (raw)
In-Reply-To: <20111219221137.GR23662@dastard>
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.
Jeremy
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
next prev parent reply other threads:[~2011-12-20 9:54 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-12-19 9:36 bug in fs/xfs/xfs_aops.c:959! (kernel 3.1.5) Jeremy Sanders
2011-12-19 22:11 ` Dave Chinner
2011-12-20 9:54 ` Jeremy Sanders [this message]
2011-12-28 17:16 ` Christoph Hellwig
2011-12-29 11:07 ` Jeremy Sanders
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4EF05B62.7020903@jeremysanders.net \
--to=jeremy@jeremysanders.net \
--cc=david@fromorbit.com \
--cc=linux-xfs@oss.sgi.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.