xfs
[Top] [All Lists]

Re: real-time device warning

To: Ross Zwisler <ross.zwisler@xxxxxxxxxxxxxxx>
Subject: Re: real-time device warning
From: Dave Chinner <david@xxxxxxxxxxxxx>
Date: Thu, 4 Feb 2016 10:40:21 +1100
Cc: xfs@xxxxxxxxxxx
Delivered-to: xfs@xxxxxxxxxxx
In-reply-to: <20160203231259.GA5137@xxxxxxxxxxxxxxx>
References: <20160203165031.GB29275@xxxxxxxxxxxxxxx> <20160203215555.GF459@dastard> <20160203231259.GA5137@xxxxxxxxxxxxxxx>
User-agent: Mutt/1.5.21 (2010-09-15)
On Wed, Feb 03, 2016 at 04:12:59PM -0700, Ross Zwisler wrote:
> On Thu, Feb 04, 2016 at 08:55:55AM +1100, Dave Chinner wrote:
> > 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
> 
> Ah, I wasn't aware of that work.  Can you please CC me next time so I can give
> you a Tested-by?

Sure, easy to forget cc's when posting a patchbomb(*), especially when
I've got my own test cases that trigger the problem...

Cheers,

Dave.

(*) I do not allow git-send-email to add cc's from commit message
details because that's a silent information leak just waiting to
happen.
-- 
Dave Chinner
david@xxxxxxxxxxxxx

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