Bug 1632353

Created attachment 1486446 [details]
File: backtrace

Created attachment 1486447 [details]
File: cgroup

Created attachment 1486448 [details]
File: core_backtrace

Created attachment 1486449 [details]
File: cpuinfo

Created attachment 1486450 [details]
File: dso_list

Created attachment 1486451 [details]
File: environ

Created attachment 1486452 [details]
File: limits

Created attachment 1486453 [details]
File: maps

Created attachment 1486454 [details]
File: mountinfo

Created attachment 1486455 [details]
File: open_fds

Created attachment 1486456 [details]
File: proc_pid_status

Created attachment 1486457 [details]
File: smart_data

Created attachment 1486458 [details]
File: var_log_messages

*** Bug 1638461 has been marked as a duplicate of this bug. ***

Similar problem has been detected:

Runninng KVM virtual machine on an external disk - which hung - this has happened before
Disk is spinning with no in/ out activity apparent
Trying to shutdown virtual machine some how produced the following:-

PAUSE

Error pausing domain: Timed out during operation: cannot acquire state change lock (held by remoteDispatchDomainSuspend)

Traceback (most recent call last):
  File "/usr/share/virt-manager/virtManager/asyncjob.py", line 89, in cb_wrapper
    callback(asyncjob, *args, **kwargs)
  File "/usr/share/virt-manager/virtManager/asyncjob.py", line 125, in tmpcb
    callback(*args, **kwargs)
  File "/usr/share/virt-manager/virtManager/libvirtobject.py", line 82, in newfn
    ret = fn(self, *args, **kwargs)
  File "/usr/share/virt-manager/virtManager/domain.py", line 1512, in suspend
    self._backend.suspend()
  File "/usr/lib64/python2.7/site-packages/libvirt.py", line 2681, in suspend
    if ret == -1: raise libvirtError ('virDomainSuspend() failed', dom=self)
libvirtError: Timed out during operation: cannot acquire state change lock (held by remoteDispatchDomainSuspend)


FORCE OFF

Error shutting down domain: Failed to terminate process 1564 with SIGKILL: Device or resource busy

Traceback (most recent call last):
  File "/usr/share/virt-manager/virtManager/asyncjob.py", line 89, in cb_wrapper
    callback(asyncjob, *args, **kwargs)
  File "/usr/share/virt-manager/virtManager/asyncjob.py", line 125, in tmpcb
    callback(*args, **kwargs)
  File "/usr/share/virt-manager/virtManager/libvirtobject.py", line 82, in newfn
    ret = fn(self, *args, **kwargs)
  File "/usr/share/virt-manager/virtManager/domain.py", line 1489, in destroy
    self._backend.destroy()
  File "/usr/lib64/python2.7/site-packages/libvirt.py", line 1143, in destroy
    if ret == -1: raise libvirtError ('virDomainDestroy() failed', dom=self)
libvirtError: Failed to terminate process 1564 with SIGKILL: Device or resource busy

After that above I attempted to start gnome-disks - which failed with this bug report

reporter:       libreport-2.9.5
backtrace_rating: 4
cmdline:        /usr/bin/gnome-disks --gapplication-service
crash_function: gdu_application_ensure_client
executable:     /usr/bin/gnome-disks
journald_cursor: s=5455a2849dce4885ba0d16edc45eb939;i=5fd320;b=ea6b441c5afd47f4902857f924021618;m=c7a4d3599;t=58635e418b565;x=99ea39aab09b98bc
kernel:         5.0.5-100.fc28.x86_64
package:        gnome-disk-utility-3.28.3-1.fc28
reason:         gnome-disks killed by SIGTRAP
rootdir:        /
runlevel:       N 5
type:           CCpp
uid:            1001

I think the harddrive is failing...  Which would mean this stuff isn't connected with this bug - I wonder if someone could confirm that - see in particular the text 'FAILING_NOW' below...

[root@Xmachine ~]# smartctl -l selftest /dev/sdb
smartctl 6.6 2017-11-05 r4594 [x86_64-linux-5.0.5-100.fc28.x86_64] (local build)
Copyright (C) 2002-17, Bruce Allen, Christian Franke, www.smartmontools.org

=== START OF READ SMART DATA SECTION ===
SMART Self-test log structure revision number 1
Num  Test_Description    Status                  Remaining  LifeTime(hours)  LBA_of_first_error
# 1  Extended offline    Aborted by host               90%     28196         -
# 2  Extended offline    Aborted by host               90%     27954         -

[root@Xmachine ~]# smartctl -a /dev/sdb
smartctl 6.6 2017-11-05 r4594 [x86_64-linux-5.0.5-100.fc28.x86_64] (local build)
Copyright (C) 2002-17, Bruce Allen, Christian Franke, www.smartmontools.org

