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? >> Today morning the process just ate 100% CPU and no writing was performed. >> > > It could be useful if you can tell us how many fragments > there are in the (aborted) target file : > > # get the inode number > ls -i <file> > # umount the device > umount <device> > # count the lines in the parameters > ntfsinfo -vi <inode number> <device> | wc -l 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". thanks, george -- Mag. Georg Graf Celix Hard & Software Vertriebs Gmbh http://www.celix.at/ Gumpendorferstrasse 59-61/2/1 A-1060 Wien Tel: +43 1 503 6111 Fax: +43 1 503 6111 9 ------------------------------------------------------------------------------ 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
