If that would work, the only difference would probably be that when restoring, the deleted files between levels are restore too. No difference for incremental backups as --listed-incremental is still used. So when the restore of that level fails, it is restarted without --incremental related options. It is a possible workaround.
A possible solution would be to not wrap binaries any more and provide similar functionalities from python code, so the code would also be more portable. I'd rather invest time on binary dependency removal rather than use other binaries. Just my opinion. On Mon, May 23, 2016 at 6:03 PM, Dieterly, Deklan <deklan.diete...@hpe.com> wrote: > Then it would not be an incremental backup/restore. This problem arises > when doing incremental backup and restores. > -- > Deklan Dieterly > > Senior Systems Software Engineer > HPE > > > > > From: Fausto Marzi <fausto.ma...@gmail.com> > Reply-To: "OpenStack Development Mailing List (not for usage questions)" > <openstack-dev@lists.openstack.org> > Date: Wednesday, May 18, 2016 at 5:22 AM > To: "OpenStack Development Mailing List (not for usage questions)" > <openstack-dev@lists.openstack.org> > Subject: Re: [openstack-dev] [Freezer] Replace Gnu Tar with DAR > > > >Hi Deklan, > > > >what happen if the extract is executed without --listed-incremental or > >--incremental options? > > > > > >Does the issue still happen? > > > > > >Thanks, > > > >Fausto > > > > > >On Sat, May 14, 2016 at 12:56 AM, Dieterly, Deklan > ><deklan.diete...@hpe.com> wrote: > > > >When using incremental backups, tar will not handle removing a dir and > >then renaming another dir to the removed dir. > > > > > >dek@dek-HP-Z620-Workstation:~/backup-test$ tar --extract > >--listed-incrementa=/dev/null --file backup.2.tar > >tar: Cannot rename Œbackup/dir1¹ to Œbackup/dir2¹: Directory not empty > >tar: Exiting with failure status due to previous errors > > > > > > > >Here are the steps to reproduce. > > > > 1845 mkdir backup > > 1846 mkdir backup/dir1 > > 1847 mkdir backup/dir2 > > 1848 echo "aa" > backup/dir1/dir1-file1 > > 1849 echo "aa" > backup/dir2/dir2-file1 > > 1852 tar --create --file=backup.tar --listed-incremental=./listed-incr > >backup > > 1854 rm -rf backup/dir2 > > 1855 mv backup/dir1 backup/dir2 > > 1856 tar --create --file=backup.2.tar --listed-incremental=./listed-incr > >backup > > 1859 tar --extract --listed-incrementa=/dev/null --file backup.tar > > 1861 tar --extract --listed-incrementa=/dev/null --file backup.2.tar > > > > > >This seems to be a well known, long-standing issue with tar. > >-- > >Deklan Dieterly > > > >Senior Systems Software Engineer > >HPE > > > > > > > > > >On 5/13/16, 4:33 PM, "Fox, Kevin M" <kevin....@pnnl.gov> wrote: > > > >>Whats the issue? > >>________________________________________ > >>From: Dieterly, Deklan [deklan.diete...@hpe.com] > >>Sent: Friday, May 13, 2016 3:07 PM > >>To: openstack-dev@lists.openstack.org > >>Subject: [openstack-dev] [Freezer] Replace Gnu Tar with DAR > >> > >>Does anybody see any issues if Freezer used DAR instead of Gnu Tar? DAR > >>seems to handle a particular use case that Freezer has while Gnu Tar does > >>not. > >>-- > >>Deklan Dieterly > >> > >>Senior Systems Software Engineer > >>HPE > >> > >> > >>_________________________________________________________________________ > >>_ > >>OpenStack Development Mailing List (not for usage questions) > >>Unsubscribe: > >openstack-dev-requ...@lists.openstack.org?subject:unsubscribe > ><http://openstack-dev-requ...@lists.openstack.org?subject:unsubscribe> > >>http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev > >> > >>_________________________________________________________________________ > >>_ > >>OpenStack Development Mailing List (not for usage questions) > >>Unsubscribe: > >openstack-dev-requ...@lists.openstack.org?subject:unsubscribe > ><http://openstack-dev-requ...@lists.openstack.org?subject:unsubscribe> > >>http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev > > > > > >__________________________________________________________________________ > >OpenStack Development Mailing List (not for usage questions) > >Unsubscribe: > >openstack-dev-requ...@lists.openstack.org?subject:unsubscribe > ><http://openstack-dev-requ...@lists.openstack.org?subject:unsubscribe> > >http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev > > > > > > > > > > > > __________________________________________________________________________ > OpenStack Development Mailing List (not for usage questions) > Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev >
__________________________________________________________________________ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
