search for: 3211264

...c21a8baf.vmss -rwxrwxrwx 1 root root 8684 Jun 24 20:18 WinXPPro.nvram -rwxrwxrwx 1 root root 2145255424 Jun 24 20:12 WinXPPro-s001.vmdk -rwxrwxrwx 1 root root 2146238464 Jun 24 20:33 WinXPPro-s002.vmdk -rwxrwxrwx 1 root root 2146631680 Jun 24 20:25 WinXPPro-s003.vmdk -rwxrwxrwx 1 root root 3211264 Jun 24 20:12 WinXPPro-s004.vmdk -rwxrwxrwx 1 root root 2106261504 Jun 24 20:18 WinXPPro-s005.vmdk -rwxrwxrwx 1 root root 2146697216 Jun 24 20:00 WinXPPro-s006.vmdk -rwxrwxrwx 1 root root 2162688 Jun 24 20:27 WinXPPro-s007.vmdk -rwxrwxrwx 1 root root 2146107392 Jun 24 20:06 WinXPPro-s008.vmdk -rw...

...684 Jun 24 20:18 WinXPPro.nvram -rw----r-x 1 libvirt-qemu kvm 2145255424 Jun 24 20:12 WinXPPro-s001.vmdk -rw----r-x 1 libvirt-qemu kvm 2146238464 Jun 24 20:33 WinXPPro-s002.vmdk -rw----r-x 1 libvirt-qemu kvm 2146631680 Jun 24 20:25 WinXPPro-s003.vmdk -rw----r-x 1 libvirt-qemu kvm 3211264 Jun 24 20:12 WinXPPro-s004.vmdk -rw----r-x 1 libvirt-qemu kvm 2106261504 Jun 24 20:18 WinXPPro-s005.vmdk -rw----r-x 1 libvirt-qemu kvm 2146697216 Jun 24 20:00 WinXPPro-s006.vmdk -rw----r-x 1 libvirt-qemu kvm 2162688 Jun 24 20:27 WinXPPro-s007.vmdk -rw----r-x 1 libvirt-qemu kvm 21...

...2 ql=0 pa=0 f: > > > htb*c10080 m=2 t=-45721 c=12161 pq=0 df=1998848 ql=0 pa=0 f: > > > htb*c10091 m=2 t=163300 c=46975 pq=0 df=44982272 ql=0 pa=0 f: > > > htb*c10109 m=2 t=168099 c=48174 pq=0 df=60000000 ql=0 pa=0 f: > > > htb*c10118 m=2 t=163300 c=46975 pq=0 df=3211264 ql=0 pa=0 f: > > > htb*c10081 m=2 t=-68763 c=8738 pq=0 df=229376 ql=0 pa=0 f: > > > htb*c10090 m=2 t=163300 c=46975 pq=0 df=60000000 ql=0 pa=0 f: > > > htb*c10108 m=2 t=168099 c=28187 pq=0 df=60000000 ql=0 pa=0 f: > > > htb*c10119 m=2 t=-203578 c=-21102 pq=0 df=5...

When I use the preallocate patch and create a 77GB file using the function I get a CPU spike on the server-side. The spike lasts about 20 minutes and uses about 20%-25% of the cpu associated with the rsync instance creating the file. The spike is directly linked to the time it takes to create the file. I compiled rsync using cygwin CVS. I initially suspected the implementation of

https://bugzilla.samba.org/show_bug.cgi?id=13317 Bug ID: 13317 Summary: rsync returns success when target filesystem is full Product: rsync Version: 3.1.2 Hardware: x64 OS: FreeBSD Status: NEW Severity: major Priority: P5 Component: core Assignee: wayned at samba.org