=== START OF INFORMATION SECTION ===
Model Family:     Western Digital RE2 Serial ATA
Device Model:     WDC WD7500AYYS-01RCA0
Serial Number:    WD-WCAPT0894689
LU WWN Device Id: 5 0014ee 2ac2bb6df
Firmware Version: 30.04G30
User Capacity:    750,156,374,016 bytes [750 GB]
Sector Size:      512 bytes logical/physical
Device is:        In smartctl database [for details use: -P show]
ATA Version is:   ATA/ATAPI-7 (minor revision not indicated)
Local Time is:    Thu Apr 11 01:51:07 2019 BST
SMART support is: Available - device has SMART capability.
SMART support is: Enabled

=== START OF READ SMART DATA SECTION ===
SMART overall-health self-assessment test result: PASSED
See vendor-specific Attribute list for marginal Attributes.

General SMART Values:
Offline data collection status:  (0x85)	Offline data collection activity
					was aborted by an interrupting command from host.
					Auto Offline Data Collection: Enabled.
Self-test execution status:      (  25)	The self-test routine was aborted by
					the host.
Total time to complete Offline 
data collection: 		(15960) seconds.
Offline data collection
capabilities: 			 (0x7b) SMART execute Offline immediate.
					Auto Offline data collection on/off support.
					Suspend Offline collection upon new
					command.
					Offline surface scan supported.
					Self-test supported.
					Conveyance Self-test supported.
					Selective Self-test supported.
SMART capabilities:            (0x0003)	Saves SMART data before entering
					power-saving mode.
					Supports SMART auto save timer.
Error logging capability:        (0x01)	Error logging supported.
					General Purpose Logging supported.
Short self-test routine 
recommended polling time: 	 (   2) minutes.
Extended self-test routine
recommended polling time: 	 ( 198) minutes.
Conveyance self-test routine
recommended polling time: 	 (   6) minutes.
SCT capabilities: 	       (0x303f)	SCT Status supported.
					SCT Error Recovery Control supported.
					SCT Feature Control supported.
					SCT Data Table supported.

SMART Attributes Data Structure revision number: 16
Vendor Specific SMART Attributes with Thresholds:
ID# ATTRIBUTE_NAME          FLAG     VALUE WORST THRESH TYPE      UPDATED  WHEN_FAILED RAW_VALUE
  1 Raw_Read_Error_Rate     0x000f   200   200   051    Pre-fail  Always       -       0
  3 Spin_Up_Time            0x0003   195   189   021    Pre-fail  Always       -       7250
  4 Start_Stop_Count        0x0032   100   100   000    Old_age   Always       -       285
  5 Reallocated_Sector_Ct   0x0033   200   200   140    Pre-fail  Always       -       0
  7 Seek_Error_Rate         0x000e   200   200   051    Old_age   Always       -       0
  9 Power_On_Hours          0x0032   062   062   000    Old_age   Always       -       28196
 10 Spin_Retry_Count        0x0012   100   100   051    Old_age   Always       -       0
 11 Calibration_Retry_Count 0x0012   100   100   051    Old_age   Always       -       0
 12 Power_Cycle_Count       0x0032   100   100   000    Old_age   Always       -       142
192 Power-Off_Retract_Count 0x0032   200   200   000    Old_age   Always       -       52
193 Load_Cycle_Count        0x0032   200   200   000    Old_age   Always       -       286
194 Temperature_Celsius     0x0022   113   104   000    Old_age   Always       -       39
196 Reallocated_Event_Count 0x0032   200   200   000    Old_age   Always       -       0
197 Current_Pending_Sector  0x0012   200   200   000    Old_age   Always       -       40
198 Offline_Uncorrectable   0x0010   200   200   000    Old_age   Offline      -       37
199 UDMA_CRC_Error_Count    0x003e   200   200   000    Old_age   Always       -       0
200 Multi_Zone_Error_Rate   0x0008   015   015   051    Old_age   Offline  FAILING_NOW 13934

SMART Error Log Version: 1
ATA Error Count: 3
	CR = Command Register [HEX]
	FR = Features Register [HEX]
	SC = Sector Count Register [HEX]
	SN = Sector Number Register [HEX]
	CL = Cylinder Low Register [HEX]
	CH = Cylinder High Register [HEX]
	DH = Device/Head Register [HEX]
	DC = Device Command Register [HEX]
	ER = Error register [HEX]
	ST = Status register [HEX]
Powered_Up_Time is measured from power on, and printed as
DDd+hh:mm:SS.sss where DD=days, hh=hours, mm=minutes,
SS=sec, and sss=millisec. It "wraps" after 49.710 days.

