log messates - automount error.

Robin Laing Robin.Laing at drdc-rddc.gc.ca
Tue Apr 15 17:15:37 UTC 2008


Since I installed F8 on my machine I get automount messages in my system 
logs.

---------------------Log messages

  Filesystem            Size  Used Avail Use% Mounted on
  /dev/sda9             2.0G  457M  1.4G  25% /
  /dev/sda10            272G  191G   67G  75% /export/home/rlaing-data
  /dev/sda7              19G   13G  5.2G  72% /usr
  /dev/sda6              19G  840M   18G   5% /var
  /dev/sda5              19G   71M   18G   1% /tmp
  /dev/sda1              99M   19M   76M  20% /boot


  --------------------- Automount Begin ------------------------

  **Unmatched Entries**
  st_ready: st_ready(): state = 2 path /pkg: 1152 Time(s)
  expire_cleanup: got thid 1079142736 path /net stat 0: 1152 Time(s)
  expire_proc: exp_proc = 1079142736 path /pkg: 1152 Time(s)
  st_expire: state 1 path /misc: 1152 Time(s)
  expire_cleanup: got thid 1079142736 path /home stat 0: 1152 Time(s)
  st_expire: state 1 path /pkg: 1152 Time(s)
  expire_cleanup: sigchld: exp 1079142736 finished, switching from 2 to 
1: 4608 Time(s)
  st_ready: st_ready(): state = 2 path /misc: 1152 Time(s)
  expire_proc: exp_proc = 1079142736 path /net: 1152 Time(s)
  expire_cleanup: got thid 1079142736 path /misc stat 0: 1152 Time(s)
  expire_proc: exp_proc = 1079142736 path /misc: 1152 Time(s)
  st_ready: st_ready(): state = 2 path /home: 1152 Time(s)
  st_ready: st_ready(): state = 2 path /net: 1152 Time(s)
  expire_cleanup: got thid 1079142736 path /pkg stat 0: 1152 Time(s)
  st_expire: state 1 path /net: 1152 Time(s)
  expire_proc: exp_proc = 1079142736 path /home: 1152 Time(s)
  st_expire: state 1 path /home: 1152 Time(s)

  ---------------------- Automount End -------------------------

Mounts

/dev/sda9 on / type ext3 (rw)
proc on /proc type proc (rw)
sysfs on /sys type sysfs (rw)
devpts on /dev/pts type devpts (rw,gid=5,mode=620)
/dev/sda10 on /export/home/rlaing-data type ext3 (rw,nosuid,nodev)
/dev/sda7 on /usr type ext3 (rw)
/dev/sda6 on /var type ext3 (rw)
/dev/sda5 on /tmp type ext2 (rw)
/dev/sda1 on /boot type ext3 (rw)
tmpfs on /dev/shm type tmpfs (rw)
none on /proc/sys/fs/binfmt_misc type binfmt_misc (rw)
sunrpc on /var/lib/nfs/rpc_pipefs type rpc_pipefs (rw)
fusectl on /sys/fs/fuse/connections type fusectl (rw)
nfsd on /proc/fs/nfsd type nfsd (rw)
/export/home/rlaing on /home/rlaing type none (rw,bind)
/export/home/rlaing-data on /net/eagle1/export/home/rlaing-data type 
none (rw,bind)
---------------------------------------


The above are from the weekend.  I was not logged in at any time over 
this period.  When I am logged in, it gets worse.  User login is using 
LDAP.


I have gone through the log files and any other information that I can 
to try tracing this down.  Using wireshark, no messages are seen trying 
to communicate to the LDAP server when the error messages occur.

I talked to two different IT people and neither of them can point me in 
a direction to look.

I have exhausted my thought processes on finding this problem.


-- 
Robin Laing




More information about the fedora-list mailing list