public inbox for git@vger.kernel.org
 help / color / mirror / Atom feed
From: "'Yuri'" <yuri@rawbw.com>
To: Jeff King <peff@peff.net>
Cc: rsbecker@nexbridge.com, "'Junio C Hamano'" <gitster@pobox.com>,
	"'Git Mailing List'" <git@vger.kernel.org>
Subject: Re: [BUG] "git clean -df ." silently doesn't delete folders with stale .nfs* files
Date: Tue, 11 Jun 2024 00:43:51 -0700	[thread overview]
Message-ID: <ed33cfa9-d0e2-4e98-95e9-e210b24ac337@rawbw.com> (raw)
In-Reply-To: <20240611064847.GC3248245@coredump.intra.peff.net>

On 6/10/24 23:48, Jeff King wrote:
> $ git clean -df . warning: failed to remove 
> xx/.nfs0000000002c8197f00000002: Device or resource busy Which makes 
> sense, since the kernel fails our unlink() call. Maybe your system 
> behaves differently at the syscall level?


The system I observed the problem is Centos with the kernel 
3.10.0-1160.76.1.el7.x86_64 (10 years old).


"rm -rf xx" command also says Device or resource busy
But git-2.43.0 doesn't say anything.




Yuri



  reply	other threads:[~2024-06-11  7:44 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-06-10 18:36 [BUG] "git clean -df ." silently doesn't delete folders with stale .nfs* files Yuri
2024-06-10 19:58 ` 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' [this message]
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=ed33cfa9-d0e2-4e98-95e9-e210b24ac337@rawbw.com \
    --to=yuri@rawbw.com \
    --cc=git@vger.kernel.org \
    --cc=gitster@pobox.com \
    --cc=peff@peff.net \
    --cc=rsbecker@nexbridge.com \
    /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