Hi Georg, Georg Graf wrote: > Hi folks, > > This weekend I was trying to archive vmware system images from disk to > an external 1 TB usb drive (ntfs-3g). Because auf space issues, I used > rsync --sparse to save space on my external (ntfs) file system. >
What kind of file were you saving ? How big, how sparse (how many holes) ? > When I left the office on friday, mount.ntfs-3g was running with lots of > cpu load (lots of "lseek" beyond the end of the file being written), > iostat showed me some 5MB/sec write throuput, which is not much, but I > can live with. > Were you saving a *single* file ? How do you know there were lseeks beyond the end of the file ? > 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 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
