bug-coreutils
[Top][All Lists]
Advanced

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

Re: [PATCH] df: new option --direct to not resolve a mount point


From: Kamil Dudka
Subject: Re: [PATCH] df: new option --direct to not resolve a mount point
Date: Tue, 7 Apr 2009 21:02:26 +0200
User-agent: KMail/1.9.7

On Tuesday 07 of April 2009 19:51:02 Pádraig Brady wrote:
> Well why I asked was I did essentially that test and was confused by:
>
> $ strace -e statfs64 ./df /home/padraig/ttt /home/padraig/
> statfs64("/home/padraig/ttt", ...) = 0
> statfs64("/home/padraig/", ...) = 0
>
> I.E. it seems each param is stated directly already?
> (which seems like the most sensible operation).
> But you explained that for remote file systems
> the stat is not done directly (why would it not be?).
> But again that doesn't seem to be the case here:
>
> $ mkdir t
> $ sudo mount -t nfs vod:/nfs t
> $ strace -e statfs64 ./df t/ISO/ t/Music/
> statfs64("t/ISO/", ...) = 0
> statfs64("t/Music/", ...) = 0
>
> What am I missing?

It works already if ./df t/ISO and t/Music/ are mount points. But it does not 
work for nested directories. There can be a different quota set for them:

$ strace -e trace=statfs \
    df -h /mnt/sorento /mnt/sorento/home /mnt/sorento/home/xdudka00
statfs("/mnt/sorento", ...) = 0
statfs("/mnt/sorento/home", ...) = 0
statfs("/mnt/sorento/home", ...) = 0


Kamil




reply via email to

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