Debian Bug report logs - #67782
'find' has race condition which sometimes causes spurious error messages

Toggle useless messages

Message #5 received at submit@bugs.debian.org (full text, mbox, reply):

From: "Sean Thompson"<sthompson@jil.com>

To: <submit@bugs.debian.org>

Subject: findutils

Date: Wed, 26 Jul 2000 15:11:53 -0400

Package: findutils
Version: 4.1-40
Severity: normal
File: /usr/local/bin/find

Running updatedb (or sometimes just find) gives the following error:

find: ./ArbitraryPath/ArbitraryFile: No such file or directory

It list different paths that do exist with no noticeable similarities yet they
cannot be checked.
what is the cause of these errors ?

Message #8 received at 67782-submitter@bugs.debian.org (full text, mbox, reply):

From: "H. Nanosecond" <aldomel@ix.netcom.com>

To: 67782-submitter@bugs.debian.org

Subject: Re: findutils

Date: Mon, 31 Jul 2000 16:03:47 -0400 (EDT)

Please tell us what the command line for find is when it gives the error
and do 'ls -l path' for the directory it errors with.
Also does it repeatedly error with the same file, or is
it intermitant?

Thanks.


  Package: findutils
  Version: 4.1-40
  Severity: normal  
  File: /usr/local/bin/find
  
  Running updatedb (or sometimes just find) gives the following error:
  
  find: ./ArbitraryPath/ArbitraryFile: No such file or directory
  
  It list different paths that do exist with no noticeable similarities yet they
  cannot be checked.
  what is the cause of these errors ?

Message #11 received at 67782-submitter@bugs.debian.org (full text, mbox, reply):

From: "H. Nanosecond" <aldomel@ix.netcom.com>

To: 67782-submitter@bugs.debian.org

Subject: Re: findutils

Date: Mon, 31 Jul 2000 16:07:38 -0400 (EDT)

Please tell us what the command line for find is when it gives the error
and do 'ls -l path' for the directory it errors with.
Also does it repeatedly error with the same file, or is
it intermitant?

Thanks.


  Package: findutils
  Version: 4.1-40
  Severity: normal  
  File: /usr/local/bin/find
  
  Running updatedb (or sometimes just find) gives the following error:
  
  find: ./ArbitraryPath/ArbitraryFile: No such file or directory
  
  It list different paths that do exist with no noticeable similarities yet they
  cannot be checked.
  what is the cause of these errors ?

Message #16 received at 67782@bugs.debian.org (full text, mbox, reply):

From: Kevin Dalley <kevind@rahul.net>

To: 67782@bugs.debian.org

Cc: "Sean Thompson"<sthompson@jil.com>

Subject: find failure

Date: 04 Jun 2001 01:19:17 -0700

I still don't know what caused the failure you mention.  Does this
problem still exist in findutils-4.1.7.  Please give the newer version
a try.
-- 
Kevin Dalley
kevind@rahul.net

Message #21 received at 67782@bugs.debian.org (full text, mbox, reply):

From: Tollef Fog Heen <tollef@add.no>

To: 67782@bugs.debian.org

Subject: Reproduceable

Date: 09 Jul 2001 19:47:26 +0200

I can reproduce this, it mostly occurs with files which comes and goes
away, like .fetchmail.lock.  I think it is because it does a
depth-first, but it has read the directory and then tries to stat the
file in question, which fails because the file has been
removed. (Guessing.)

-- 

Tollef Fog Heen
You Can't Win

Message #26 received at 67782@bugs.debian.org (full text, mbox, reply):

From: Kevin Dalley <kevind@rahul.net>

To: 67782@bugs.debian.org

Cc: Tollef Fog Heen <tollef@add.no>

Subject: Re: Bug#67782: disappearing files

Date: 10 Jul 2001 22:56:56 -0700

Is this really a bug?  Files are allowed to disappear during a find
command.  Is this error message unacceptable?

  find: ./ArbitraryPath/ArbitraryFile: No such file or directory

Tollef Fog Heen <tollef@add.no> writes:

> I can reproduce this, it mostly occurs with files which comes and goes
> away, like .fetchmail.lock.  I think it is because it does a
> depth-first, but it has read the directory and then tries to stat the
> file in question, which fails because the file has been
> removed. (Guessing.)
> 
> -- 
> 
> Tollef Fog Heen
> You Can't Win
> 

-- 
Kevin Dalley
kevind@rahul.net

Message #31 received at 67782@bugs.debian.org (full text, mbox, reply):

From: Tollef Fog Heen <tollef@add.no>

To: 67782@bugs.debian.org

Subject: Re: Bug#67782: disappearing files

Date: 11 Jul 2001 08:03:16 +0200

* Kevin Dalley 

| Is this really a bug?  Files are allowed to disappear during a find
| command.  Is this error message unacceptable?
| 
|   find: ./ArbitraryPath/ArbitraryFile: No such file or directory

It's annoying to get it once in a while from cron (read updatedb).
Why do I, as a system admin, care about the fact that find wasn't able
to stat a file because of some racing condition somewhere in find?

