[prev in list] [next in list] [prev in thread] [next in thread] 

List:       coreutils
Subject:    Re: New switch for coreutils?
From:       Pádraig_Brady <P () draigBrady ! com>
Date:       2017-09-11 16:34:54
Message-ID: c49cd9ac-7cf2-b7c9-b5d7-6fb8b4dd6fa1 () draigBrady ! com
[Download RAW message or body]

On 11/09/17 05:47, Philipp Thomas wrote:
> 
> Prior to coreutils 8, df would do a statfs then print out info for each
> individual filesystem sequentially.  This was useful for troubleshooting
> network filesystems in particular, as df hangs at the individual fs that
> had the issues.
> 
> Probably as a result of \
> http://git.savannah.gnu.org/gitweb/?p=coreutils.git;a=commitdiff;h=ddf6fb8686b1ed6a26d5f1c76a642d0fb5fe7ba7
>  df no longer does this.  Instead, it does statfs on all filesystems before
> attempting to print anything.  The result is that if there's a problem with
> any filesystem, no output is printed out.  This is irritating, to the point
> that some (big) customers keep the old df around just for this.
> 
> My question is, if a patch that allows doing it the old sequential way would
> have a chance of being accepted.

I presume df -l is not an option?
Maybe, though df would still hang eventually right?
Outputting as early as possible would be beneficial.
Maybe we could do that with df -a

cheers,
Pádraig


[prev in list] [next in list] [prev in thread] [next in thread]