[Bug 13496] New: lseek returned -1, not 2147483648: Invalid argument (22)

samba-bugs at samba.org samba-bugs at samba.org
Fri Jun 29 12:52:08 UTC 2018


            Bug ID: 13496
           Summary: lseek returned -1, not 2147483648: Invalid argument
           Product: rsync
           Version: 3.1.2
          Hardware: Sparc
                OS: Solaris
            Status: NEW
          Severity: normal
          Priority: P5
         Component: core
          Assignee: wayned at samba.org
          Reporter: samba.pkoch at dfgh.net
        QA Contact: rsync-qa at samba.org

Dear rsync experts:

We are rsyncing our file servers /home-directory with approx 1TB data every
night by using the following command:

rsync --password-file=/etc/backup.pass -aHA \
      --link-dest=../<backup-dir from last night> \
      /home/ v480 at backup::v480/home/<new backup-dir>

The sending server is a Sun machine running Solaris 10, the receiving
machine runs Slackware Linux 14.2.

For a long time we were using rsync 3.0.8 on the Solaris 10 machine and
rsync 3.1.2 on the backup.server and everything was fine.

Two month ago we decided to rsync ACLs as well and this forced us to
upgrade rsync on the Solaris machine to a newer version. I decided that
using the exact same version on both machines would be the best
situation and so I compiled rsync 3.1.2 on the Solaris machine with

sh configure --prefix=/usr; make; make install

Again everything was working fine (including ACLs) but since 3 days
rsync stops every night with the following error message:

rsync: lseek returned -1, not 2147483648: Invalid argument (22)
rsync error: error in file IO (code 11) at fileio.c(249) [sender=3.1.2]

I suspected a largefile-problem, but none of our files is of size >2GB.

Sometimes the rsync-command is successfull when we restart it
in the morning. SOmetimes the problem still happens when the command
is restarted and we then rsync each subdirectoy separately.

When using the verbose-option we see that rsync fails at different
locations within the file tree.

It seems to me that some kind of 2GB-limit is reached. I looked into
the source code to find out why rsync is doing a lseek(2GB). But
this gave me no ideas about what's happening. errno=22 indicates that
lseek was called with invalid parameters. But rsync --versions shows:

rsync  version 3.1.2  protocol version 31
Copyright (C) 1996-2015 by Andrew Tridgell, Wayne Davison, and others.
Web site: http://rsync.samba.org/
    64-bit files, 64-bit inums, 32-bit timestamps, 64-bit long ints,
    socketpairs, hardlinks, symlinks, IPv6, batchfiles, inplace,
    append, ACLs, xattrs, iconv, no symtimes, no prealloc

So we do have largefile support.

The only way to reproduce this problem is to rsync the complete 1TB.
Is there any other debugging information that I can print in line 249
of fileio.c and that might help you to diagnose the problem.

Kind regards

Peter Koch

You are receiving this mail because:
You are the QA Contact for the bug.

More information about the rsync mailing list