Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com Delivered-To: mailing list cygwin AT cygwin DOT com MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-ID: <16072.7583.437368.989346@gargle.gargle.HOWL> Date: Sun, 18 May 2003 16:56:15 -0700 From: Martin Buchholz To: "Max Bowsher" Cc: Subject: Re: SPARSE files considered harmful - please revert In-Reply-To: <009001c31d93$b61d08e0$78d96f83@pomello> References: <16072 DOT 892 DOT 778395 DOT 24290 AT gargle DOT gargle DOT HOWL> <009001c31d93$b61d08e0$78d96f83 AT pomello> Reply-To: martin AT xemacs DOT org >>>>> "Max" == Max Bowsher writes: Max> Martin Buchholz wrote: >> As a result, a non-empty but small sparse file takes up a minimum of >> 16*clustersize bytes on the disk. My measurements suggest an overhead >> of 32kb per file with a cluster size of 4kb. Max> I just thought I'd throw a few more numbers into the debate: Max> I patched Cygwin to respond to CYGWIN=sparse / CYGWIN=nosparse Max> Then, I did a cvs co winsup: Max> "Size on disc" of checked out dir, as shown in Windows properties box: Max> Sparse: 40.7MB Max> Not sparse: 43.6MB Max> OK, so sparse seems to win? But that makes no sense - backed up by noting Max> that for various individual sparse files, "Size on disc" is reporting a size Max> which is not an integer number of clusters. Max> Now, Properties of disc, look at "Used space": Max> Difference in creating sparse checkout: ~ 200MB !!! Max> Difference in creating normal checkout: ~ 40MB This 5-fold expansion is just like what I saw. Max> Personally, I'm inclined to trust the overall disc stats more. The thing that matters is, what happens when the disk gets to 100%? This did happen to me. I do not recall getting any "disk full" error messages, but the disk was unhappy nevertheless. Processes writing to the disk would tend to hang. Max> I think this evidence suggests that sparse files should NOT be on by default Max> in Cygwin. Yup. Martin -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/