Bug 1653770 - ANOM_ABEND reported 15000 times in last 10 days
Summary: ANOM_ABEND reported 15000 times in last 10 days
Alias: None
Product: Fedora
Classification: Fedora
Component: mdadm
Version: 29
Hardware: x86_64
OS: Linux
Target Milestone: ---
Assignee: Jes Sorensen
QA Contact: Fedora Extras Quality Assurance
Depends On:
TreeView+ depends on / blocked
Reported: 2018-11-27 15:36 UTC by Paul DeStefano
Modified: 2019-11-27 18:16 UTC (History)
5 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Last Closed: 2019-11-27 18:16:48 UTC
Type: Bug

Attachments (Terms of Use)

Description Paul DeStefano 2018-11-27 15:36:42 UTC
Description of problem:

Nov 27 07:28:12 <hostname> audit[812530]: ANOM_ABEND auid=4294967295 uid=0 gid=0 ses=4294967295 subj=system_u:system_r:pcp_pmcd_t:s0 pid=812530 comm="mdadm" exe="/usr/sbin/mdadm" sig=11 res=1

Version-Release number of selected component (if applicable):

How reproducible:
Occurs frequently without effort.

Comment 1 Jason Farrell 2019-01-29 16:00:33 UTC
Seeing this as well. System runs fine, but the log is being spammed with seemingly harmless mdadm crashes.

FWIW: I have a LVM PV over a partitioned 2-disk raid1 mirror (using intel isw fakeraid).

# cat /proc/mdstat ; file -s /dev/md126*
Personalities : [raid1] 
md126 : active raid1 sdc[1] sdb[0]
      1953511424 blocks super external:/md127/0 [2/2] [UU]
md127 : inactive sdc[1](S) sdb[0](S)
      6320 blocks super external:imsm
unused devices: <none>
/dev/md126:   DOS/MBR boot sector; partition 1 : ID=0x7, start-CHS (0x0,32,33), end-CHS (0x3ff,254,63), startsector 2048, 976750592 sectors; partition 2 : ID=0x83, start-CHS (0x3ff,254,63), end-CHS (0x3ff,254,63), startsector 976754688, 2930268160 sectors
/dev/md126p1: DOS/MBR boot sector, code offset 0x52+2, OEM-ID "NTFS    ", sectors/cluster 8, Media descriptor 0xf8, sectors/track 63, heads 255, hidden sectors 2048, dos < 4.0 BootSector (0x80), FAT (1Y bit by descriptor); NTFS, sectors/track 63, sectors 976750591, $MFT start cluster 786432, $MFTMirror start cluster 2, bytes/RecordSegment 2^(-1*246), clusters/index block 1, serial number 06c6a56246a55eafa; containsMicrosoft Windows XP/VISTA bootloader BOOTMGR
/dev/md126p2: LVM2 PV (Linux Logical Volume Manager), UUID: naBF70-attg-r7Tt-miNB-YSVu-krR0-BUlAuX, size: 1500297297920

Comment 2 Ben Cotton 2019-10-31 20:05:01 UTC
This message is a reminder that Fedora 29 is nearing its end of life.
Fedora will stop maintaining and issuing updates for Fedora 29 on 2019-11-26.
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 '29'.

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 29 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.

Comment 3 Paul DeStefano 2019-11-01 04:59:41 UTC
Hey, I don't think I'm getting these anymore.  Jason, how about you?

Comment 4 Ben Cotton 2019-11-27 18:16:48 UTC
Fedora 29 changed to end-of-life (EOL) status on 2019-11-26. Fedora 29 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

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

Note You need to log in before you can comment on or make changes to this bug.