-- 

Tollef Fog Heen
You Can't Win

Message #36 received at 67782@bugs.debian.org (full text, mbox, reply):

From: owner@bugs.debian.org (Debian Bug Tracking System)

To: 67782@bugs.debian.org, tollef@add.no

Subject: Bug#67782: Info received (was Bug#67782: disappearing files)

Date: Wed, 11 Jul 2001 01:07:11 -0500

Thank you for the additional information you have supplied regarding
this problem report.  It has been forwarded to the developer(s) and
to the developers mailing list to accompany the original report.

Your message has been sent to the package maintainer(s):
 Kevin Dalley <kevind@rahul.net>

If you wish to continue to submit further information on your problem,
please send it to 67782@bugs.debian.org, as before.

Please do not reply to the address at the top of this message,
unless you wish to report a problem with the Bug-tracking system.

Darren Benham
(administrator, Debian Bugs database)

Message #41 received at 67782@bugs.debian.org (full text, mbox, reply):

From: Kevin Dalley <kevind@rahul.net>

To: 67782@bugs.debian.org

Subject: Re: Bug#67782: disappearing files

Date: 12 Jul 2001 12:50:51 -0700

You shouldn't get this message with the daily updatedb since the
stderr is sent to /dev/null in /etc/cron.daily/find.

Tollef Fog Heen <tollef@add.no> writes:

> It's annoying to get it once in a while from cron (read updatedb).
> Why do I, as a system admin, care about the fact that find wasn't able
> to stat a file because of some racing condition somewhere in find?

-- 
Kevin Dalley
kevind@rahul.net

Message #48 received at 67782-submitter@bugs.debian.org (full text, mbox, reply):

From: Andreas Metzler <ametzler@logic.univie.ac.at>

To: 67782-submitter@bugs.debian.org

Subject: Bug forwarded

Date: Mon, 21 Jul 2003 13:25:15 +0200

forwarded 67782 bug-findutils@gnu.org
thank

"Sean Thompson"<sthompson@jil.com> wrote
> Package: findutils
> Version: 4.1-40
> Severity: normal
> File: /usr/local/bin/find
>
> Running updatedb (or sometimes just find) gives the following error:
>
> find: ./ArbitraryPath/ArbitraryFile: No such file or directory
>
> It list different paths that do exist with no noticeable
> similarities yet they cannot be checked.  what is the cause of these
> errors?

I've forwarded this bug to upstream's bug tracking system at
http://savannah.gnu.org/bugs/?func=detailbug&bug_id=4391&group_id=61
          cu andreas

Message #53 received at 67782@bugs.debian.org (full text, mbox, reply):

From: James Youngman <jay@gnu.org>

To: 67782@bugs.debian.org

Subject: Fixed upstream via the use of the -ignore_readdir_race option.

Date: Sun, 31 Oct 2004 14:09:53 +0000

Fixed upstream via the use of the -ignore_readdir_race option.
See for example release 4.2.3.

Message #66 received at 67782-close@bugs.debian.org (full text, mbox, reply):

From: Andreas Metzler <ametzler@debian.org>

To: 67782-close@bugs.debian.org

Subject: Bug#67782: fixed in findutils 4.2.20-2

Date: Thu, 09 Jun 2005 14:32:18 -0400

Source: findutils
Source-Version: 4.2.20-2

We believe that the bug you reported is fixed in the latest version of
findutils, which is due to be installed in the Debian FTP archive:

findutils_4.2.20-2.diff.gz
  to pool/main/f/findutils/findutils_4.2.20-2.diff.gz
findutils_4.2.20-2.dsc
  to pool/main/f/findutils/findutils_4.2.20-2.dsc
findutils_4.2.20-2_i386.deb
  to pool/main/f/findutils/findutils_4.2.20-2_i386.deb



A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 67782@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Andreas Metzler <ametzler@debian.org> (supplier of updated findutils package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmaster@debian.org)


-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Format: 1.7
Date: Thu,  9 Jun 2005 20:07:37 +0200
Source: findutils
Binary: findutils
Architecture: source i386
Version: 4.2.20-2
Distribution: unstable
Urgency: low
Maintainer: Andreas Metzler <ametzler@debian.org>
Changed-By: Andreas Metzler <ametzler@debian.org>
Description: 
 findutils  - utilities for finding files--find, xargs, and locate
