From: Bruce Jerrick <bmj001@gmail.com>
To: cygwin@cygwin.com
Subject: cygwin 3.5.3-1 : "Device or resource busy" from 'find {pagefile,swapfile}.sys'
Date: Thu, 4 Apr 2024 07:22:36 -0700 [thread overview]
Message-ID: <e29f0d76-3b05-aa63-2e15-b2d5982d4410@gmail.com> (raw)
As of cygwin 3.5.3-1, 'find' reports "Device or resource busy" and
exits with status 1 on these two files:
$ find /cygdrive/c/{pagefile,swapfile}.sys
/cygdrive/c/pagefile.sys
find: ‘/cygdrive/c/pagefile.sys’: Device or resource busy
/cygdrive/c/swapfile.sys
find: ‘/cygdrive/c/swapfile.sys’: Device or resource busy
$ echo $?
1
It also happens with cygwin 3.6.0-0.109.ga0a25849f9dd .
It does not happen with cygwin 3.5.1-1 :
$ find /cygdrive/c/{pagefile,swapfile}.sys
/cygdrive/c/pagefile.sys
/cygdrive/c/swapfile.sys
$ echo $?
0
I first observed this from running 'updatedb'.
There appear to be no ill effects other than the spurious (?)
error messages and exit status. E.g., adding '-ls' to 'find'
seems to produce normal stat info.
next reply other threads:[~2024-04-04 14:22 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-04 14:22 Bruce Jerrick [this message]
2024-04-04 16:25 ` Corinna Vinschen
2024-04-04 17:57 ` Bruce Jerrick
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=e29f0d76-3b05-aa63-2e15-b2d5982d4410@gmail.com \
--to=bmj001@gmail.com \
--cc=cygwin@cygwin.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).