I tried upgrading from xfs-sources-2.4.20_pre6 to xfs-sources-2.4.20 and had a slew of problems when booting. It looks like these problems are related to mounting filesystems. Even though /var was mounted a `ls /var` showed no files. `umount /var` and then `mount /var` made those files visiable. I don't know if it was related but the only thing I changed in `make menuconfig` was enabling PREEEMPT. Reproducible: Always Steps to Reproduce: boot into xfs-sources-2.4.20 Actual Results: the contents of filesystems appear to be missing until you unmount/mount them. Expected Results: all my filesytems to be there Portage 2.0.47-r10 (default-1.0, gcc-2.95.3, glibc-2.2.5-r4,2.2.5-r7) ================================================================= System uname: 2.4.20-xfs_pre6 i686 Intel(R) Pentium(R) 4 CPU 1.80GHz GENTOO_MIRRORS="http://gentoo.oregonstate.edu/ http://distro.ibiblio.org/pub/Linux/distributions/gentoo" CONFIG_PROTECT="/etc /var/qmail/control /usr/kde/2/share/config /usr/kde/3/share/config /usr/X11R6/lib/X11/xkb /opt/jakarta/tomcat/conf /usr/kde/3.1/share/config /usr/share/config" CONFIG_PROTECT_MASK="/etc/gconf /etc/env.d" PORTDIR="/usr/portage" DISTDIR="/usr/portage/distfiles" PKGDIR="/usr/portage/packages" PORTAGE_TMPDIR="/var/tmp" PORTDIR_OVERLAY="/usr/local/portage" USE="x86 oss apm avi crypt encode jpeg libg++ mikmod mmx mpeg ncurses pdflib spell truetype xml2 xmms xv arts berkdb cdr gdbm gif gnome-libs gpm gtk guile imlib java kde libwww motif nls oggvorbis opengl pam perl png postgres python qt readline scanner sdl slang ssl svga tcpd tetex X -esd -3dnow ipv6 tcltk tiff cups mozilla alsa -ldap quicktime" COMPILER="" CHOST="i686-pc-linux-gnu" CFLAGS="-march=i686 -O3 -pipe" CXXFLAGS="-march=i686 -O3 -pipe" ACCEPT_KEYWORDS="x86" MAKEOPTS="-j2" AUTOCLEAN="yes" SYNC="rsync://rsync2.us.gentoo.org/gentoo-portage" FEATURES="sandbox ccache"
im having trouble reproducing this, and the xfs devs havent heard of it. ill try some different boxes in the morning, and im also adding a ebuild for newer xfs snapshot (will be marked ~x86)
I'll try to figure this out more after Wednesday. It may be an error on my part. The computer I had a problem with is my workstation at work and I have an important deadline before then.
well, this cannot be reproduced. please feel free to reopen and post more info if you have it later on. Until then, without more info, we cannot fix this issue. Jay
db fix