When using floppy and supermount: 1. insert a floppy 2. ls /mnt/floppy, I get a file listing 3. eject the floppy 4. ls /mnt/floppy, now I get I/O error that's the correct behavior right? but when I try with memory stick: 1. insert memorystick to card reader 2. ls /mnt/memorystick, and I get a file listing 3. remove the stick 4. ls /mnt/memorystick, and I still get the same file listing it persists even one hour after removing the memory stick (I don't have a second memstick, so I can't test inserting another memstick at this point) Only a reboot will clear that file listing problem. Umounting /mnt/memorystick will lock up the system hard. Kernel: lolo-sources 2.4.20-lolo-r2_pre2 relevant fstab entries: none /mnt/floppy supermount fs=auto,dev=/dev/fd0,--,defaults,sync,uid=1000 0 0 none /mnt/smartmedia supermount fs=auto,dev=/dev/sda1,--,defaults,sync,uid=1000 0 0 none /mnt/compactflash supermount fs=auto,dev=/dev/sdb1,--,defaults,sync,uid=1000 0 0 none /mnt/securedigital supermount fs=auto,dev=/dev/sdc1,--,defaults,sync,uid=1000 0 0 none /mnt/memorystick supermount fs=auto,dev=/dev/sdd1,--,defaults,sync,uid=1000 0 0 card reader: USB PQI travel flash, 6-in-1 with 4 slots Reproducible: Always Steps to Reproduce: 1. reboot 2. insert memstick 3. ls /mnt/memorystick 4. remove memstick 5. ls /mnt/memorystick, I get the same listing and it always remembers that unless rebooted Actual Results: the file listing is cached even after the media is removed, and nothing but reboot will clear the cache Expected Results: the same way it does to the floppy Portage 2.0.46-r12 (default-x86-1.4, gcc-3.2.2, glibc-2.3.1-r2) ================================================================= System uname: 2.4.20-lolo-r2_pre2 i686 AMD Athlon(TM) XP 1800+ GENTOO_MIRRORS="http://csociety-ftp.ecn.purdue.edu/pub/gentoo/" CONFIG_PROTECT="/etc /var/qmail/control /usr/kde/2/share/config /usr/X11R6/lib/X11/xkb /usr/kde/3.1/share/config /usr/kde/3/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="" USE="apm libg++ pdflib spell zlib slang tetex svga guile gpm esd ldap 3dnow aalib alsa arts avi berkdb bonobo cdr cjk crypt cups dga doc dvd encode evo fbcon flash gd gdbm ggz gif gnome gphoto2 gtk gtk2 gtkhtml imap imlib java jikes jpeg kde libgda libwww maildir mbox mikmod mmx motif mozilla mpeg mysql ncurses nls oggvorbis opengl oss pam pda perl plotutils png python qt qtmt quicktime readline ruby samba scanner sdl slp sse ssl tcltk tcpd truetype tiff wmf X xface xml xml2 xmms xv x86" COMPILER="gcc3" CHOST="i686-pc-linux-gnu" CFLAGS="-march=athlon-xp -O3 -pipe" CXXFLAGS="-march=athlon-xp -O3 -pipe" ACCEPT_KEYWORDS="x86" MAKEOPTS="-j2" AUTOCLEAN="yes" SYNC="rsync://rsync.us.gentoo.org/gentoo-portage" FEATURES="sandbox ccache"
apparently this is a bug that has now been fixed in the supermount code, lolo-sources will be updating to it soon.
test with the latest lolo-sources if possible.
I did, but the problem still persists :( 2.4.20-lolo-r2_pre3
try this with either gentoo-sources-2.4.20-r3. there is updated supermount code in both. Thanks, Jay
this seems to be fixed in bothe gentoo-sources-2.4.20-r3 & pfeifer-sources-2.4.20_pre7. closing. Jay
