All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Theodore Y. Ts'o" <tytso@mit.edu>
To: Jan Kara <jack@suse.cz>
Cc: Yang Xu <xuyang2018.jy@cn.fujitsu.com>,
	fstests <fstests@vger.kernel.org>
Subject: Re: generic/269 hangs on lastest upstream kernel
Date: Wed, 19 Feb 2020 10:20:20 -0500	[thread overview]
Message-ID: <20200219152020.GH330201@mit.edu> (raw)
In-Reply-To: <20200219124324.GO16121@quack2.suse.cz>

On Wed, Feb 19, 2020 at 01:43:24PM +0100, Jan Kara wrote:
> This means, fsstress command has queued cache flush request (from
> blkdev_issue_flush()), this has been dispatched to the driver ('D' event)
> but it has never been completed by the driver and so blkdev_issue_flush()
> never returns.
> 
> To debug this further, you probably need to start looking into what happens
> with the request inside QEMU. There's not much I can help you with at this
> point since I'm not an expert there. Do you use image file as a backing store
> or a raw partition?

This is looking more and more like a Qemu bug or a host OS issue.
Yang is using a two year old Qemu (qemu-kvm-2.12.0-32.el8+1900+70997154)
and is using a QCOW backing file.  It also could be a host kernel bug,
although that's less likely.

Yang, any chance you could have a chance to upgrade to a newer version
of Qemu, and see if the problem goes away?  If you have a RHEL support
contract, perhaps you could file a support request with the Red Hat help desk?

	  	      	    	   	   	   - Ted

  reply	other threads:[~2020-02-19 15:21 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-02-11  8:14 generic/269 hangs on lastest upstream kernel Yang Xu
2020-02-12 10:54 ` Jan Kara
2020-02-13  8:49   ` Yang Xu
2020-02-13 17:08     ` Theodore Y. Ts'o
2020-02-14  1:14       ` Yang Xu
2020-02-14 14:05         ` Theodore Y. Ts'o
     [not found]           ` <7adf16bf-d527-1c25-1a24-b4d5e4d757c4@cn.fujitsu.com>
2020-02-18 14:35             ` Theodore Y. Ts'o
2020-02-19 10:57               ` Yang Xu
2020-02-13 21:10     ` Jan Kara
     [not found]       ` <062ac52c-3a16-22ef-6396-53334ed94783@cn.fujitsu.com>
2020-02-14 15:00         ` Jan Kara
2020-02-18  3:25           ` Yang Xu
2020-02-18  8:24             ` Jan Kara
2020-02-18  9:46               ` Yang Xu
2020-02-18 11:03                 ` Jan Kara
2020-02-19 10:09                   ` Yang Xu
     [not found]                     ` <73af3d5c-ca64-3ad3-aee2-1e78ee4fae4a@cn.fujitsu.com>
2020-02-19 12:43                       ` Jan Kara
2020-02-19 15:20                         ` Theodore Y. Ts'o [this message]
2020-02-20  1:35                           ` Yang Xu
2020-02-25  6:03                             ` Yang Xu

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=20200219152020.GH330201@mit.edu \
    --to=tytso@mit.edu \
    --cc=fstests@vger.kernel.org \
    --cc=jack@suse.cz \
    --cc=xuyang2018.jy@cn.fujitsu.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.