From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from relay.sgi.com (relay1.corp.sgi.com [137.38.102.111]) by oss.sgi.com (Postfix) with ESMTP id 651BF7CA1 for ; Wed, 3 Feb 2016 15:56:15 -0600 (CST) Received: from cuda.sgi.com (cuda2.sgi.com [192.48.176.25]) by relay1.corp.sgi.com (Postfix) with ESMTP id 545438F8039 for ; Wed, 3 Feb 2016 13:56:12 -0800 (PST) Received: from ipmail07.adl2.internode.on.net (ipmail07.adl2.internode.on.net [150.101.137.131]) by cuda.sgi.com with ESMTP id 0YC9Nzo8H4CgA2kK for ; Wed, 03 Feb 2016 13:56:09 -0800 (PST) Date: Thu, 4 Feb 2016 08:55:55 +1100 From: Dave Chinner Subject: Re: real-time device warning Message-ID: <20160203215555.GF459@dastard> References: <20160203165031.GB29275@linux.intel.com> MIME-Version: 1.0 Content-Disposition: inline In-Reply-To: <20160203165031.GB29275@linux.intel.com> List-Id: XFS Filesystem from SGI List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Errors-To: xfs-bounces@oss.sgi.com Sender: xfs-bounces@oss.sgi.com To: Ross Zwisler Cc: xfs@oss.sgi.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