This service will be undergoing maintenance at 00:00 UTC, 2017-10-23 It is expected to last about 30 minutes
Bug 118815 - [PATCH] extranious error with mdadm
[PATCH] extranious error with mdadm
Product: Red Hat Enterprise Linux 3
Classification: Red Hat
Component: mdadm (Show other bugs)
All Linux
medium Severity medium
: ---
: ---
Assigned To: Doug Ledford
Depends On:
  Show dependency treegraph
Reported: 2004-03-20 19:57 EST by Christopher McCrory
Modified: 2007-11-30 17:07 EST (History)
1 user (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2007-06-07 12:22:12 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)
error patch (318 bytes, patch)
2004-03-20 19:58 EST, Christopher McCrory
no flags Details | Diff

  None (edit)
Description Christopher McCrory 2004-03-20 19:57:38 EST
Description of problem:
extranious error with mdadm

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

How reproducible:

Steps to Reproduce:
1. startup mdadm 
Actual results:
[chrismcc@djali /]$ sudo /sbin/service mdmonitor start
Starting mdmonitor: mdadm: bad /proc/mdstat line starts: Event:
mdadm: bad /proc/mdstat line starts: Event:
[chrismcc@djali /]$                                        [  OK  ]

Expected results:

no error

Additional info:

Patch attached ! :)
Comment 1 Christopher McCrory 2004-03-20 19:58:18 EST
Created attachment 98721 [details]
error patch
Comment 2 Christopher McCrory 2004-03-22 15:27:54 EST
I also sent a note to the program author,  this has already been taken
care of in v1.5.0

in the init script, stderr is not closed
mdadm --monitor --scan &
mdadm --monitor --scan --daemonize

solves that.

Comment 3 Doug Ledford 2004-03-30 16:00:35 EST
An updated version of the package that uses the upstream 1.5.0 mdadm
code has been built into our system and should make the next update.

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