From: bugzilla-daemon@bugzilla.kernel.org
To: linux-xfs@vger.kernel.org
Subject: [Bug 208907] [fstests generic/074 on xfs]: 5.7.10 fails with a hung task on
Date: Fri, 14 Aug 2020 22:41:14 +0000 [thread overview]
Message-ID: <bug-208907-201763-kHPdQlDTLz@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-208907-201763@https.bugzilla.kernel.org/>
https://bugzilla.kernel.org/show_bug.cgi?id=208907
--- Comment #2 from Dave Chinner (david@fromorbit.com) ---
On Fri, Aug 14, 2020 at 06:43:18PM +0000, bugzilla-daemon@bugzilla.kernel.org
wrote:
> Just ssh to kdevops-xfs and run:
>
> cd /var/lib/xfstests/
> ./gendisks.sh -m
> ./check generic/074
>
> Aug 14 18:27:34 kdevops-xfs-dev kernel: XFS (loop16): Mounting V5 Filesystem
> Aug 14 18:27:34 kdevops-xfs-dev kernel: XFS (loop16): Ending clean mount
> Aug 14 18:27:34 kdevops-xfs-dev kernel: xfs filesystem being mounted at
> /media/test supports timestamps until 2038 (0x7fffffff)
> Aug 14 18:28:16 kdevops-xfs-dev kernel: nvme nvme1: I/O 128 QID 2 timeout,
> aborting
> Aug 14 18:28:16 kdevops-xfs-dev kernel: nvme nvme1: Abort status: 0x4001
> Aug 14 18:28:47 kdevops-xfs-dev kernel: nvme nvme1: I/O 128 QID 2 timeout,
> reset controller
Hardware lost an IO. I'm guessing the error handling that reset the
controller failed to error out the bio the lost IO belonged to, so
XFS has hung waiting for it...
Cheers,
Dave.
--
You are receiving this mail because:
You are watching the assignee of the bug.
prev parent reply other threads:[~2020-08-14 22:41 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-08-14 18:43 [Bug 208907] New: [fstests generic/074 on xfs]: 5.7.10 fails with a hung task on bugzilla-daemon
2020-08-14 19:19 ` [Bug 208907] " bugzilla-daemon
2020-08-14 22:41 ` [Bug 208907] New: " Dave Chinner
2020-08-14 22:41 ` bugzilla-daemon [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=bug-208907-201763-kHPdQlDTLz@https.bugzilla.kernel.org/ \
--to=bugzilla-daemon@bugzilla.kernel.org \
--cc=linux-xfs@vger.kernel.org \
/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