Error 3 occurred at disk power-on lifetime: 28190 hours (1174 days + 14 hours)
  When the command that caused the error occurred, the device was active or idle.

  After command completion occurred, registers were:
  ER ST SC SN CL CH DH
  -- -- -- -- -- -- --
  40 51 00 c9 e2 34 40  Error: UNC at LBA = 0x0034e2c9 = 3465929

  Commands leading to the command that caused the error were:
  CR FR SC SN CL CH DH DC   Powered_Up_Time  Command/Feature_Name
  -- -- -- -- -- -- -- --  ----------------  --------------------
  60 10 00 f0 e3 34 4f 00      04:06:57.787  READ FPDMA QUEUED
  60 f0 40 00 e3 34 4f 00      04:06:57.787  READ FPDMA QUEUED
  61 18 38 20 30 3f 4b 00      04:06:57.787  WRITE FPDMA QUEUED
  60 10 08 f0 e2 34 4f 00      04:06:57.786  READ FPDMA QUEUED
  60 f0 58 00 e2 34 4f 00      04:06:57.786  READ FPDMA QUEUED

Error 2 occurred at disk power-on lifetime: 28179 hours (1174 days + 3 hours)
  When the command that caused the error occurred, the device was active or idle.

  After command completion occurred, registers were:
  ER ST SC SN CL CH DH
  -- -- -- -- -- -- --
  40 51 40 8e 3d 4f 40  Error: UNC at LBA = 0x004f3d8e = 5193102

  Commands leading to the command that caused the error were:
  CR FR SC SN CL CH DH DC   Powered_Up_Time  Command/Feature_Name
  -- -- -- -- -- -- -- --  ----------------  --------------------
  60 08 00 88 3d 4f 4f 00      04:16:29.533  READ FPDMA QUEUED
  e7 08 00 28 33 7b 00 00      04:16:29.463  FLUSH CACHE
  61 58 08 10 70 3c 4b 00      04:16:21.736  WRITE FPDMA QUEUED
  60 08 00 80 3d 4f 4f 00      04:16:21.736  READ FPDMA QUEUED
  61 10 08 88 8e 87 2b 00      04:16:21.736  WRITE FPDMA QUEUED

Error 1 occurred at disk power-on lifetime: 28179 hours (1174 days + 3 hours)
  When the command that caused the error occurred, the device was active or idle.

  After command completion occurred, registers were:
  ER ST SC SN CL CH DH
  -- -- -- -- -- -- --
  40 51 40 80 3d 4f 40  Error: UNC 64 sectors at LBA = 0x004f3d80 = 5193088

  Commands leading to the command that caused the error were:
  CR FR SC SN CL CH DH DC   Powered_Up_Time  Command/Feature_Name
  -- -- -- -- -- -- -- --  ----------------  --------------------
  25 03 40 80 3d 4f 4f 00      04:16:17.039  READ DMA EXT
  ef 03 46 08 ff 70 00 00      04:16:17.039  SET FEATURES [Set transfer mode]
  ef 03 0c 08 ff 70 00 00      04:16:17.039  SET FEATURES [Set transfer mode]
  ec 40 40 08 ff 70 00 00      04:16:17.039  IDENTIFY DEVICE
  60 40 08 80 3d 4f 4f 00      04:15:46.516  READ FPDMA QUEUED

SMART Self-test log structure revision number 1
Num  Test_Description    Status                  Remaining  LifeTime(hours)  LBA_of_first_error
# 1  Extended offline    Aborted by host               90%     28196         -
# 2  Extended offline    Aborted by host               90%     27954         -

SMART Selective self-test log data structure revision number 1
 SPAN  MIN_LBA  MAX_LBA  CURRENT_TEST_STATUS
    1        0        0  Not_testing
    2        0        0  Not_testing
    3        0        0  Not_testing
    4        0        0  Not_testing
    5        0        0  Not_testing
Selective self-test flags (0x0):
  After scanning selected spans, do NOT read-scan remainder of disk.
If Selective self-test is pending on power-up, resume after 0 minute delay.

[root@Xmachine ~]#

This message is a reminder that Fedora 28 is nearing its end of life.
On 2019-May-28 Fedora will stop maintaining and issuing updates for
Fedora 28. It is Fedora's policy to close all bug reports from releases
that are no longer maintained. At that time this bug will be closed as
EOL if it remains open with a Fedora 'version' of '28'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version.

Thank you for reporting this issue and we are sorry that we were not 
able to fix it before Fedora 28 is end of life. If you would still like 
to see this bug fixed and are able to reproduce it against a later version 
of Fedora, you are encouraged  change the 'version' to a later Fedora 
version prior this bug is closed as described in the policy above.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events. Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.

Fedora 28 changed to end-of-life (EOL) status on 2019-05-28. Fedora 28 is
no longer maintained, which means that it will not receive any further
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen this bug against that version. If you
are unable to reopen this bug, please file a new report against the
current release. If you experience problems, please add a comment to this
bug.

Thank you for reporting this bug and we are sorry it could not be fixed.