Closes: 5956 31858 67782 102914 111143 111578 159221 162838 169730 175372 176201 185202 185203 192330 202512 219855 244766 246040 254676 256367 260780 261598 262476 286977 295399 300323 300429 300631
Changes: 
 findutils (4.2.20-2) unstable; urgency=low
 .
   * Upload to unstable.
 .
 findutils (4.2.20-1) experimental; urgency=low
 .
   * [locate] Do not index cifs (Closes: #295399) lustre (Closes: #300323) and
     nfs4 (Closes: #300631) filesystems by default.
   * [locate] Ignore /media by default. (Closes: #300429)
   * New upstream version 4.2.20
     - includes up-to-date Italian translation. (Closes: #286977)
 .
 findutils (4.2.14-1) experimental; urgency=low
 .
   * New upstream version
     - includes patch to fix savannah #11495.
     - locate: New options  -L, --follow|-P, -H, --nofollow for ignoring
       dangling symlinks (or not). (Closes: #159221)
     - find supports -exec ... {} +.
     - locate support for FreeBSD options (Sclms, m and s are ignored, but
       undocumented, I've already opened upstream report #11730 on that.)
       (Closes: #102914)
     - find built with --enable-d_type-optimisation, for using
       readdir/getdents. (Closes: #202512)
 .
 findutils (4.2.11-2) experimental; urgency=low
 .
   * find -printf '%n' (hard link count) was broken (savannah #11495).
 .
 findutils (4.2.11-1) experimental; urgency=low
 .
   * New upstream version.
 .
 findutils (4.2.10.CVS20041219-1) experimental; urgency=low
 .
   * New upstream, CVS from CVS20041219 (pre- 4.2.11).
     * -printf '%P' works correctly again.
   * Run testsuite.
 .
 findutils (4.2.9-1) experimental; urgency=low
 .
   * New upstream source
 .
 findutils (4.2.8-1) experimental; urgency=low
 .
   * New upstream version
     - New option --arg-file=file and extended documentation about
       stdin-handling (short in manpage, more extensive in info).
       (Closes: #5956)
     - improved behavior on automounted directories.
 .
 findutils (4.2.5-1) experimental; urgency=low
 .
   * New upstream version
     - includes 25_destdir_localstatedir.dpatch, our last remaining patch, we
       are vanilla now.
   * Add minimal debian/README.source.
   * Chuan-kai Lin <cklin@debian.org> has offered to serve as backup
     maintainer. Thanks. Add him to Uploaders.
 .
 findutils (4.2.4-1) experimental; urgency=low
 .
   * New upstream version
     - Closes: #175372: findutils: man pages have L's on references
     - includes 10_updatedb-findopts patch.
     - does not print warning about listing options after non-options unless
       connected to a tty.
     - xargs now uses 128Kb instead of 20Kb of command line by default, as
       ARG_MAX is 131072 on linux this Closes: #261598.
 .
 findutils (4.2.3.CVS20041106-1) experimental; urgency=low
 .
   * New upstream version (pre-4.2.4, CVS 2004-11-06).
     - Closes: #176201: findutils: xargs enviroment size limited to 20k
     - Closes: #254676: xargs: environment is too large for exec
     - Closes: #219855: -printf: accepts C octal escapes, contrary to the
       documentation.
     - Closes: #246040: findutils: find -printf %H segfaults
     - Closes: #185202: findutils: extra ")" not caught
     - Closes: #185203: findutils: overflow causes -mtime to succeed
     - Closes: #244766: /usr/bin/locate: locate should have equivalent of
       -print0 option
     - documents type of supported regular expressions for -regex
       (Closes: #162838)
     - Closes: #256367: Deprecated usage of trap in locate/updatedb.sh
     - includes some examples in find.1 manpage. (Closes: #111578)
     - new option -ignore_readdir_race to selectively suppress the obnoxious
       race-condition caused errormessages. (Closes: #67782)
     - -print0/-0 issues explained in more detail. (Closes: #111143)
     - includes supplied patch for GNU/FreeBSD. (Closes: #192330)
     - updatedb invokes "cd /" before running commands as unprivileged user.
       (Closes: #262476)
     - 'xargs -n 1 -i' works. (Closes: #31858). Please note that it is no bug
       that -i changes xargs to pass a whole line of input as a single argument
       instead of splitting on any blank characters as without -i. - Other
       implementations behave the same and the -I XSI extension documented in
       SUSv3/POSIX works like this, too.
 .
    * Removed unnecessary patches: 10_missing_includes 20_missing_newlines
      30_locate_nologinsh 35_updatedb-location 36_savannah-8623 40_direntry
      50_install_info
   * Add shfs to PRUNFS (Closes: #260780)
   * New patch: 10_updatedb-findopts: Add --findoptions option to updatedb to
     pass global options to find.
   * Set FINDOPTIONS='-ignore_readdir_race' for updatedb.sh's cron-job.
     (Closes: #169730)
   * standards-version 3.6.1 (no changes required).
Files: 
 d8131ceadf2d1c15b52622c533021e9f 663 base required findutils_4.2.20-2.dsc
 3be936480966e5d4c165047efe0f0b4b 12033 base required findutils_4.2.20-2.diff.gz
 652a8b1a819cacd6fff1cc0033a11032 306194 base required findutils_4.2.20-2_i386.deb

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.1 (GNU/Linux)

iD8DBQFCqIguHTOcZYuNdmMRAiVzAJ9SXQUwkrX+XJpMXqozjAJW4b2/eQCfVmHn
9PgyJmTGtS+ww4AI2JuJi4o=
=fOpd
-----END PGP SIGNATURE-----

Send a report that this bug log contains spam.