[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date: Fri, 9 Sep 2016 10:03:27 -0400
From: Theodore Ts'o <tytso@....edu>
To: Jan Kara <jack@...e.cz>
Cc: Ross Zwisler <ross.zwisler@...ux.intel.com>,
Xiao Guangrong <guangrong.xiao@...ux.intel.com>,
linux-ext4@...r.kernel.org,
Dan Williams <dan.j.williams@...el.com>,
Yumei Huang <yuhuang@...hat.com>, KVM <kvm@...r.kernel.org>,
"linux-nvdimm@...ts.01.org" <linux-nvdimm@...1.01.org>,
"qemu-devel@...gnu.org" <qemu-devel@...gnu.org>,
LKML <linux-kernel@...r.kernel.org>,
Linux ACPI <linux-acpi@...r.kernel.org>,
Stefan Hajnoczi <stefanha@...hat.com>
Subject: Re: DAX can not work on virtual nvdimm device
On Fri, Sep 09, 2016 at 11:19:25AM +0200, Jan Kara wrote:
> > > > > 1. make the guest kernel based on your tree, the top commit is
> > > > > 10d7902fa0e82b (dax: unmap/truncate on device shutdown) and
> > > > > the config file can be found in this thread.
What git tree is 10d7902fa0e82b from?
> Hum, nothing unusual in there. I've tried reproducing on a local SLE11 SP3
> machine (which is from about the same time) but everything works as
> expected there. Shrug...
I just tried reproducing it via "gce-xfstests --pmem-device shell"
with a downgraded e2fsprogs to stock upstream 1.42.12, and I can't
reproduce it with the ext4.git tree. I'm not sure whether the git
commit is critical, though. Is this a regression that was working
before?
Or it's possible that Red Hat did something weird with the CentOS 6
e2fsprogs....
- Ted
Powered by blists - more mailing lists