[Top][All Lists]
[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 18:51:27 +0200 |
User-agent: |
KMail/1.9.7 |
On Tuesday 07 of April 2009 14:22:38 Pádraig Brady wrote:
> Kamil Dudka wrote:
> > Hello,
> >
> > I am attaching a single patch for df adding a new option --direct to not
> > resolve mount point and show statistics directly for a file. It can be
> > especially useful for NFS mount points if there is a boundary between two
> > storage policies behind the mount point.
>
> So this only changes the headings and not the values,
> and is only useful when multiple files specified?
I don't think so. If I run df with /home/kdudka/foo and /home is a mount point
it calls statfs for /home. With the new --direct option it calls statfs
directly for /home/kdudka/foo. The last column then shows the (canonized)
file (or directory) name and not the mount point, therefore the change
in heading.
Consider a NFS mount point. If there is different quota set for a subtree on
the remote storage, it shows different values with --direct.
> Why is --direct mutually exclusive with --local?
It does not make sense as any mount point resolving is bypassed and it always
shows the statistics for given file (if exists).
Kamil