public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: Corinna Vinschen <corinna-cygwin@cygwin.com>
To: cygwin@cygwin.com
Subject: Re: Sparse file support for SMB by default? Re: Comment about "Cygwin: sparse support: enable automatic sparsifying of files on SSDs", extend feature to VMware/qemu disks?
Date: Thu, 7 Dec 2023 11:56:47 +0100	[thread overview]
Message-ID: <ZXGk7xKkOv0tDEyx@calimero.vinschen.de> (raw)
In-Reply-To: <44fb3609-4170-424d-a438-cadab1966f94@shaddybaddah.name>

On Dec  7 17:42, Shaddy Baddah via Cygwin wrote:
> Hi Corinna,
> 
> On 6/12/2023 8:38 pm, Corinna Vinschen via Cygwin wrote:
> 
> > If you want to see if a filesystem supports that flag, just use the
> > /usr/lib/csih/getVolInfo tool:
> > 
> >    $ /usr/lib/csih/getVolInfo .
> >    Device Type        : 7
> >    Characteristics    : 20020
> >    Volume Name        : <root>
> >    Serial Number      : 2292001085
> >    Max Filenamelength : 255
> >    Filesystemname     : <NTFS>
> >    Flags              : 3e72eff
> >      FILE_CASE_SENSITIVE_SEARCH        : TRUE
> ...
> >      FILE_SUPPORTS_GHOSTING            : FALSE
> 
> Is is worth it/possible to extend this getVolInfo to also include the
> SSINFO_FLAGS_NO_SEEK_PENALTY flag in the output?-- Regards, Shaddy

Good idea.  I created a patch and a new version of the csih package
(0.9.14) will be available shortly.


Thanks,
Corinna

  reply	other threads:[~2023-12-07 10:56 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-12-01 10:12 Cedric Blancher
2023-12-01 10:43 ` Corinna Vinschen
2023-12-06  8:49   ` Sparse file support for SMB by default? " Cedric Blancher
2023-12-06  9:38     ` Corinna Vinschen
2023-12-06 10:24       ` Corinna Vinschen
2023-12-07  6:42       ` Shaddy Baddah
2023-12-07 10:56         ` Corinna Vinschen [this message]
2023-12-18 11:10       ` Cedric Blancher
2024-01-08 14:13         ` Corinna Vinschen

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=ZXGk7xKkOv0tDEyx@calimero.vinschen.de \
    --to=corinna-cygwin@cygwin.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).