Bug 119939 – broken filesystem after upgrading to sys-apps/baselayout-1.11.14-r2 and reboot

• Product: Gentoo Linux
• Status: RESOLVED CANTFIX

[Description Wernfried Haas (RETIRED) 2006-01-22 08:43:53 UTC]

Sorry for this rather inaccurate bug report as i don't exactly know what to report. After upgrading my stable x86 system (which included kernel gentoo-sources from 2.6.13 to 2.6.15-r1 (which i also compiled and set in my bootloader), udev from sys-fs/udev-070-r1 to sys-fs/udev-079-r1 and baselayout from sys-apps/baselayout-1.11.13-r1 to sys-apps/baselayout-1.11.14-r2 and doing dispatch-conf my system went into FS recovery mode for /dev/hda6 (which is /home). It turned out my mozilla profile was broken, rsync (to compare with my backup (no data lost)) reported an I/O error.
After booting a live system and fscking both / (which had 2 errors) and /home (which had loads of errors) and restoring my box nothing is lost, but the upgrade seemed rather bumpy to me. Any ideas how to prevent that stuff from happening? I'll also try to provide any other useful information if you can tell me what you need to know or reproduce this. 
I also ran badblocks (in ro mode) against the disk to ensure no disk error caused this, it was fine. smartctl -a /dev/hda showed no errors on that drive, too.
Btw, if the upgrade went fine for everyone else this bug may be closed with ALLMYFAULT. ;-)
Just another thought, should i have done "udevstart" before rebooting?

emerge info:
Portage 2.1_pre3-r1 (default-linux/x86/2005.0, gcc-3.4.4, glibc-2.3.5-r2, 2.6.15
=================================================================
System uname: 2.6.15-gentoo-r1 i686 Intel(R) Pentium(R) M processor 2.00GHz
Gentoo Base System version 1.6.14
dev-lang/python:     2.4.2
sys-apps/sandbox:    1.2.12
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.6-r1
sys-devel/binutils:  2.16.1
sys-devel/libtool:   1.5.22
virtual/os-headers:  2.6.11-r2
ACCEPT_KEYWORDS="x86"
AUTOCLEAN="yes"
CBUILD="i686-pc-linux-gnu"
CFLAGS="-march=pentium-m -O3 -pipe -fomit-frame-pointer"
CHOST="i686-pc-linux-gnu"
CONFIG_PROTECT="/etc /usr/kde/2/share/config /usr/kde/3.4/env /usr/kde/3.4/share
onfig /usr/lib/X11/xkb /usr/lib/mozilla/defaults/pref /usr/share/config /var/qma
CONFIG_PROTECT_MASK="/etc/gconf /etc/terminfo /etc/env.d"
CXXFLAGS="-march=pentium-m -O3 -pipe -fomit-frame-pointer"
DISTDIR="/usr/portage/distfiles"
FEATURES="autoconfig distlocks sandbox sfperms strict userpriv usersandbox"
GENTOO_MIRRORS="http://distfiles.gentoo.org http://distro.ibiblio.org/pub/linux/
MAKEOPTS="-j2"
PKGDIR="/usr/portage/packages"
PORTAGE_TMPDIR="/var/tmp"
PORTDIR="/usr/portage"
PORTDIR_OVERLAY="/usr/local/portage"
SYNC="rsync://192.168.0.75/gentoo-portage"
USE="x86 X aalib alsa apm atm audiofile avi berkdb bitmap-fonts bzip2 cdparanoia
mboss encode esd ethereal exif expat fam fbcon ffmpeg flac foomaticdb fortran gd
magick imap imlib ipv6 java jpeg kde lcms libg++ libwww mad mikmod mmx mng mozil
rbis opengl oss pam pcre pdflib perl png ppds python qt quicktime readline real 
d tiff truetype truetype-fonts type1-fonts udev vorbis win32codecs xinetd xml2 x
U"
Unset:  ASFLAGS, CTARGET, LANG, LC_ALL, LDFLAGS, LINGUAS

[Comment 1 Jakub Moc (RETIRED) 2006-01-22 08:49:51 UTC]

Well, I don't think that udev causes filesystem corruption. :-) Can you post your /etc/fstab?

[Comment 2 Wernfried Haas (RETIRED) 2006-01-22 08:55:20 UTC]

I don't think so either, my guess is that something went wrong on unmounting /home when shutting down the box to boot the new kernel/udev.
Here's my fstab:
# <fs>                  <mountpoint>    <type>          <opts>                  <dump/pass>

# NOTE: If your BOOT partition is ReiserFS, add the notail option to opts.
/dev/hda1               /boot           ext2            noauto,noatime         0 2
/dev/hda2               /               ext3            defaults               0 1
/dev/hda5               none            swap            sw                     0 0
/dev/hdc                /mnt/cdrom      iso9660         noauto,ro,user         0 0
/dev/hda6               /home           ext3            defaults               0 2

none                    /proc           proc            defaults               0 0

none                    /dev/shm        tmpfs           defaults               0 0

[Comment 3 Jakub Moc (RETIRED) 2006-01-22 09:11:19 UTC]

Well, uhm - WORKSFORME? :) Passing to baselayout guys, dunno if there were any changes wrt unmounting on reboot.

[Comment 4 SpanKY 2006-01-22 12:17:54 UTC]

there isnt anything we can really do about it