From: Junio C Hamano <gitster@pobox.com>
To: <rsbecker@nexbridge.com>
Cc: "'Yuri'" <yuri@rawbw.com>, "'Git Mailing List'" <git@vger.kernel.org>
Subject: Re: [BUG] "git clean -df ." silently doesn't delete folders with stale .nfs* files
Date: Mon, 10 Jun 2024 17:29:49 -0700 [thread overview]
Message-ID: <xmqqmsnsxqwy.fsf@gitster.g> (raw)
In-Reply-To: <0ee501dabb91$aa2340a0$fe69c1e0$@nexbridge.com> (rsbecker@nexbridge.com's message of "Mon, 10 Jun 2024 19:55:20 -0400")
<rsbecker@nexbridge.com> writes:
> I have tried to reproduce your situation using git 2.43.0 without success.
>
> $ mkdir test
> $ cd test
> $ touch .nfs12309
> $ git clean -df .
> Removing .nfs12309
I suspec that this is different from a real NFSv3 client in that
removal of such "removed while still open" files would result in
another one automatically resurrected by the filesystem.
In any case, if we cannot remove a file (due to filesystem
limitation), we should report the fact, just like in a case
where we cannot remove a regular file, e.g.
$ cd git.git/
$ mkdir -p junk/ttt
$ >junk/ttt/sss
$ chmod a-w junk/ttt
$ cd junk
$ git clean -f -d -x ttt; echo $?
warning: failed to remove ttt/sss: Permission denied
1
Figuring out why it is not happening is left as an exercise to
readers ;-), as I no longer have an NFSv3 environment handy.
Thanks.
next prev parent reply other threads:[~2024-06-11 0:29 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 [this message]
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=xmqqmsnsxqwy.fsf@gitster.g \
--to=gitster@pobox.com \
--cc=git@vger.kernel.org \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox