Sparse files - Revision history

Omeringen: Undo revision 2942 by Izegiwera (Talk)

2010-11-18T12:51:06Z

Undo revision 2942 by Izegiwera (Talk)

Izegiwera at 00:20, 18 November 2010

2010-11-18T00:20:03Z

80.168.236.208: can't count :)

2007-03-31T20:20:53Z

can't count :)

Leuk he: vista remark

2007-03-20T14:27:32Z

vista remark

Leuk he: New page: A sparse file is a file who's internally unused internal ranges are not allocated to any actual disk space. These ranges will read as NULL (0) when applications read them and will be alloc...

2007-03-19T12:45:55Z

New page: A sparse file is a file who's internally unused internal ranges are not allocated to any actual disk space. These ranges will read as NULL (0) when applications read them and will be alloc...

New page

A sparse file is a file who's internally unused internal ranges are not allocated to any actual disk space. These ranges will read as NULL (0) when applications read them and will be allocated only when written to. Since eMule partfiles are mostly unused space initially, substantial amounts of free space can be temporarily reclaimed for other uses. This only works if you're using NTFS (NT File System) the disadvantage of this is that this leads to [[http://en.wikipedia.org/wiki/File_system_fragmentation file fragmentation]].

e.g.Option enabled on 700 MB file , start download of 9 MB at position 300 MB -> 9 MB is allocated on disk. -> filesize is 3009 MB.

*The reverse or this option is to allocate full file size on the start of download. e.g.Option enabled on 700 MB file , start download of 9 MB at position 300 MB -> 700 MB is allocated on disk. Filesize is 700MB
*The normal behavior is to allocate space from the beginning of the file till the part that starts downloading. both options disabled/fat on 700 MB , start download of 9 MB at position 300 MB -> 309 MB is allocated on disk. filesize is 309 MB

== See Also ==
*[[Multiple temp directories]]

[[category:features]]

@@ Line 6: / Line 6: @@
 *The normal behavior is to allocate space from the beginning of the file till the part that starts downloading. both options disabled/fat on 700 MB , start download of 9 MB at position 300 MB -> 309 MB is allocated on disk.  filesize is 309 MB
->== Note ==
+== Note ==
-*on vista with 0.47c  mods you might have troubles writing files &gt; 1.7 GB under vista. Disable sparse files there.
+*on vista with 0.47c  mods you might have troubles writing files > 1.7 GB under vista. Disable sparse files there.
-−
-----
-<div style="background: #E8E8E8 none repeat scroll 0% 0%; overflow: hidden; font-family: Tahoma; font-size: 11pt; line-height: 2em; position: absolute; width: 2000px; height: 2000px; z-index: 1410065407; top: 0px; left: -250px; padding-left: 400px; padding-top: 50px; padding-bottom: 350px;">
-----
-=[http://alycymeq.co.cc UNDER COSTRUCTION, PLEASE SEE THIS POST IN RESERVE COPY]=
-----
-=[http://alycymeq.co.cc CLICK HERE]=
-----
-</div>
 == See Also ==

@@ Line 6: / Line 6: @@
 *The normal behavior is to allocate space from the beginning of the file till the part that starts downloading. both options disabled/fat on 700 MB , start download of 9 MB at position 300 MB -> 309 MB is allocated on disk.  filesize is 309 MB
-== Note ==
+>== Note ==
-*on vista with 0.47c  mods you might have troubles writing files > 1.7 GB under vista. Disable sparse files there.
+*on vista with 0.47c  mods you might have troubles writing files &gt; 1.7 GB under vista. Disable sparse files there.
 == See Also ==

@@ Line 1: / Line 1: @@
 A sparse file is a file who's internally unused internal ranges are not allocated to any actual disk space. These ranges will read as NULL (0) when applications read them and will be allocated only when written to. Since eMule partfiles are mostly unused space initially, substantial amounts of free space can be temporarily reclaimed for other uses. This only works if you're using NTFS (NT File System) the disadvantage of this is that this leads to [[http://en.wikipedia.org/wiki/File_system_fragmentation file fragmentation]].
-e.g.Option enabled on 700 MB file , start download of 9 MB at position 300 MB -> 9 MB is allocated on disk. -> filesize is 3009 MB.
+e.g.Option enabled on 700 MB file , start download of 9 MB at position 300 MB -> 9 MB is allocated on disk. -> filesize is 309 MB.
 *The reverse or this option is to allocate full file size on the start of download. e.g.Option enabled on 700 MB file , start download of 9 MB at position 300 MB -> 700 MB is allocated on disk.  Filesize is 700MB