Re: [Duplicity-talk] exclude lost+found . [SEC=UNCLASSIFIED]

[edgar . soldin]

On 10.07.2015 09:37, Eponymous - wrote:
> On Fri, Jul 10, 2015 at 5:46 AM,  <address@hidden> wrote:
>>
>>
>> Hi,
>>
>> Can someone advise what the correct format for excluding lost+found might
>> be please ?
>>
>> I keep getting 'Error accessing possibly locked file /backup/lost+found'
>> and thus the backup has 'Errors: 1' in the summary.
>>
>> currently trying :
>> duplicity --dry-run --encrypt-key=backup '--exclude=/backup/lost
>> +found' /backup scp://address@hidden:54321//backup/
>>
>> Output :
>> Local and Remote metadata are synchronized, no sync needed.
>> Last full backup date: Fri Jul 10 14:27:01 2015
>> Error accessing possibly locked file /backup/lost+found
>> --------------[ Backup Statistics ]--------------
>> StartTime 1436503247.49 (Fri Jul 10 14:40:47 2015)
>> EndTime 1436503247.64 (Fri Jul 10 14:40:47 2015)
>> ElapsedTime 0.14 (0.14 seconds)
>> SourceFiles 214
>> SourceFileSize 28016193 (26.7 MB)
>> NewFiles 5
>> NewFileSize 9800 (9.57 KB)
>> DeletedFiles 6
>> ChangedFiles 2
>> ChangedFileSize 600 (600 bytes)
>> ChangedDeltaSize 0 (0 bytes)
>> DeltaEntries 13
>> RawDeltaSize 0 (0 bytes)
>> TotalDestinationSizeChange 0 (0 bytes)
>> Errors 1
>> -------------------------------------------------
>>
>> Versions :
>> rpm -q duplicity
>> duplicity-0.6.24-2.1.4.x86_64
>>
>> opensuse 13.2
>>
>>
>>
>>
>> thanks
>>
>> Peter Hine
>> Senior Technical Support Engineer (Servers)
>> FCoA ITS
>> address@hidden
>>
>>
>>
>> **********************************************************************
>> The information contained in this e-mail (including any attachments)
>> is for the exclusive use of the addressee. If you are not the intended
>> recipient please notify the sender immediately and delete this e-mail.
>> It is noted that legal privilege is not waived because you have read
>> this e-mail.
>> **********************************************************************
>>
>>
>> _______________________________________________
>> Duplicity-talk mailing list
>> address@hidden
>> https://lists.nongnu.org/mailman/listinfo/duplicity-talk
> 
> 
> 
> Duplicity will attempt to scan the entire source directory and stat
> each item it comes across. It appears you are running as a user who
> doesn't have the permissions to stat lost+found and so even though
> you've explicitly excluded it, it will still throw an error.
> 
> Three ideas come to mind - neither of which might suit your needs:
> 
> 1) Run your backup as the root user.
> 2) Start using ACLs (http://www.vanemery.com/Linux/ACL/linux-acl.html
> - old but really good information) and create a new "backup" user or
> group and add a read ACL entry for the new user on lost+found.
> 3) Modify Duplicity to have a new option such as
> "--ignore-permissions-errors" which will allow it to continue and
> report success even if you can't access a file. This has the potential
> for hiding genuine issues though.
> 

this is a long standing issue. the proper solution though, implementation still 
pending, would be to first check if a path is excluded before doing any file 
operation on it. that'd would be your proper 3).

..ede/duply.net