GNU bug report logs - #41664
du give file not accessible

Previous Next

Package: coreutils;

Reported by: Sumit Gupta <sumitg1011 <at> gmail.com>

Date: Tue, 2 Jun 2020 15:04:03 UTC

Severity: normal

To reply to this bug, email your comments to 41664 AT debbugs.gnu.org.

Toggle the display of automated, internal messages from the tracker.

View this report as an mbox folder, status mbox, maintainer mbox


Report forwarded to bug-coreutils <at> gnu.org:
bug#41664; Package coreutils. (Tue, 02 Jun 2020 15:04:03 GMT) Full text and rfc822 format available.

Acknowledgement sent to Sumit Gupta <sumitg1011 <at> gmail.com>:
New bug report received and forwarded. Copy sent to bug-coreutils <at> gnu.org. (Tue, 02 Jun 2020 15:04:03 GMT) Full text and rfc822 format available.

Message #5 received at submit <at> debbugs.gnu.org (full text, mbox):

From: Sumit Gupta <sumitg1011 <at> gmail.com>
To: bug-coreutils <at> gnu.org
Subject: du give file not accessible
Date: Tue, 2 Jun 2020 15:12:08 +0530
[Message part 1 (text/plain, inline)]
Hey Team,

I have encountered this issue that while running the du command I get the
error like "file not present".

This generally happens because the du command and deletion operation are
working in parallel, meaning when the du operation is triggered at that the
file is present but during the operation the file is deleted so, at the
time of output when the command actually tries to access the file to run
the operation, it fails to locate the file.

Is this expected or shall the command be modified to ignore such files?

Thanks,
Sumit
[Message part 2 (text/html, inline)]

Information forwarded to bug-coreutils <at> gnu.org:
bug#41664; Package coreutils. (Tue, 02 Jun 2020 15:30:02 GMT) Full text and rfc822 format available.

Message #8 received at 41664 <at> debbugs.gnu.org (full text, mbox):

From: Paul Eggert <eggert <at> cs.ucla.edu>
To: Sumit Gupta <sumitg1011 <at> gmail.com>
Cc: 41664 <at> debbugs.gnu.org
Subject: Re: bug#41664: du give file not accessible
Date: Tue, 2 Jun 2020 08:28:56 -0700
On 6/2/20 2:42 AM, Sumit Gupta wrote:
> Is this expected or shall the command be modified to ignore such files?

It does seem reasonable that 'du' should ignore a file when the system call says
ENOENT, since the file isn't there and cannot be consuming disk space.




This bug report was last modified 4 years and 156 days ago.

Previous Next


GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.