public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: Cedric Blancher <cedric.blancher@gmail.com>
To: cygwin@cygwin.com
Cc: Brian Inglis <Brian.Inglis@systematicsw.ab.ca>
Subject: Re: /usr/bin/fallocate -v -d -l 2 myfile takes forever
Date: Mon, 29 Jan 2024 11:39:04 +0100	[thread overview]
Message-ID: <CALXu0UcHQVOHsgE5QjOj7_LoiiXvOa4RveYP-oZ32pkGd6GSfQ@mail.gmail.com> (raw)
In-Reply-To: <d6134ced-53f6-46bb-9448-7b2f7efc636b@SystematicSW.ab.ca>

On Mon, 29 Jan 2024 at 09:33, Brian Inglis via Cygwin <cygwin@cygwin.com> wrote:
>
> On 2024-01-28 23:44, Cedric Blancher via Cygwin wrote:
> > rm -f myfile
> > touch myfile
> > /usr/bin/fallocate -v -d -l myfile takes forever with latest Cygwin 3.5
>
> It takes much longer without Cygwin 3.5!
>
> Your fallocate(1) option -l has no length numeric argument and no -o offset
> numeric argument to specify the start of the range.

Apologies, I typed this from a screenshot, and made a mistake.
The line should be:
/usr/bin/fallocate -v -d -l 2 myfile
like in the Subject

Offset is 0 i this case, because no -o was given

Ced
-- 
Cedric Blancher <cedric.blancher@gmail.com>
[https://plus.google.com/u/0/+CedricBlancher/]
Institute Pasteur

      reply	other threads:[~2024-01-29 10:39 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
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 [this message]

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=CALXu0UcHQVOHsgE5QjOj7_LoiiXvOa4RveYP-oZ32pkGd6GSfQ@mail.gmail.com \
    --to=cedric.blancher@gmail.com \
    --cc=Brian.Inglis@systematicsw.ab.ca \
    --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).