Antony Pavlenko wrote: > When i execute df to /net (automounted) directory i have seen unexpected > behaviour. > root at bserv4 # df -k /net/beesmc/store/explorers/new/ > Filesystem kbytes used avail capacity Mounted on > -hosts 0 0 0 0% > /net/beesmc/store/explorers/new > > but if open this dir and then execute df, then output is ok. > root at bserv4 # df -k /net/beesmc/store/explorers/new/ > Filesystem kbytes used avail capacity Mounted on > beesmc:/store/explorers/new > 859145280 644400967 201327220 77% > /net/beesmc/store/explorers/new > > This breaks Explorer thuogth nfs for example. So is it a bug or not?
It's not new behaviour, and is the result of a tradeoff. If you forced the statvfs(2) access of 'df' to trigger the mount, 'df' would do just that and cause mount storms by mounting stuff you don't care about. (Imagine this in /home for true fun.) If you need to trigger the mount, a reliable way to do that is to access the '.' directory in the mount point, e.g. jurassic[12]% df /net/arachnid/export/lab Filesystem kbytes used avail capacity Mounted on -hosts 0 0 0 0% /net/arachnid/export/lab jurassic[13]% df /net/arachnid/export/lab/. Filesystem kbytes used avail capacity Mounted on arachnid:/export/lab 17413250 13220960 4018158 77% /net/arachnid/export/lab Rob T
