This is the mail archive of the mailing list for the Cygwin project.

Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

Re: SPARSE files considered harmful - please revert

Max Bowsher wrote:

> >> Based on the posted numbers, global use of sparse files is a bad idea.
> Can
> >> we conditionalize sparse files on a $CYGWIN option? (Or something else, I
> >> don't mind, but the important thing is that it should not be on by
> default.)
> >
> > Why not make in on by default *when it can help*, i.e. when the write()
> > leaves holes?
> Does anyone know of any programs which write non-sparse files, but not
> contiguously? If there are none, then this approach should be fine.

There must be some... Cygwin would check that the holes are bigger than a
minimum threshold. Thus such files would never be really short and the
penalty for guessing wrong would never be large.
> In any case, the $CYGWIN approach could be a valid temporary measure until
> someone writes the heuristic code.

The code change I have in mind is very simple (because it's similar to what is
already done against a Win95 bug), so we might as well skip the intermediate step.
However a patch against current cvs might conflict with bigger changes that 
Chris Faylor has already made in his sandbox.


Unsubscribe info:
Problem reports:

Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]