X-Recipient: archive-cygwin@delorie.com
DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org 8902B3858289
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=cygwin.com;
	s=default; t=1704723218;
	bh=mLvMFUdT5n2Pzblr+qa1IvN8TJ8GtHrxcFUYpmdlxyQ=;
	h=Date:To:Subject:References:In-Reply-To:List-Id:List-Unsubscribe:
	 List-Archive:List-Post:List-Help:List-Subscribe:From:Reply-To:Cc:
	 From;
	b=teKRw0QPD3YL6uv4WB0oUV+n11nlXTychFcQ7rYyLIMz70hVf7G/7n7QEQAsiWrLQ
	 8tQ8P+WsLQsu1KXsOX2bbbAsguFSzJ0W358fZRDpYmQyBOxge+tEX6ldeNsmPbz3s7
	 aAhG0ojK0cO0HzilfZAVUmNYaU2w/gB4ckDOeP2A=
X-Original-To: cygwin@cygwin.com
Delivered-To: cygwin@cygwin.com
DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org 0F8AE385842A
Date: Mon, 8 Jan 2024 15:13:14 +0100
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?
Message-ID: <ZZwC-uXKO6LmcBIy@calimero.vinschen.de>
Mail-Followup-To: cygwin@cygwin.com
References: <CALXu0Udckh5XVXr23yaz1Fg1DoJ_12jE+XKo-jukDPoeL_vdZA@mail.gmail.com>
 <ZWm4xf0yfNjYqL-V@calimero.vinschen.de>
 <CALXu0Ue3LjqdZKgK46=E-TgXBunUn6=LHqKi1Y5-N1hoAA_Fcg@mail.gmail.com>
 <ZXBBJJ18Q3y4CSBx@calimero.vinschen.de>
 <CALXu0Uczsr4pPE1Z2bhZavStXQVDFchCeAX3TAr9FFyVmOOmQA@mail.gmail.com>
MIME-Version: 1.0
Content-Disposition: inline
In-Reply-To: <CALXu0Uczsr4pPE1Z2bhZavStXQVDFchCeAX3TAr9FFyVmOOmQA@mail.gmail.com>
X-BeenThere: cygwin@cygwin.com
X-Mailman-Version: 2.1.30
Precedence: list
List-Id: General Cygwin discussions and problem reports <cygwin.cygwin.com>
List-Unsubscribe: <https://cygwin.com/mailman/options/cygwin>,
 <mailto:cygwin-request@cygwin.com?subject=unsubscribe>
List-Archive: <https://cygwin.com/pipermail/cygwin/>
List-Post: <mailto:cygwin@cygwin.com>
List-Help: <mailto:cygwin-request@cygwin.com?subject=help>
List-Subscribe: <https://cygwin.com/mailman/listinfo/cygwin>,
 <mailto:cygwin-request@cygwin.com?subject=subscribe>
From: Corinna Vinschen via Cygwin <cygwin@cygwin.com>
Reply-To: cygwin@cygwin.com
Cc: Corinna Vinschen <corinna-cygwin@cygwin.com>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Errors-To: cygwin-bounces+archive-cygwin=delorie.com@cygwin.com
Sender: "Cygwin" <cygwin-bounces+archive-cygwin=delorie.com@cygwin.com>

On Dec 18 12:10, Cedric Blancher via Cygwin wrote:
> On Wed, 6 Dec 2023 at 10:39, Corinna Vinschen via Cygwin
> <cygwin@cygwin.com> wrote:
> > Basically, with 3.4, you always have to set the "sparse" mount option,
> > with 3.5, on local SSDs you don't.  I don't see a problem here.
> 
> How can I remount the existing C: mount with the "sparse" option in
> Cygwin 3.4? I cannot get it working, or I am too stupid.

How about you tell us what you did, so we can check?  I know that it
works, but apparently something crucial is missing.

One thing, for instance, is, that changes in fstab and fstab.d only
start working after stopping all Cygwin processes of the user or after
calling `mount -a'.

Another is, of course, how your fstab line actually looked like.


Corinna

-- 
Problem reports:      https://cygwin.com/problems.html
FAQ:                  https://cygwin.com/faq/
Documentation:        https://cygwin.com/docs.html
Unsubscribe info:     https://cygwin.com/ml/#unsubscribe-simple