The Linux Kernel Mailing List
 help / color / mirror / Atom feed
From: Anand Jain <anand.jain@oracle.com>
To: kernel test robot <xiaolong.ye@intel.com>
Cc: 0day robot <fengguang.wu@intel.com>,
	LKML <linux-kernel@vger.kernel.org>,
	lkp@01.org
Subject: Re: [lkp] [btrfs] 164a91c9be: xfstests.generic.088.fail
Date: Tue, 21 Jun 2016 18:25:00 +0800	[thread overview]
Message-ID: <ddb71dd7-5e57-ab7c-a433-f8ea7a12ed6a@oracle.com> (raw)
In-Reply-To: <20160621021143.GC25382@yexl-desktop>



Thanks for the report.

 > _check_btrfs_filesystem: filesystem on /dev/sda5 is inconsistent (see 
/lkp/benchmarks/xfstests/results//check.full)
 > generic/088	 0s

Ran tests again unfortunately I couldn't reproduce..
---------
generic/088 0s ... 0s
generic/089 21s ... 39s
generic/090 4s ... 4s
generic/091 58s ... 58s
generic/092 1s ... 0s
generic/096	 [not run] xfs_io fzero failed (old kernel/wrong fs?)
generic/098 2s ... 2s
generic/100 18s ... 18s
generic/101	 3s
generic/102	 8s
generic/103	 2s
----------

But a possible scenario .. in systems where rcu_callback itself
could be deferred it needs rcu_barrier(). Fixed this in V2, by
restoring rcu_barrier() and then grace period wait for devices
to close.


>     +mount: /dev/sda6 is already mounted or /fs/scratch busy
::
>     +umount: /dev/sda6: not mounted

This might be different issue, when this happens generally
wipefs all scratch pool devices helps.


Thanks, Anand

      reply	other threads:[~2016-06-21 10:24 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-06-21  2:11 [lkp] [btrfs] 164a91c9be: xfstests.generic.088.fail kernel test robot
2016-06-21 10:25 ` Anand Jain [this message]

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=ddb71dd7-5e57-ab7c-a433-f8ea7a12ed6a@oracle.com \
    --to=anand.jain@oracle.com \
    --cc=fengguang.wu@intel.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lkp@01.org \
    --cc=xiaolong.ye@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