https://bugzilla.samba.org/show_bug.cgi?id=13496
Peter Koch <samba.pk...@dfgh.net> changed: What |Removed |Added ---------------------------------------------------------------------------- Resolution|--- |INVALID Status|NEW |RESOLVED --- Comment #2 from Peter Koch <samba.pk...@dfgh.net> --- (In reply to Peter Koch from comment #0) Dear readers: Problem has been solved, Here's what was going on: 1: I was (partly) wrong when stating that there were no files with size >2GB in our /home-directory 2: Both 32bit and 64bit executables on Solaris 10 do support largefiles. So does rsync. 3: One of our administrators created a NFS link from our mailserver into our fileservers /home-directory and for some reason forced the Solaris machine to use NFS version 2 4: 3 day ago a file of size>2GB was created on our mailserver. rsync detected this file within the /home-directory. It had size >2GB but due to the NFS version 2 limitation only the first 2GB of this file were readable. So lseek(2GB) returned -1 Now I'm using rsync -aHAx instead of rsync -aHA and everything works fine again Thank you all for this wonderfull software Peter -- You are receiving this mail because: You are the QA Contact for the bug. -- Please use reply-all for most replies to avoid omitting the mailing list. To unsubscribe or change options: https://lists.samba.org/mailman/listinfo/rsync Before posting, read: http://www.catb.org/~esr/faqs/smart-questions.html