Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!
Bug 267823 - sys-fs/mdadm: /etc/init.d/mdraid shuts down in wrong order
Summary: sys-fs/mdadm: /etc/init.d/mdraid shuts down in wrong order
Status: RESOLVED INVALID
Alias: None
Product: Gentoo Linux
Classification: Unclassified
Component: [OLD] Core system (show other bugs)
Hardware: All Linux
: High normal (vote)
Assignee: Gentoo's Team for Core System packages
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2009-04-29 03:02 UTC by Timothy Miller
Modified: 2009-06-26 04:33 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 Timothy Miller 2009-04-29 03:02:44 UTC
The mdraid daemon shuts down (unsuccessfully) before a whole bunch of other things during shutdown.  Shouldn't it be the last thing that is terminated?  I'm concerned that if it's killed without being shut down properly, corruption might occur.  (Although I'm not entirely sure what the daemon does.)

BTW, it doesn't matter if mdraid is in sysinit or boot runlevels.

Reproducible: Always




$ emerge --info
Portage 2.1.6.11 (default/linux/amd64/2008.0, gcc-4.3.3, glibc-2.9_p20081201-r2, 2.6.29-gentoo-r1 x86_64)
=================================================================
System uname: Linux-2.6.29-gentoo-r1-x86_64-Intel-R-_Core-TM-2_Quad_CPU_Q9450_@_2.66GHz-with-gentoo-2.0.0
Timestamp of tree: Wed, 29 Apr 2009 00:00:01 +0000
app-shells/bash:     4.0_p17-r1
dev-java/java-config: 2.1.7
dev-lang/python:     2.6.2
dev-util/cmake:      2.6.3-r1
sys-apps/baselayout: 2.0.0
sys-apps/openrc:     0.4.3-r2
sys-apps/sandbox:    1.9
sys-devel/autoconf:  2.13, 2.63-r1
sys-devel/automake:  1.5, 1.7.9-r1, 1.8.5-r3, 1.9.6-r2, 1.10.2
sys-devel/binutils:  2.19.1-r1
sys-devel/gcc-config: 1.4.1
sys-devel/libtool:   2.2.6a
virtual/os-headers:  2.6.28-r1
ACCEPT_KEYWORDS="amd64 ~amd64"
CBUILD="x86_64-pc-linux-gnu"
CFLAGS="-O2 -march=core2 -pipe"
CHOST="x86_64-pc-linux-gnu"
CONFIG_PROTECT="/etc /usr/kde/3.5/env /usr/kde/3.5/share/config /usr/kde/3.5/shutdown /usr/share/config"
CONFIG_PROTECT_MASK="/etc/ca-certificates.conf /etc/env.d /etc/env.d/java/ /etc/fonts/fonts.conf /etc/gconf /etc/gentoo-release /etc/php/apache2-php5/ext-active/ /etc/php/cgi-php5/ext-active/ /etc/php/cli-php5/ext-active/ /etc/revdep-rebuild /etc/sandbox.d /etc/terminfo /etc/udev/rules.d"
CXXFLAGS="-O2 -march=core2 -pipe"
DISTDIR="/usr/portage/distfiles"
FEATURES="distlocks fixpackages parallel-fetch protect-owned sandbox sfperms strict unmerge-orphans userfetch"
GENTOO_MIRRORS="ftp://mirror.datapipe.net/gentoo ftp://mirror.csclub.uwaterloo.ca/gentoo-distfiles/ http://gentoo.mirrors.easynews.com/linux/gentoo/ ftp://ftp.free.fr/mirrors/ftp.gentoo.org/ ftp://gentoo.imj.fr/pub/gentoo/ ftp://distro.ibiblio.org/pub/linux/distributions/gentoo/"
LANG="en_US.utf8"
LDFLAGS="-Wl,-O1"
MAKEOPTS="-j5"
PKGDIR="/usr/portage/packages"
PORTAGE_CONFIGROOT="/"
PORTAGE_RSYNC_OPTS="--recursive --links --safe-links --perms --times --compress --force --whole-file --delete --stats --timeout=180 --exclude=/distfiles --exclude=/local --exclude=/packages"
PORTAGE_TMPDIR="/var/tmp"
PORTDIR="/usr/portage"
PORTDIR_OVERLAY="/usr/local/portage"
SYNC="rsync://rsync.gentoo.org/gentoo-portage"
USE="X acl amd64 berkdb bzip2 cdr cli cracklib crypt cups dbus dri dvd fbcon fortran gcj gdbm gpm hal iconv ipv6 isdnlog jadetex java jpeg kde kde4 lm_sensors midi mmx mng mp3 mudflap multilib mysql ncurses nls nptl nptlonly opengl openmp pam pcre perl php png pppd python qt4 readline reflection ruby samba session spl sse sse2 sse3 ssl symlink sysfs tcpd tiff truetype unicode vcd webkit xorg zlib" ALSA_CARDS="ali5451 als4000 atiixp atiixp-modem bt87x ca0106 cmipci emu10k1x ens1370 ens1371 es1938 es1968 fm801 hda-intel intel8x0 intel8x0m maestro3 trident usb-audio via82xx via82xx-modem ymfpci" ALSA_PCM_PLUGINS="adpcm alaw asym copy dmix dshare dsnoop empty extplug file hooks iec958 ioplug ladspa lfloat linear meter mmap_emul mulaw multi null plug rate route share shm softvol" APACHE2_MODULES="actions alias auth_basic authn_alias authn_anon authn_dbm authn_default authn_file authz_dbm authz_default authz_groupfile authz_host authz_owner authz_user autoindex cache dav dav_fs dav_lock deflate dir disk_cache env expires ext_filter file_cache filter headers include info log_config logio mem_cache mime mime_magic negotiation rewrite setenvif speling status unique_id userdir usertrack vhost_alias" ELIBC="glibc" INPUT_DEVICES="keyboard mouse" KERNEL="linux" LCD_DEVICES="bayrad cfontz cfontz633 glk hd44780 lb216 lcdm001 mtxorb ncurses text" USERLAND="GNU" VIDEO_CARDS="fglrx"
Unset:  CPPFLAGS, CTARGET, EMERGE_DEFAULT_OPTS, FFLAGS, INSTALL_MASK, LC_ALL, LINGUAS, PORTAGE_COMPRESS, PORTAGE_COMPRESS_FLAGS, PORTAGE_RSYNC_EXTRA_OPTS
Comment 1 SpanKY gentoo-dev 2009-06-26 00:25:29 UTC
the daemon is purely for monitoring.  having it shutdown last really doesnt matter as if it detects anything wrong in those last <10 seconds, it's not like it can do anything about it.
Comment 2 Timothy Miller 2009-06-26 03:25:49 UTC
In that case, the bug is that the shutdown messages regarding mdadm are in red, making it appear as if some error has occurred.  You're telling me that there's no error.  Good.  Then there should be no error MESSAGE either.
Comment 3 SpanKY gentoo-dev 2009-06-26 04:12:48 UTC
i didnt say that.  you said it shutdown in the wrong order and i said the order is irrelevant.  as to why you got [!!], there is not enough information in this report to figure that out.  starting and stopping mdadm works fine for me.  please refrain from putting words into others' mouths.
Comment 4 Timothy Miller 2009-06-26 04:30:53 UTC
I apologize if I came across as rude.  What I meant was to suggest that, based on your comment, I had been mistaken as to the nature of the bug and was suggesting that there may still be a bug, just different from the one I had thought.

The error I get refers to the fact that the partition for which mdadm (the root partition) is busy at the time the mdadm daemon is shut down.  Is your setup similar to mine (root on RAID)?  Or something different?
Comment 5 SpanKY gentoo-dev 2009-06-26 04:33:28 UTC
there are two (mostly unrelated) aspects of mdadm.  the first is the init.d script which you refer to in the summary.  that order is irrelevant.  if you're saying you get [!!] when shutting down the array, that is not the init.d script but rather the mdadm raid hook.  and i believe that is Bug 119380.