Hi again, Georg Graf wrote: > Hi! > > Jean-Pierre André wrote: > >> Hi Georg, >> >> What kind of file were you saving ? How big, how >> sparse (how many holes) ? >> > very big files. 20 GB. Many holes. vmware disk images. > > >> Were you saving a *single* file ? >> > well, yes and no. NO, because I used rsync -a. > YES, because it happened within a single file. > > >> How do you know there were lseeks beyond the end >> of the file ? >> > I was strace'ing the rsync server side process. And is'nt that the way > sparse files are brought to life? >
Ok, this is normal for a sparse file. > Sorry, this is not possible at the moment. The file being transferred as > I canceled the job is 20GB when using "ls -l", but only 1.4GB when using > "du". The worst case (fragments smaller than 4K and more than 8K apart) would mean 1.4GB/4K = 350000 fragments. Your situation is probably not that bad, but no doubt ntfs-3g will choke before. I have no magic solution right now. Have you tried compressing the file before transferring ? Regards Jean-Pierre ------------------------------------------------------------------------------ The Planet: dedicated and managed hosting, cloud storage, colocation Stay online with enterprise data centers and the best network in the business Choose flexible plans and management services without long-term contracts Personal 24x7 support from experience hosting pros just a phone call away. http://p.sf.net/sfu/theplanet-com _______________________________________________ ntfs-3g-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/ntfs-3g-devel
