From: Cedric Blancher <cedric.blancher@gmail.com>
To: cygwin@cygwin.com
Subject: Re: /usr/bin/fallocate -v -d -l 2 myfile takes forever
Date: Tue, 5 Mar 2024 09:46:12 +0100 [thread overview]
Message-ID: <CALXu0UdUXGPsbuwBhyT-_W7GXdsNw7=VYQvWS15d3fvJfyj7qg@mail.gmail.com> (raw)
In-Reply-To: <1de1f9f9-f8ee-45bf-9c63-fd151b6714f7@maxrnd.com>
On Mon, 29 Jan 2024 at 10:46, Mark Geisert via Cygwin <cygwin@cygwin.com> wrote:
>
> On 1/28/2024 11:56 PM, Mark Geisert via Cygwin wrote:
> > On 1/28/2024 10:44 PM, Cedric Blancher via Cygwin wrote:
> >> Good morning!
> >>
> >> rm -f myfile
> >> touch myfile
> >> /usr/bin/fallocate -v -d -l myfile takes forever with latest Cygwin 3.5
> > ^ length goes here, before filename
> >
> > I believe you need to
> > chattr +S myfile
> > after the 'touch' to make the file sparsifiable.
> >
> > Also, I'm unsure if '-d' makes sense when initially allocating a sparse
> > file. If I leave it off, fallocate does the right thing.
> >
> > I'm separately investigating the 'takes forever' report.
>
> It's taking forever because it's in an infinite loop looking for data
> followed by a hole, which is not present in a new file being created.
> This is due to the '-d' option being specified. fallocate ought to
> diagnose this condition rather than looping forever, but here we are.
>
> It's possible we have an old fallocate from an old util-linux package.
> I'll try to investigate this further when I have time.
>
Any update on this issue?
Ced
--
Cedric Blancher <cedric.blancher@gmail.com>
[https://plus.google.com/u/0/+CedricBlancher/]
Institute Pasteur
next prev parent reply other threads:[~2024-03-05 8:46 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-29 6:44 Cedric Blancher
2024-01-29 7:56 ` Mark Geisert
2024-01-29 9:45 ` Mark Geisert
2024-03-05 8:46 ` Cedric Blancher [this message]
2024-03-05 10:43 ` Mark Geisert
2024-03-08 9:43 ` Mark Geisert
2024-03-05 11:04 ` Mark Geisert
2024-01-29 8:32 ` Brian Inglis
2024-01-29 10:39 ` Cedric Blancher
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='CALXu0UdUXGPsbuwBhyT-_W7GXdsNw7=VYQvWS15d3fvJfyj7qg@mail.gmail.com' \
--to=cedric.blancher@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).