Is this a known problem? I've seen this problem both under 2.0.6 and 2.0.7, on my Debian Linux system (kernel 2.2.14): A Win95 share that I mounted under smbfs will show up as mounted in df, and even contain the correct Used/Available info. If I do an 'ls' on the mountpoint, I see no files. If I 'umount' the share, I get the 'not mounted' error, but then no longer see the share in df. This whole thing is a particular pain if you're trying to write Perl scripts that do things based on whether shares are mounted, since Filesys::Diskfree seems the best way to tell, but this problem breaks it, since it apparently relies on df. I just noticed the opposite (of sorts) also happens. I performed the sequence below within the space of a few seconds. The share really is mounted, but the first df I performed did not show it. Notice also that the 2nd df does *not* show the correct Used/Available info. root@debserver:~# df Filesystem 1k-blocks Used Available Use% Mounted on /dev/hda1 1981000 608800 1269788 32% / /dev/hda3 2858128 1032622 1677708 38% /var /dev/hdc1 794118 445793 307301 59% /usr /dev/hdc3 189335 159760 19798 89% /home root@debserver:~# df Filesystem 1k-blocks Used Available Use% Mounted on /dev/hda1 1981000 608800 1269788 32% / /dev/hda3 2858128 1032636 1677694 38% /var /dev/hdc1 794118 445793 307301 59% /usr /dev/hdc3 189335 159760 19798 89% /home //ACCOUNTANT/C 2096832 0 2096832 0% /mnt/accountant_c root@debserver:~# ls /mnt/accountant_c AUTOEXEC.BAT CONFIG.WIN MSDOS.SYS SCANDISK.LOG ffastun.ffa qdata BOOTLOG.PRV DETLOG.OLD My Documents SETUPLOG.TXT ffastun.ffl BOOTLOG.TXT DETLOG.TXT NETLOG.TXT SUHDLOG.DAT ffastun.ffo BackupQB IO.SYS OEMROM.BIN SYSTEM.1ST ffastun0.ffx COMMAND.COM LWRITE Program Files WINDOWS logo.sys CONFIG.SYS MSDOS.--- RECYCLED debbie prime
On Wed, 30 Aug 2000, Keith G. Murphy wrote:> Is this a known problem?No. I have never heard of this re-appearing act.> A Win95 share that I mounted under smbfs will show up as mounted in df, > and even contain the correct Used/Available info. If I do an 'ls' on > the mountpoint, I see no files. If I 'umount' the share, I get the 'not > mounted' error, but then no longer see the share in df.Maybe it never actually mounted anything but it wrote something in /etc/mtab. As root: # df Filesystem 1k-blocks Used Available Use% Mounted on /dev/sda1 202220 136282 55498 71% / ... /dev/sda11 3059728 1060632 1843672 37% /mnt/data # echo "/dev/sda5 /mnt/empty ext2 ro 0 0" >> /etc/mtab # df Filesystem 1k-blocks Used Available Use% Mounted on /dev/sda1 202220 136282 55498 71% / ... /dev/sda11 3059728 1060632 1843672 37% /mnt/data /dev/sda5 202220 136282 55498 71% /mnt/empty # ls -alF /mnt/empty total 2 drwxr-xr-x 2 root root 1024 Apr 14 17:57 ./ drwxr-xr-x 19 root root 1024 Jul 31 17:44 ../ # umount /mnt/empty umount: /dev/sda5: not found umount: /mnt/empty: not mounted Some differences from your description, mainly that the used/available isn't at all right. 'cat /proc/mounts' shows what is actually mounted. df and mount both trust /etc/mtab for what to display (at least the versions I have).> I just noticed the opposite (of sorts) also happens. I performed the > sequence below within the space of a few seconds. The share really is > mounted, but the first df I performed did not show it. Notice also that > the 2nd df does *not* show the correct Used/Available info.This is very strange. "old" mount programs would have trouble mounting smbfs, causing a delay between the mount command and when the mount becomes useable. accountant_c is not under automounter control? That could be an idea why it suddenly appears. Any funny kernel log messages? /Urban