[arch-general] adb backup broken named pipe

Pascal patatetom at gmail.com
Fri May 17 09:59:09 UTC 2019


*(sorry, bad Ctrl-C Ctrl-V)*
yes, but I have two constraints, the second being directly related to the
first : limited storage space and access to data backed up through
archivemount that does not support the android backup format.

Le ven. 17 mai 2019 à 11:49, Pascal <patatetom at gmail.com> a écrit :

> Indeed, but it has to face two constraints, the second being directly
> related to the first : limited storage space and access to the data backed
> up through archivemount which does not support the android backup format.
>
> Le ven. 17 mai 2019 à 10:32, Ralph Corderoy <ralph at inputplus.co.uk> a
> écrit :
>
>> Hi Pascal,
>>
>> > I still have a slight problem because the tar command ends with an
>> error :
>> > *(the same error is also present with adb, printf and tail).*
>> ..
>> > $ python3 adbackup.py > /tmp/mybackup.tgz
>> > $ tar tvzf /tmp/mybackup.tgz
>> > ... all my files are here :-)
>> > gzip: stdin: unexpected end of file
>> > tar: Child returned status 1
>> > tar: Error is not recoverable: exiting now
>>
>> Why not keep the non-tar file long term and convert it to gzip'd tar
>> format when required.  That way you'll be able to improve your
>> conversion over time, and not break if adb changes its format.  That
>> breakage could go unnoticed until it's too late to re-backup the data.
>>
>>     (printf ... && cat foo.ab) | tar ...
>>
>> --
>> Cheers, Ralph.
>>
>


More information about the arch-general mailing list