Bug 138129 – ivman/hal refuse to detect partition changes

• Product: Gentoo Linux
• Status: RESOLVED INVALID

[Description Daniel Frey 2006-06-26 18:20:03 UTC]

[emerge --info]
Portage 2.1_rc4 (default-linux/x86/2006.0, gcc-3.3.6, glibc-2.3.6-r3, 2.6.16-gentoo-r7 i686)
=================================================================
System uname: 2.6.16-gentoo-r7 i686 AMD Athlon(tm) XP 3200+
Gentoo Base System version 1.6.14
distcc 2.18.3 i686-pc-linux-gnu (protocols 1 and 2) (default port 3632) [enabled]
dev-lang/python:     2.3.5-r2, 2.4.2
dev-python/pycrypto: 2.0.1-r5
dev-util/ccache:     [Not Present]
dev-util/confcache:  [Not Present]
sys-apps/sandbox:    1.2.17
sys-devel/autoconf:  2.13, 2.59-r7
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-r2
sys-devel/libtool:   1.5.22
virtual/os-headers:  2.6.11-r2
ACCEPT_KEYWORDS="x86"
AUTOCLEAN="yes"
CBUILD="i686-pc-linux-gnu"
CFLAGS="-O2 -march=athlon-xp -pipe"
CHOST="i686-pc-linux-gnu"
CONFIG_PROTECT="/etc /usr/kde/3.5/env /usr/kde/3.5/share/config /usr/kde/3.5/shutdown /usr/share/X11/xkb /usr/share/config"
CONFIG_PROTECT_MASK="/etc/gconf /etc/terminfo /etc/env.d"
CXXFLAGS="-O2 -march=athlon-xp -pipe"
DISTDIR="/usr/portage/distfiles"
FEATURES="autoconfig distcc distlocks metadata-transfer sandbox sfperms strict"
GENTOO_MIRRORS="http://distfiles.gentoo.org http://distro.ibiblio.org/pub/linux/distributions/gentoo"
MAKEOPTS="-j7"
PKGDIR="/usr/portage/packages"
PORTAGE_RSYNC_OPTS="--recursive --links --safe-links --perms --times --compress --force --whole-file --delete --delete-after --stats --timeout=180 --exclude='/distfiles' --exclude='/local' --exclude='/packages'"
PORTAGE_TMPDIR="/var/tmp"
PORTDIR="/usr/portage"
SYNC="rsync://rsync.gentoo.org/gentoo-portage"
USE="x86 3dnow 3dnowext X aac aalib alsa apm arts audacious avi berkdb bitmap-fonts cdr cli crypt cups dri dts dvd dvdread eds emboss encode esd flac foomaticdb fortran gdbm gif gpm gstreamer gtk gtk2 hal imlib isdnlog jpeg kde libg++ libwww mad matroska mikmod mmx motif mp3 mpeg musepack ncurses nls nptl ogg opengl oss pam pcre pdflib perl png pppd python qt quicktime readline reflection samba scanner sdl session spell spl sse ssl tcpd theora truetype truetype-fonts type1-fonts udev vorbis win32codecs x264 xml xmms xorg xv xvid zlib elibc_glibc input_devices_keyboard input_devices_mouse kernel_linux userland_GNU video_cards_nvidia video_cards_vesa"
Unset:  CTARGET, EMERGE_DEFAULT_OPTS, INSTALL_MASK, LANG, LC_ALL, LDFLAGS, LINGUAS, PORTAGE_RSYNC_EXTRA_OPTS, PORTDIR_OVERLAY

[equery list <ivman|hal>]
[I--] [  ] sys-apps/hal-0.5.5.1-r3 (0)
[I--] [  ] sys-apps/ivman-0.6.8 (0)

Long story short: I was attempting to set up a drive in my USB caddy. I wanted to remove the 3 existing partitions and just create one ext3 partition.

(These steps were tried on both firewire and usb interfaces.)

After initially plugging the device in, it correctly detected the [first] partition, which was 32M.

I ran fdisk, repartitioned, and ran mke2fs. Mounted the drive, tried using it, found out that the device only thought it had 32M (as reported by `df -h`, after I repartitioned it to one 120G partition!

I unmounted it, unplugged it, and plugged it in again. Same thing. At this point I switched interfaces (firewire->usb2) and tried again, same results. Went back to firewire, then I stopped both ivman and hald, remounted manually, and lo and behold, `df -h` was reporting the correct size. Restarted hald/ivman, unplugged and replugged and now all is fine.

I understand remounting after fdisk may not have updated the partition sizes, but I was assuming unplugging/replugging should have refreshed it.


(Guessing KDE component...)

[Comment 1 Doug Goldstein (RETIRED) 2006-10-30 17:34:07 UTC]

If df -h reported the wrong thing then it's not hal/ivman. That info comes directly from the kernel via the /proc interface. HAL reads the same info from the kernel and ivman reads the info from HAL. So basically you're kernel didn't process the unplug and clear everything out fully by the time you plugged it back in.

This is not a HAL/ivman issue.