From: Dave Chinner <david@fromorbit.com>
To: Ross Zwisler <ross.zwisler@linux.intel.com>
Cc: xfs@oss.sgi.com
Subject: Re: real-time device warning
Date: Thu, 4 Feb 2016 08:55:55 +1100 [thread overview]
Message-ID: <20160203215555.GF459@dastard> (raw)
In-Reply-To: <20160203165031.GB29275@linux.intel.com>
On Wed, Feb 03, 2016 at 09:50:31AM -0700, Ross Zwisler wrote:
> I've been doing some more real-time device testing with XFS, and I was able to
> get past the BUG I reported here:
>
> http://www.spinics.net/lists/xfs/msg37445.html
>
> by setting CONFIG_XFS_DEBUG=n as Dave suggested.
>
> After that I/O seems to work, although it doesn't look like the DAX mount
> option is applied to I/Os that go to the real-time device.
>
> After the first I/O, though, the following warning is hit:
>
> [ 413.086897] XFS (ram1): _xfs_buf_ioapply: no ops on block 0xa0/0x8
This series:
http://oss.sgi.com/archives/xfs/2016-02/msg00017.html
-Dave.
--
Dave Chinner
david@fromorbit.com
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
next prev parent reply other threads:[~2016-02-03 21:56 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-03 16:50 real-time device warning Ross Zwisler
2016-02-03 21:55 ` Dave Chinner [this message]
2016-02-03 23:12 ` Ross Zwisler
2016-02-03 23:40 ` Dave Chinner
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=20160203215555.GF459@dastard \
--to=david@fromorbit.com \
--cc=ross.zwisler@linux.intel.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