From: BillStuff <billstuff2001@sbcglobal.net>
To: Brian Foster <bfoster@redhat.com>
Cc: xfs@oss.sgi.com
Subject: Re: dmesg error in xfs_aops.c on kernel 3.14.21
Date: Sun, 12 Oct 2014 14:00:18 -0500 [thread overview]
Message-ID: <543ACFC2.2090308@sbcglobal.net> (raw)
In-Reply-To: <20141012140704.GA35667@bfoster.bfoster>
On 10/12/2014 09:07 AM, Brian Foster wrote:
> On Sat, Oct 11, 2014 at 01:59:27PM -0500, BillStuff wrote:
>> Hi,
>>
>> I'm running 3.14.21, and got these traces in dmesg; they appear to be from
>> xfs:
>>
>> [56180.816526] ------------[ cut here ]------------
>> [56180.816550] WARNING: CPU: 5 PID: 67 at fs/xfs/xfs_aops.c:1172
>
> if (WARN_ON(delalloc))
> return 0;
>
> So this generally looks like stale delalloc blocks on a page that is
> reclaimed/invalidated or otherwise expected to be clean. We've been
> seeing this a lot over the past few kernel releases and there have been
> a variety of fixes in error paths and such so it's hard to say precisely
> what might be causing this. Some examples:
>
> aad3f375 xfs: xfs_vm_write_end truncates too much on failure
> 72ab70a1 xfs: write failure beyond EOF truncates too much data
> 4ab9ed57 xfs: kill buffers over failed write ranges properly
>
> It looks like those are in the stable tree as of 3.15, so you could give
> that a try and see if it helps. Otherwise, can you post xfs_info for the
> filesytem? Do you have particular workloads or sequences of operations
> that tend to reproduce this?
>
> Brian
>
Thanks Brian,
I'll try out those fixes.
The filesystem is home theater recordings on a 6 disk raid5 array:
meta-data=/dev/md3 isize=256 agcount=81,
agsize=15237264 blks
= sectsz=4096 attr=2
data = bsize=4096 blocks=1218981920, imaxpct=5
= sunit=16 swidth=80 blks
naming =version 2 bsize=4096 ascii-ci=0
log =internal bsize=4096 blocks=32768, version=2
= sectsz=4096 sunit=1 blks, lazy-count=0
realtime =none extsz=131072 blocks=0, rtextents=0
I believe it was just starting a recording when I got this message.
-Bill
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
next prev parent reply other threads:[~2014-10-12 19:00 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-11 18:59 dmesg error in xfs_aops.c on kernel 3.14.21 BillStuff
2014-10-12 14:07 ` Brian Foster
2014-10-12 19:00 ` BillStuff [this message]
2014-10-13 11:21 ` Brian Foster
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=543ACFC2.2090308@sbcglobal.net \
--to=billstuff2001@sbcglobal.net \
--cc=bfoster@redhat.com \
--cc=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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox