Bug 145486

Summary:	Mounting raid devices generates cosmetic error
Product:	Red Hat Enterprise Linux 2.1	Reporter:	Matthew Galgoci <mgalgoci>
Component:	mount	Assignee:	Karel Zak <kzak>
Status:	CLOSED WONTFIX	QA Contact:	Brian Brock <bbrock>
Severity:	medium	Docs Contact:
Priority:	medium
Version:	2.1	CC:	aander07
Target Milestone:	---
Target Release:	---
Hardware:	All
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2007-10-19 19:21:00 UTC	Type:	---
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Matthew Galgoci 2005-01-18 21:54:38 UTC

Aparently with the e.57 kernel, the kernel does not like the ioctls
that mount is using to mount software raid devices. I get the
following in my kernel log:

md: mount(pid 212) used obsolete MD ioctl, upgrade your software to
use new ictls.
md: mount(pid 212) used obsolete MD ioctl, upgrade your software to
use new ictls.
md: mount(pid 212) used obsolete MD ioctl, upgrade your software to
use new ictls.
md: mount(pid 212) used obsolete MD ioctl, upgrade your software to
use new ictls.
md: mount(pid 212) used obsolete MD ioctl, upgrade your software to
use new ictls.


It's purely cosmetic, but it could do with fixing. If this is the only
issue with this kernel I will still be happy :)

Comment 1 Need Real Name 2005-04-12 02:17:15 UTC

This error message is still present in the e.59 kernels.  Either mount needs to
be errata'ed, or the kernel needs to be silenced, but please fix this, as it is
filling system logs with useless messages.

Comment 3 RHEL Program Management 2007-10-19 19:21:00 UTC

This bug is filed against RHEL2.1, which is in maintenance phase.
During the maintenance phase, only security errata and select mission
critical bug fixes will be released for enterprise products.  Since
this bug does not meet that criteria, it is now being closed.

For more information of the RHEL errata support policy, please visit:
http://www.redhat.com/security/updates/errata/

If you feel this bug is indeed mission critical, please contact your
support representative.  You may be asked to provide detailed
information on how this bug is affecting you.