From: Yang Xu <xuyang2018.jy@cn.fujitsu.com>
To: "Theodore Y. Ts'o" <tytso@mit.edu>, Jan Kara <jack@suse.cz>
Cc: fstests <fstests@vger.kernel.org>
Subject: Re: generic/269 hangs on lastest upstream kernel
Date: Tue, 25 Feb 2020 14:03:58 +0800 [thread overview]
Message-ID: <e844b86b-658e-519a-d8e7-f099fdc353bb@cn.fujitsu.com> (raw)
In-Reply-To: <27bea3a0-7a72-a924-644a-eece4bef97a2@cn.fujitsu.com>
on 2020/02/20 9:35, Yang Xu wrote:
>
>
> on 2020/02/19 23:20, Theodore Y. Ts'o wrote:
>> 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?
> Of course, I will update lastest qemu to test.(I don't have their support).
Hi Ted, Jan
I have updated lastest qemu(4.2.0), it still hangs. But I think it
is not fs problem. Because it only failed when disk uses IDE bus, I use
scsi bus, it passed. Thanks for your analysis and help.
Best Regards
Yang Xu
>>
>> - Ted
>>
>>
>
>
prev parent reply other threads:[~2020-02-25 6:04 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
2020-02-20 1:35 ` Yang Xu
2020-02-25 6:03 ` Yang Xu [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=e844b86b-658e-519a-d8e7-f099fdc353bb@cn.fujitsu.com \
--to=xuyang2018.jy@cn.fujitsu.com \
--cc=fstests@vger.kernel.org \
--cc=jack@suse.cz \
--cc=tytso@mit.edu \
/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).