The explanation why this bug affects only 1.6 the following.
The difference between the ways of tar streaming in 1.6 and 2.0 is 1.6 use external "tar4ibd" command which is invoked from "start_ibbackup" subroutine in innobackupex while 2.0 use libarchive functions("archive_entry_new()", "archive_entry_set_pathname()" from "stream_open()" for creating "file" in stream and "archive_write_data()" from "stream_write()" for writing data to stream) to work with tar stream.
I think tar from "libtar-1.2.11" just converts absolute path to relative because innobackupex pass absolute path of ibdata file to tar4ibd but we get relative path in the output stream. As we patch tar for using it in innobackupex the solution may be in including this bug fixing in tar4ibd_libtar-1.2.11.patch.
The explanation why this bug affects only 1.6 the following.
The difference between the ways of tar streaming in 1.6 and 2.0 is 1.6 use external "tar4ibd" command which is invoked from "start_ibbackup" subroutine in innobackupex while 2.0 use libarchive functions( "archive_ entry_new( )", "archive_ entry_set_ pathname( )" from "stream_open()" for creating "file" in stream and "archive_ write_data( )" from "stream_write()" for writing data to stream) to work with tar stream.
I think tar from "libtar-1.2.11" just converts absolute path to relative because innobackupex pass absolute path of ibdata file to tar4ibd but we get relative path in the output stream. As we patch tar for using it in innobackupex the solution may be in including this bug fixing in tar4ibd_ libtar- 1.2.11. patch.