public inbox for git@vger.kernel.org
 help / color / mirror / Atom feed
From: Yuri <yuri@rawbw.com>
To: Git Mailing List <git@vger.kernel.org>
Subject: [BUG] "git clean -df ." silently doesn't delete folders with stale .nfs* files
Date: Mon, 10 Jun 2024 11:36:28 -0700	[thread overview]
Message-ID: <ae862adb-1475-48e9-bd50-0c07dc42a520@rawbw.com> (raw)

NFS sometimes leaves files like .nfsXXXXXXXXXXX which usually means that 
some process that has this file open is alive.


"git clean -df ." was supposed to remove the folder where such file is 
located, but it encountered the failure, and silently ignored it and 
succeeded.


Desired behavior: "git clean -df ." should notify the user with warnings 
or errors for each such file that it failed to remove.


When "git clean -df ." succeeded I ran the next command and it failed 
because of the still-present folder with the .nfsXXXXXXXXX file in it.


I believe that this is a bug in git.


git-2.38.1



Thanks,

Yuri



             reply	other threads:[~2024-06-10 18:58 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-06-10 18:36 Yuri [this message]
2024-06-10 19:58 ` [BUG] "git clean -df ." silently doesn't delete folders with stale .nfs* files Junio C Hamano
2024-06-10 20:08   ` Yuri
2024-06-10 21:37     ` Junio C Hamano
2024-06-10 23:27       ` Yuri
2024-06-10 23:55         ` rsbecker
2024-06-11  0:29           ` Junio C Hamano
2024-06-11  1:09           ` 'Yuri'
2024-06-11  1:19             ` rsbecker
2024-06-11  1:22               ` 'Yuri'
2024-06-11  1:46                 ` Chris Torek
2024-06-11  6:48             ` Jeff King
2024-06-11  7:43               ` 'Yuri'
2024-06-13  8:09                 ` Gabor Gombas
2024-06-13  9:21                   ` 'Yuri'
2024-06-11 13:48               ` rsbecker
2024-06-11 17:46                 ` 'Yuri'

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=ae862adb-1475-48e9-bd50-0c07dc42a520@rawbw.com \
    --to=yuri@rawbw.com \
    --cc=git@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox