| To: | Dave Chinner <david@xxxxxxxxxxxxx> |
|---|---|
| Subject: | Re: [4.8 hang] xfstests generic/361 hangs on dax enabled filesystems |
| From: | Dan Williams <dan.j.williams@xxxxxxxxx> |
| Date: | Wed, 3 Aug 2016 19:52:53 -0700 |
| Cc: | Ross Zwisler <ross.zwisler@xxxxxxxxxxxxxxx>, XFS Developers <xfs@xxxxxxxxxxx>, linux-fsdevel <linux-fsdevel@xxxxxxxxxxxxxxx>, "linux-nvdimm@xxxxxxxxxxxx" <linux-nvdimm@xxxxxxxxxxxx> |
| Delivered-to: | xfs@xxxxxxxxxxx |
| Dkim-signature: | v=1; a=rsa-sha256; c=relaxed/relaxed; d=intel-com.20150623.gappssmtp.com; s=20150623; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=0teZmo3JWIW1SxIUujXF5R+48VbEoSXd5nI04kMhf7k=; b=txGJDK97+HkYy7QZ+b96gpRQdnaMfUQ/s9enXrgW1WxLv2ARrnspJ6a/+ossLCSVXa jTTwfgzfpSEfnsA9skCjOX1fQxwylIRF/Z6sYSBGDg1QWV3fMbx8A6JxpyjGYS4/5NOe 5dO8OwtYmppc4b3aKJkrLxjruJznz3XG9W266f79+1j/IvWKRJ3FHSsOZHX2Az3TLrqS VizekpnjmV+xAdq5cgpLgdbWC13mJ/l1KKGn4cbGhvraxp2SqiF+d90eIYwTjc4qT6Jm +NtQAh/O61AZ4ccbWuCfO5apHswBfzY59os+YcLn0S91QgkIMef4cBb8IRHXeojhReNG TxIA== |
| In-reply-to: | <20160803231655.GY16044@dastard> |
| References: | <20160803003354.GP16044@dastard> <20160803171127.GA15876@xxxxxxxxxxxxxxx> <20160803223713.GA22364@xxxxxxxxxxxxxxx> <20160803231655.GY16044@dastard> |
On Wed, Aug 3, 2016 at 4:16 PM, Dave Chinner <david@xxxxxxxxxxxxx> wrote: > On Wed, Aug 03, 2016 at 04:37:13PM -0600, Ross Zwisler wrote: >> On Wed, Aug 03, 2016 at 11:11:27AM -0600, Ross Zwisler wrote: >> > On Wed, Aug 03, 2016 at 10:33:54AM +1000, Dave Chinner wrote: >> > > Hi folks, >> > > >> > > Just hit a reproducable hang in generic/361. Essentially this on >> > > a 8GB pmem device: >> > > >> > > mkfs.xfs -f /dev/pmem1 >> > > mount -o dax /dev/pmem1 /mnt/scratch >> > > xfs_io -f -c "truncate 1g" test.img >> > > losetup -f --show /mnt/scratch/test.img >> > > mkfs.xfs -f /dev/loop0 >> > > >> > > And the mkfs.xfs command hangs with a discard that never completes: > .... >> > > This only reproduces when the underlying filesystem is mounted with >> > > -o dax, so there is a bad interaction with loop devices and DAX >> > > occurring somewhere. generic/361 is a recent test (committed june 14) >> > > so this probably hasn't actually been tested until now. >> > > >> > > I haven't got time to look at this right now, hence the report. >> > >> > Cool, thanks for the report. I've reproduced this with linux/master, and >> > the >> > test passes with v4.7. >> > >> > Running a bisect... >> >> This bisected to a commit to the block layer code. I've sent a bug report to >> the author of the commit. > > And the commit id is ...? c2df40dfb8c0 drivers: use req op accessor |
| <Prev in Thread] | Current Thread | [Next in Thread> |
|---|---|---|
| ||
| Previous by Date: | xfstests xfs fuzzers fail with DAX, Xiong Zhou |
|---|---|
| Next by Date: | Re: xfstests xfs fuzzers fail with DAX, Eric Sandeen |
| Previous by Thread: | Re: [4.8 hang] xfstests generic/361 hangs on dax enabled filesystems, Dave Chinner |
| Next by Thread: | Re: [4.8 hang] xfstests generic/361 hangs on dax enabled filesystems, Christoph Hellwig |
| Indexes: | [Date] [Thread] [Top] [All Lists] |