Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!
Bug 99611 - mdadm fails to stop /dev/mdX with root partition at shutdown
Summary: mdadm fails to stop /dev/mdX with root partition at shutdown
Status: RESOLVED WONTFIX
Alias: None
Product: Gentoo Linux
Classification: Unclassified
Component: [OLD] baselayout (show other bugs)
Hardware: x86 Linux
: High normal (vote)
Assignee: Gentoo's Team for Core System packages
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2005-07-19 19:34 UTC by pinihadad
Modified: 2009-09-07 11:24 UTC (History)
0 users

See Also:
Package list:
Runtime testing required: ---


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description pinihadad 2005-07-19 19:34:05 UTC
At shutdown get something like:
mdadm: failed to stop /dev/md0 array, device or resource busy [!!]
That device has / on it. I'm not sure when this started happening exactly, but
it wasn't too long ago (within the last month or so?). I didn't change any
configuration having to do with that as far as I know, but I have upgraded all
sorts of important packages. Someone else seems to be reporting the same problem
in
http://forums.gentoo.org/viewtopic-t-360870.html?sid=6ba08c72116ec3dfd64d6f24dfb56b05
.

Reproducible: Always
Steps to Reproduce:
1.
2.
3.



Portage 2.0.51.22-r2 (default-linux/x86/2005.0, gcc-3.3.5-20050130,
glibc-2.3.5-r0, 2.6.12-ck3 i686)
=================================================================
System uname: 2.6.12-ck3 i686 AMD Athlon(tm) XP 3000+
Gentoo Base System version 1.6.13
dev-lang/python:     2.3.5
sys-apps/sandbox:    1.2.10
sys-devel/autoconf:  2.13, 2.59-r6
sys-devel/automake:  1.4_p6, 1.5, 1.6.3, 1.7.9-r1, 1.8.5-r3, 1.9.5
sys-devel/binutils:  2.15.92.0.2-r10
sys-devel/libtool:   1.5.18-r1
virtual/os-headers:  2.6.11-r2
ACCEPT_KEYWORDS="x86"
AUTOCLEAN="yes"
CBUILD="i686-pc-linux-gnu"
CFLAGS="-O3 -march=athlon-xp -pipe"
CHOST="i686-pc-linux-gnu"
CONFIG_PROTECT="/etc /usr/kde/2/share/config /usr/kde/3.3/env
/usr/kde/3.3/share/config /usr/kde/3.3/shutdown /usr/kde/3.4/env
/usr/kde/3.4/share/config /usr/kde/3.4/shutdown /usr/kde/3/share/config
/usr/lib/X11/xkb /usr/share/config /var/qmail/control"
CONFIG_PROTECT_MASK="/etc/gconf /etc/terminfo /etc/env.d"
CXXFLAGS="-O3 -march=athlon-xp -pipe"
DISTDIR="/usr/portage/distfiles"
FEATURES="autoconfig distlocks maketest sandbox sfperms strict test"
GENTOO_MIRRORS="http://mirror.datapipe.net/gentoo"
MAKEOPTS="-j2"
PKGDIR="/usr/portage/packages"
PORTAGE_TMPDIR="/var/tmp"
PORTDIR="/usr/portage"
PORTDIR_OVERLAY="/usr/local/portage"
SYNC="rsync://rsync.us.gentoo.org/gentoo-portage"
USE="x86 3dnow X aac aalib acl acpi alsa apache2 apm arts avi bash-completion
berkdb bitmap-fonts bzip2 cdparanoia cdr crypt cups curl dga directfb divx4linux
dvd dvdr dvdread emboss encode fam fbcon ffmpeg flac foomaticdb gd gif glut gpg
gpm gstreamer gtk2 i8x0 imagemagick imlib jabber jpeg junit kde libwww
lm_sensors mad mbox mime mmx mozsvg mp3 mpeg mplayer mysql ncurses nptl nptlonly
offensive ogg oggvorbis opengl pam pda pdflib php png postgres ppds python qt
quicktime rdesktop readline real samba scanner sdl sftplogging skey slang snmp
spell sse ssl stream subversion svg svga sysfs tcltk tcpd tga theora tiff
truetype truetype-fonts type1-fonts unicode usb v4l v4l2 videos vorbis xine
xinerama xml xml2 xmms xosd xv xvid zlib userland_GNU kernel_linux elibc_glibc"
Unset:  ASFLAGS, CTARGET, LANG, LC_ALL, LDFLAGS, LINGUAS
Comment 1 SpanKY gentoo-dev 2005-07-20 18:39:50 UTC
it's a non-fatal error and can be ignored ... if you have a clean solution, i'll
look at it, otherwise current situation is Good Enough For Me ;)
Comment 2 pinihadad 2005-07-20 19:24:51 UTC
(In reply to comment #1)
> it's a non-fatal error and can be ignored ... if you have a clean solution, i'll
> look at it, otherwise current situation is Good Enough For Me ;)

I don't have a clean solution. I understand that it's non-fatal and shouldn't be
a high priority, but it was broken recently and I don't understand why it
shouldn't evetually be fixed- and left as a bug till then. Could you please
explain? Thanks for your time regardless.
Comment 3 SpanKY gentoo-dev 2005-07-20 19:43:26 UTC
it's always done that

the difference is that the older version used to pipe the errors to /dev/null
and ignore the result
Comment 4 pinihadad 2005-07-20 19:59:28 UTC
(In reply to comment #3)
> it's always done that
> 
> the difference is that the older version used to pipe the errors to /dev/null
> and ignore the result

Ah. Thanks for the info.
Comment 5 Martin Bailey 2008-06-07 07:40:54 UTC
(In reply to comment #3)
> it's always done that
> 
> the difference is that the older version used to pipe the errors to /dev/null
> and ignore the result

Since this always prints *Failed* every time a RAID machine reboots, could the next version be changed to pipe it to /dev/null again?
Comment 6 macindy 2009-09-07 11:24:52 UTC
Any update on this? Error msg. are error msg. Please dev/null it, if not interesting.