Re: Help masking Stale file handle errors when using df

[Pádraig Brady]

On 08/09/17 05:33, Kaushal Modi wrote:
> On Fri, Sep 8, 2017 at 12:40 AM Pádraig Brady <address@hidden 
> <mailto:address@hidden>> wrote:
> 
> 
>     The older df was looking at a static list of mounts from /etc/mtab,
>     while the newer df uses the more dynamic /proc/self/mountinfo.
>     This latter file has entries to the problematic mount points.
>     I suspect ~/.snapshot/ may point to NFS and that is giving ESTALE
>     errors for various mount points.
> 
> 
> Hello Pádraig,
> 
> It seems like the Stale file handle issue is affecting du too. With du, 
> though, I get "Abort (core dumped)".
> 
> When using du from coreutils 8.4:
> 
>> cd ~
>> du -h --max-depth=1 .
> 596K    ./.mcop
> 23M     ./temp
> 40K     ./.DV_Checklist
> 4.0K    ./.adCwgCIC
> 270M    ./hugo
> 24K     ./.thumbnails
> 518M    ./.rustup
> 152K    ./.python-eggs
> /usr/bin/du: cannot read directory 
> `./.snapshot/daily.2017-09-01_2000/.Trash-0': Permission denied
> /usr/bin/du: cannot read directory 
> `./.snapshot/hourly.2017-09-08_0605/.Trash-0': Permission denied
> /usr/bin/du: cannot read directory 
> `./.snapshot/daily.2017-08-31_2000/.Trash-0': Permission denied
> /usr/bin/du: cannot access `./.snapshot/hourly.2017-09-08_0405': Stale file 
> handle
> /usr/bin/du: cannot read directory 
> `./.snapshot/daily.2017-09-03_2000/.Trash-0': Permission denied
> /usr/bin/du: cannot read directory 
> `./.snapshot/weekly.2017-09-03_0015/.Trash-0': Permission denied
> /usr/bin/du: cannot read directory 
> `./.snapshot/daily.2017-09-05_2000/.Trash-0': Permission denied
> /usr/bin/du: cannot read directory 
> `./.snapshot/daily.2017-09-06_2000/.Trash-0': Permission denied
> /usr/bin/du: cannot read directory 
> `./.snapshot/daily.2017-08-28_2000/.Trash-0': Permission denied
> /usr/bin/du: cannot read directory 
> `./.snapshot/hourly.2017-09-08_0705/.Trash-0': Permission denied
> 
> When using When using du from coreutils 8.28:
> 
>> cd ~
>> du -h --max-depth=1 .
> 596K    ./.mcop
> 23M     ./temp
> 40K     ./.DV_Checklist
> 4.0K    ./.adCwgCIC
> 270M    ./hugo
> 24K     ./.thumbnails
> 518M    ./.rustup
> 152K    ./.python-eggs
> Abort (core dumped)
> 
> It looks like the crash happens just when it gets into invalid ~/.snapshot 
> paths.
> 
> [Core dump attached]

Unfortunately that's for a stripped binary.
Note that was a large file to send to everyone.
Also note it contains a RAM dump from your machine so is insecure to send 
publicly.
Anyway....

Could you try with the unstripped binary. Something like:

gdb -args coreutils-8.28/src/du -h --max-depth=1 .
gdb> run
gdb> bt

thanks