Unknown file system entries in the bdf output

[Rajeev Koolattil]

I have 3 new ia bl860 machines running on 11.31 OS. I am seeing some strange file systems (basically copy of the "/" (slash) file system. Those which are mounted starting with "/net" are fake entries..Please see below the bdf o/p.
==============================
# bdf
Filesystem kbytes used avail %used Mounted on
/dev/vg00/lvol3 4194304 394328 3770360 9% /
/dev/vg00/lvol1 2097152 332432 1751008 16% /stand
/dev/vg00/lvol9 8388608 1379048 6954912 17% /var
/dev/vg00/lvol11 1048576 21120 1019560 2% /var/tmp
/dev/vg00/lvol10 8388608 21104 8302272 0% /var/adm/crash
/dev/vg00/lvol7 8388608 2650904 5693000 32% /usr
/dev/vg00/lvol8 1048576 833744 213264 80% /usr/local
/dev/vg00/lvol6 8388608 658496 7669744 8% /tmp
/dev/vg00/lvol5 11534336 5578440 5909400 49% /opt
/ 4194304 394328 3770360 9% /net/b201u007
/ 4194304 394328 3770360 9% /net/b201u007.bg.na.jci.com
/ 4194304 394328 3770360 9% /net/b201u007b
/ 4194304 394328 3770360 9% /net/b201u007b.bg.na.jci.com
b7mdcs114:/bg_homeus
41303024 33524376 7778648 81% /home
/ 4194304 394328 3770360 9% /net/localhost
/ 4194304 394328 3770360 9% /net/loopback
b7mdcs114:/bg_dlc 7228016 5948744 1279272 82% /dlc
======================================
b201u005 is the hostname. b201u00b is another aliase to the hostname (the backup lan interface). It picks these entries from /etc/hosts file..These entries are neither present in fstab or autodirect..If we reboot the machie, it gets cleared off, but again it comes back after sometime..If you do ll , it will list you the "/" contents..basically these are pointing to "/". I tried to umount the these false entries, but it said, device busy, can be unmounted (since it's "/")..
I am seeing these entries in syslog file:

Jun 3 00:01:18 b201u007 sshd[22991]: ERROR: Unexpected error in conversation: (6)
Jun 3 00:01:18 b201u007 sshd[22991]: WARNING: Failed to get password for 'get_first_pass' option
Jun 3 00:01:25 b201u007 sshd[22996]: error: setsockopt SO_KEEPALIVE: Invalid argument
Jun 3 00:01:37 b201u007 sshd[22997]: error: setsockopt SO_KEEPALIVE: Invalid argument
Jun 3 00:01:39 b201u007 inetd[22998]: telnet/tcp: Connection from unknown (10.10.240.67) at Thu Jun 3 00:01:39 2010
Jun 3 00:01:43 b201u007 inetd[22999]: telnet/tcp: Connection from unknown (10.10.240.68) at Thu Jun 3 00:01:43 2010
Jun 3 00:02:26 b201u007 sshd[23220]: error: setsockopt SO_KEEPALIVE: Invalid argument
Jun 3 00:02:38 b201u007 sshd[23221]: error: setsockopt SO_KEEPALIVE: Invalid argument
Jun 3 00:02:40 b201u007 inetd[23222]: telnet/tcp: Connection from unknown (10.10.240.67) at Thu Jun 3 00:02:40 2010
Jun 3 00:02:44 b201u007 inetd[23223]: registrar/tcp: Connection from localhost (127.0.0.1) at Thu Jun 3 00:02:44 2010
Jun 3 00:02:44 b201u007 inetd[23225]: telnet/tcp: Connection from unknown (10.10.240.68) at Thu Jun 3 00:02:44 2010
================================
The IPs mentioedn here doesn't resolve to these hosts..except the loop back..I think these eerrors in syslog are common and nothing to do with this issue..but still just pasted for your reference..can anyone please suggest a solution here..It's a big pain for me..

[Steven E. Protter]

Shalom,

Check your .sh_history file for mount commands.

It it important to know how these mounts were made.

I think you need to umount them or shut down the automount configuration that made them and make sure all the IP and hostnames being used resolve properly before firing this up.

What is happening is not good, and I do not thing the current setup is reliable.

SEP

[singh sanjeev]

check /etc/auto.direct file if your not using automount ..then try disabling it and see the result..