bug-fileutils
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Strange behaviour


From: Olivier Beyssac
Subject: Strange behaviour
Date: Tue, 18 Nov 2003 16:26:36 +0100
User-agent: Mutt/1.4.1i

Hello,

I can't understand why df, when given an argument, parses the whole list
of mount points:
    % strace df /usr 2>&1 | grep ^stat
    stat64("/usr", {st_mode=S_IFDIR|0755, st_size=4096, ...}) = 0
    statfs("/usr", {f_type="EXT2_SUPER_MAGIC", f_bsize=4096, f_blocks=492147, 
f_bfree=251212, f_files=250368, f_ffree=173436, f_namelen=255}) = 0
    stat64("/usr", {st_mode=S_IFDIR|0755, st_size=4096, ...}) = 0
    stat64("/", {st_mode=S_IFDIR|0755, st_size=1024, ...}) = 0
    stat64("/", {st_mode=S_IFDIR|0755, st_size=1024, ...}) = 0
    stat64("/proc", {st_mode=S_IFDIR|0555, st_size=0, ...}) = 0
    stat64("/dev/pts", {st_mode=S_IFDIR|0755, st_size=0, ...}) = 0
    stat64("/var", {st_mode=S_IFDIR|0755, st_size=1024, ...}) = 0
    stat64("/tmp", {st_mode=S_IFDIR|S_ISVTX|0777, st_size=7168, ...}) = 0
    stat64("/usr", {st_mode=S_IFDIR|0755, st_size=4096, ...}) = 0

This is really painful when you have a NFS mountpoint that is broken,
for example, and that you want statistics on another, perfectly working,
NFS mount point.  If the broken one is located before the good one in
/proc/mounts, you'll have to wait for the NFS timeout, if any, to get
the result.

Regards.

-- 
Olivier Beyssac - address@hidden




reply via email to

[Prev in Thread] Current Thread [Next in Thread]