From: Gabor Gombas <gombasg@digikabel.hu>
To: 'Yuri' <yuri@rawbw.com>
Cc: Jeff King <peff@peff.net>,
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: Thu, 13 Jun 2024 10:09:39 +0200 [thread overview]
Message-ID: <ZmqpQ4FkfXRm2jAE@lan> (raw)
In-Reply-To: <ed33cfa9-d0e2-4e98-95e9-e210b24ac337@rawbw.com>
On Tue, Jun 11, 2024 at 12:43:51AM -0700, 'Yuri' wrote:
> 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.
On RHEL7:
$ mkdir foo
$ cd foo
$ git --version
git version 2.39.2
$ git init
$ mkdir xx
$ touch xx/x
$ tail -f xx/x
$ git clean -dfx
warning: failed to remove xx/: Directory not empty
Removig xx/x
$ git clean -dfx
warning: failed to remove xx/.nfs[... long hex number...]: Device or resource busy
Well, try something:
$ echo xx > .gitignore
$ git add .gitignore
$ git commit -m foo
$ git clean -df
[there is no output - bingo]
$ git clean -dfx
warning: failed to remove xx/.nfs[... long hex number...]: Device or resource busy
Regards,
Gabor
next prev parent reply other threads:[~2024-06-13 8:40 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'
2024-06-13 8:09 ` Gabor Gombas [this message]
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=ZmqpQ4FkfXRm2jAE@lan \
--to=gombasg@digikabel.hu \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=peff@peff.net \
--cc=rsbecker@nexbridge.com \
--cc=yuri@rawbw.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.