I wish there were guidelines for filling out this bug report... Anyway, I'm using LVM on top of a software RAID array (OK, 2 software RAID arrays), since it's nice to be able to rearrange the space on this large collection of disks. Unfortunately, the checkfs script starts the LVM stuff before the raid stuff, so LVM volumes on RAID devices won't work at boot time. This could potentially be a pretty major problem if something like, say, /usr was in that LVM set. The fix is to move the LVM initialization section to below the RAID initialization section in checkfs, but before the fsck section. I'd submit a patch, but a description consumes less bandwidth.
there are guidelines for filling out bug reports and you neglected the biggest one ... re-open when you've posted `emerge info
Re: guidelines - see Bug 57282. I looked for them... :) Anyway: Portage 2.0.51-r3 (default-ppc-2004.1, gcc-3.4.1, glibc-2.3.3.20040420-r2, 2.6.9 -gentoo-r1 ppc) ================================================================= System uname: 2.6.9-gentoo-r1 ppc 7400, altivec supported Gentoo Base System version 1.4.16 distcc 2.17 powerpc-unknown-linux-gnu (protocols 1 and 2) (default port 3632) [d isabled] Autoconf: sys-devel/autoconf-2.59-r5 Automake: sys-devel/automake-1.8.5-r1 Binutils: sys-devel/binutils-2.15.90.0.3-r3 Headers: sys-kernel/linux26-headers-2.6.8.1 Libtools: sys-devel/libtool-1.5.2-r7 ACCEPT_KEYWORDS="ppc" AUTOCLEAN="yes" CFLAGS="-O2 -mcpu=7400 -maltivec -mabi=altivec -pipe" CHOST="powerpc-unknown-linux-gnu" COMPILER="" CONFIG_PROTECT="/etc /usr/X11R6/lib/X11/xkb /usr/kde/2/share/config /usr/kde/3.3 /env /usr/kde/3.3/share/config /usr/kde/3.3/shutdown /usr/kde/3/share/config /us r/share/config /var/bind /var/qmail/control" CONFIG_PROTECT_MASK="/etc/gconf /etc/terminfo /etc/env.d" CXXFLAGS="-O2 -mcpu=7400 -maltivec -mabi=altivec -pipe" DISTDIR="/usr/portage/distfiles" FEATURES="autoaddcvs ccache distlocks" GENTOO_MIRRORS="http://ftp-mirror.internap.com/pub/gentoo/ http://gentoo.mirrors .pair.com http://gentoo.mirror.sdv.fr http://gentoo.binarycompass.org ftp://mirr or.nutsmaas.nl/gentoo/ http://distro.ibiblio.org/pub/Linux/distributions/gentoo/ " MAKEOPTS="-j2" PKGDIR="/usr/portage/packages" PORTAGE_TMPDIR="/var/tmp" PORTDIR="/usr/portage" PORTDIR_OVERLAY="" SYNC="rsync://rsync.gentoo.org/gentoo-portage" USE="X altivec berkdb cdr crypt cups dvd dvdr esd f77 fortran gcj gdbm gif gnome gnome-libs gpm gtk imlib jbig jikes jpeg kde lcms ldap mad maildir mpeg mysql n as ncurses nls oggvorbis opengl pam perl pic png ppc python qt readline sasl sla ng snmp ssl tcltk tcpd tiff truetype wmf xinerama xml2 yahoo zlib"
This might also be relevent, actually: gutenberg root # equery belongs /etc/init.d/checkfs Searching for file '/etc/init.d/checkfs' in *... sys-apps/baselayout-1.9.4-r6 (/etc/init.d/checkfs)
upgrade to baselayout-1.11.7-r2 and make sure the problem still exists there
I'm running a backup now, and will report back. Meanwhile, is there any particular reason for me to be nervous about a baselayout and sysvinit that's marked unstable on my platform? :)
i dont think so ... expect to update a few config files though we're planning on moving a version into stable so it's going to happen to you soon anyways :)
Well, I was gonna see if it'd restart cleanly after upgrading to the new baselayout, but it appears that the upgrade removed my /sbin/shutdown and /sbin/reboot. That, I'd think, is a bit of a problem (and perhaps a new bug). I checked the backup, and those files were there before the upgrade (to baselayout-1.11.7-r2). So, I updated to baselayout 1.11.8. Same deal. Where in the heck did shutdown and restart go? I'll happily verify this as fixed (or reopen), just as soon as I figure out how to restart the machine. :)
