Summary: | baselayout(?): Doesn't unmount md raid root partition on reboot/halt | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Prakash Punnoor <prakashp> |
Component: | [OLD] baselayout | Assignee: | Gentoo's Team for Core System packages <base-system> |
Status: | RESOLVED WORKSFORME | ||
Severity: | normal | ||
Priority: | High | ||
Version: | unspecified | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- |
Description
Prakash Punnoor
2004-12-05 07:41:55 UTC
you neglected to provide `emerge info` like the bug report page says to Sorry, here you go Portage 2.0.51-r8 (gcc34-x86-2004.2, gcc-3.4.3, glibc-2.3.4.20041102-r0, 2.6.10-rc3-ck1 i686) ================================================================= System uname: 2.6.10-rc3-ck1 i686 AMD Athlon(tm) Gentoo Base System version 1.6.7 Python: dev-lang/python-2.3.4 [2.3.4 (#1, Nov 29 2004, 12:17:47)] distcc 2.18.2 i686-pc-linux-gnu (protocols 1 and 2) (default port 3632) [disabled] dev-lang/python: 2.3.4 sys-devel/autoconf: 2.13, 2.59-r6 sys-devel/automake: 1.8.5-r2, 1.9.3, 1.5, 1.6.3, 1.7.9, 1.4_p6 sys-devel/binutils: 2.15.92.0.2-r1 sys-devel/libtool: 1.5.2-r7 virtual/os-headers: 2.6.8.1-r1 ACCEPT_KEYWORDS="x86 ~x86" AUTOCLEAN="yes" CFLAGS="-march=athlon-xp -mtune=athlon-xp -O2 -pipe -frename-registers -fomit-frame-pointer -fprefetch-loop-arrays" CHOST="i686-pc-linux-gnu" CONFIG_PROTECT="/etc /usr/X11R6/lib/X11/xkb /usr/kde/2/share/config /usr/kde/3/share/config /usr/share/config/usr/share/texmf/dvipdfm/config/ /usr/share/texmf/dvips/config/ /usr/share/texmf/tex/generic/config/ /usr/share/texmf/tex/platex/config/ /usr/share/texmf/xdvi/ /var/qmail/control" CONFIG_PROTECT_MASK="/etc/gconf /etc/terminfo /etc/env.d" CXXFLAGS="-march=athlon-xp -mtune=athlon-xp -O2 -pipe -frename-registers -fomit-frame-pointer -fprefetch-loop-arrays -fvisibility-inlines-hidden" DISTDIR="/usr/portage/distfiles" FEATURES="autoaddcvs candy ccache digest distlocks prelink sandbox" GENTOO_MIRRORS=" ftp://ftp.tu-clausthal.de/pub/linux/gentoo/ ftp://linux.rz.ruhr-uni-bochum.de/gentoo-mirror/http://www.ibiblio.org/pub/Linux/distributions/gentoo" MAKEOPTS="-j2" PKGDIR="/usr/portage/packages" PORTAGE_TMPDIR="/var/tmp" PORTDIR="/usr/portage" PORTDIR_OVERLAY="/usr/local/bmg-main /usr/lportage" SYNC="rsync://linux.rz.ruhr-uni-bochum.de/gentoo-portage/" USE="3dnow 3dnowex S3TC X Xaw3d aac acpi acpi4linux alsa apm audiofile avi berkdb bitmap-fonts cddb cdparanoia cdr crypt cups curl dga divx4linux dts dv dvb dvd dvdr dvdread edl encode ext-png ext-zlib faac faad ffmpeg fftw flac foomaticdb freetype gdbm gif gimp gimpprint gnome gphoto2 gpm gs gstreamer gtk gtk2 gtkhtml hal ieee1394 imlib ithreads java javascript jpeg jpeg2k kde ldap libg++ libwww live lm_sensors lzo mad matroska mikmodmmx mmx2 monkey motif moznocompose mpeg mpi nas ncurses network nls no_wxgtk1 nocd nptl nvidia oggvorbis openal opengl openssh oss pam pdflib perl pic png povray ppds python qt qtmt quicktime readline real rtc samba scanner sdl slang smime speex spell sqlite sse ssl tcpd tetex theora threads tiff transcode truetype usb videos wmf wxwindows x86 xfs xine xinetd xml xml2 xmms xprint xv xvid xvmc yv12 zlib linguas_de" did this work in earlier versions ? As I already said, I haven't had a RAID array earlier, so I don't know whether it is a regression (ie if an earlier version worked). try this ... emerge -f =baselayout-1.11.6-r1 tar -jxf /usr/portage/distfiles/rc-scripts-1.6.6.tar.bz2 rc-scripts-1.6.6/init.d/halt.sh mv rc-scripts-1.6.6/init.d/halt.sh /etc/init.d/halt.sh reboot if you experience the same problem, then this is not a regression ;) No it doesn't help, but I found something interesting: In local.start I change the default level of kernel logging via echo 6 4 1 7 > /proc/sys/kernel/printk Only with this commandI actually get this warning about my raid partition printed. Nevertheless, I never got troubles before putting my root on raid... could you try baselayout-1.11.9-r1 ? we added a few extra retries in the final unmount/remount readonly code path ... I haven't noticed any issues lately, so I guess you can close it for now. ok, well please re-open if it starts acting up again :) |