From: Jan Kara <jack@suse.cz>
To: Theodore Ts'o <tytso@mit.edu>
Cc: Jan Kara <jack@suse.cz>,
linux-ext4@vger.kernel.org, linux-nvdimm@ml01.01.org,
Vishal Verma <vishal.l.verma@intel.com>,
Ross Zwisler <ross.zwisler@linux.intel.com>,
Dan Williams <dan.j.williams@intel.com>,
linux-fsdevel@vger.kernel.org
Subject: Re: [PATCH 0/4] ext4: DAX fixes
Date: Mon, 16 May 2016 11:35:25 +0200 [thread overview]
Message-ID: <20160516093525.GD12026@quack2.suse.cz> (raw)
In-Reply-To: <20160513135600.GA2996@thunk.org>
On Fri 13-05-16 09:56:00, Ted Tso wrote:
> On Fri, May 13, 2016 at 01:24:19AM -0400, Theodore Ts'o wrote:
> > Queued and I'm running tests before I push them out. The patches
> > passed the smoke tests[1], and the full tests should be running for the
> > next seven hours or so at: http://104.197.222.91
>
> So the good news is that the full tests ("gce-xfstests full") look
> really good[1]) Unfortunately the DAX tests ("gce-xfstests -c dax -g
> auto") show a regression. Is this expected? (i.e., were you
> expecting test regressions that will be fixed by the DAX patch
> series?)
No, I was not expecting to get new xfstests failures from just ext4
patches. That being said I didn't test ext4 patches on their own, just in
combination with other DAX changes so there may be some interaction I
forgot about. I'll see whether I can reproduce the failures and understand
what's going on. Thanks for having a look!
Honza
> Before this patch series:
>
> BEGIN TEST dax: Ext4 4k block using DAX Fri May 13 08:01:57 EDT 2016
> Failures: generic/250 generic/252 generic/299 generic/338
>
> After the patch series:
>
> CMDLINE: -c dax -g auto
> FSTESTVER: e2fsprogs v1.43-WIP-2015-05-18-64-g2334bd3 (Sat, 5 Sep 2015 22:21:35 -0400)
> FSTESTVER: fio fio-2.6-8-ge6989e1 (Thu, 4 Feb 2016 12:09:48 -0700)
> FSTESTVER: quota 67fd9cc (Mon, 4 Apr 2016 00:32:39 -0400)
> FSTESTVER: xfsprogs v4.3.0 (Mon, 23 Nov 2015 15:24:24 +1100)
> FSTESTVER: xfstests-bld ccae8d1 (Tue, 26 Apr 2016 00:42:18 -0400)
> FSTESTVER: xfstests linux-v3.8-1010-g97dd2d8 (Wed, 27 Apr 2016 00:04:44 -0400)
> FSTESTVER: kernel 4.6.0-rc4-ext4-00022-gaacd0c8 #282 SMP Fri May 13 00:52:07 EDT 2016 x86_64
> FSTESTCFG: "dax"
> FSTESTSET: "-g auto"
> FSTESTEXC: ""
> FSTESTOPT: "aex"
> MNTOPTS: ""
> CPUS: "4"
> MEM: "13052.8"
> MEM: 26 GB (Max capacity)
> BEGIN TEST dax: Ext4 4k block using DAX Fri May 13 01:21:58 EDT 2016
> Failures: generic/075 generic/091 generic/112 generic/127 generic/231 generic/250 generic/252 generic/263 generic/299 generic/338 generic/340
>
> - Ted
>
> [1] CMDLINE: full
> FSTESTVER: e2fsprogs v1.43-WIP-2015-05-18-64-g2334bd3 (Sat, 5 Sep 2015 22:21:35 -0400)
> FSTESTVER: fio fio-2.6-8-ge6989e1 (Thu, 4 Feb 2016 12:09:48 -0700)
> FSTESTVER: quota 67fd9cc (Mon, 4 Apr 2016 00:32:39 -0400)
> FSTESTVER: xfsprogs v4.3.0 (Mon, 23 Nov 2015 15:24:24 +1100)
> FSTESTVER: xfstests-bld ccae8d1 (Tue, 26 Apr 2016 00:42:18 -0400)
> FSTESTVER: xfstests linux-v3.8-1010-g97dd2d8 (Wed, 27 Apr 2016 00:04:44 -0400)
> FSTESTVER: kernel 4.6.0-rc4-ext4-00018-g816cd71 #279 SMP Thu May 5 22:45:36 EDT 2016 x86_64
> FSTESTCFG: "4k 1k ext3 encrypt nojournal ext3conv adv dioread_nolock data_journal bigalloc bigalloc_1k"
> FSTESTSET: "-g auto"
> FSTESTEXC: ""
> FSTESTOPT: "aex"
> MNTOPTS: ""
> CPUS: "2"
> MEM: "7497.07"
> MEM: 7680 MB (Max capacity)
> BEGIN TEST 4k: Ext4 4k block Thu May 5 22:52:10 EDT 2016
> Passed all 212 tests
> BEGIN TEST 1k: Ext4 1k block Thu May 5 23:38:50 EDT 2016
> Failures: generic/018
> BEGIN TEST ext3: Ext4 4k block emulating ext3 Fri May 6 00:30:11 EDT 2016
> Passed all 167 tests
> BEGIN TEST encrypt: Ext4 encryption Fri May 6 01:15:41 EDT 2016
> Failures: ext4/020
> BEGIN TEST nojournal: Ext4 4k block w/ no journal Fri May 6 01:40:25 EDT 2016
> Failures: ext4/301
> BEGIN TEST ext3conv: Ext4 4k block w/nodelalloc and no flex_bg Fri May 6 02:20:39 EDT 2016
> Passed all 212 tests
> BEGIN TEST adv: Ext4 advanced features (inline_data, metadata_csum, 64bit) Fri May 6 03:06:25 EDT 2016
> Passed all 211 tests
> BEGIN TEST dioread_nolock: Ext4 4k block w/dioread_nolock Fri May 6 03:53:34 EDT 2016
> Passed all 212 tests
> BEGIN TEST data_journal: Ext4 4k block w/data=journal Fri May 6 04:40:52 EDT 2016
> Failures: ext4/271 generic/018
> BEGIN TEST bigalloc: Ext4 4k block w/bigalloc Fri May 6 05:28:12 EDT 2016
> Failures: ext4/004 generic/204 generic/219 generic/235 generic/273
> BEGIN TEST bigalloc_1k: Ext4 1k block w/bigalloc Fri May 6 06:18:54 EDT 2016
> Failures: ext4/004 generic/204 generic/235 generic/270
--
Jan Kara <jack@suse.com>
SUSE Labs, CR
next prev parent reply other threads:[~2016-05-16 9:35 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-05-11 9:39 [PATCH 0/4] ext4: DAX fixes Jan Kara
2016-05-11 9:39 ` [PATCH 1/4] ext4: Handle transient ENOSPC properly for DAX Jan Kara
2016-05-11 9:39 ` [PATCH 2/4] ext4: Fix race in transient ENOSPC detection Jan Kara
2016-05-11 9:39 ` [PATCH 3/4] ext4: Refactor direct IO code Jan Kara
2016-05-11 9:39 ` [PATCH 4/4] ext4: Pre-zero allocated blocks for DAX IO Jan Kara
2016-05-13 5:24 ` [PATCH 0/4] ext4: DAX fixes Theodore Ts'o
2016-05-13 13:56 ` Theodore Ts'o
2016-05-16 9:35 ` Jan Kara [this message]
2016-05-16 14:26 ` Jan Kara
2016-05-16 15:08 ` Theodore Ts'o
2016-05-16 15:13 ` Dan Williams
2016-05-16 15:59 ` Jan Kara
2016-05-16 18:29 ` Dan Williams
2016-05-16 20:47 ` Theodore Ts'o
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=20160516093525.GD12026@quack2.suse.cz \
--to=jack@suse.cz \
--cc=dan.j.williams@intel.com \
--cc=linux-ext4@vger.kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-nvdimm@ml01.01.org \
--cc=ross.zwisler@linux.intel.com \
--cc=tytso@mit.edu \
--cc=vishal.l.verma@intel.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;
as well as URLs for NNTP newsgroup(s).