[Bug 11646] New: rsync incapable of copying corrupted filesystem

samba-bugs at samba.org samba-bugs at samba.org
Mon Dec 21 17:59:10 UTC 2015


https://bugzilla.samba.org/show_bug.cgi?id=11646

            Bug ID: 11646
           Summary: rsync incapable of copying corrupted filesystem
           Product: rsync
           Version: 3.1.1
          Hardware: All
                OS: All
            Status: NEW
          Severity: normal
          Priority: P5
         Component: core
          Assignee: wayned at samba.org
          Reporter: arekm at maven.pl
        QA Contact: rsync-qa at samba.org

I'm trying to backup corrupted xfs filesystem (that cannot be repaired due to
bugs in xfs_repair) on linux 4.3.0

Anyway linux kernel is providing information about dirs and files for this
filesystem. Unfortunately some data is causing rsync to fail at assertion.

IMO rsync should be able to deal with anything linux kernel is providing to
userspace. Thus this bugreport.

cd /mnt/storage4/snapshots/blade3/
rsync -e ssh -avvvvvvvPH * root at host:/dest/snapshots/blade3/

[sender] pushing local filters for
/mnt/storage4/snapshots/blade3/daily.1/usr/bin/
[sender] flist start=58089, used=2, low=0, high=0
[sender] i=58089 <NULL> daily.1/usr/bin/ mode=040755 len=12,288 uid=0 gid=0
flags=4
[sender] i=58090 <NULL> daily.1/usr/bin/ mode=040755 len=12,288 uid=0 gid=0
flags=14
send_files(56588, daily.1/usr/bin)
recv_generator(daily.1/usr/bin,56589)
touch_up_dirs: daily.1/usr/bin (9080)
recv_files(daily.1/usr/bin)
[receiver] receiving flist for dir 9580
[generator] receiving flist for dir 9580
received 2 names
removing duplicate name daily.1/usr/bin from file list (57337)
[generator] flist start=57336, used=2, low=0, high=0
[generator] i=57336 3 daily.1/usr/bin/ mode=040755 len=12288 uid=0 gid=0
flags=4
[generator] i=57337   mode=00 len=1 uid=0 gid=0 flags=0
recv_file_list done
recv_generator(daily.1/usr/bin,56591)
rsync: exclude.c:614: change_local_filter_dir: Assertion `dir_depth < 4096/2+1'
failed.
Aborted

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



More information about the rsync mailing list