Please note that this is NOT a place to ask questions or report bugs. This comment system is only intended for users to share tips and documentation additions concerning particular document. Please report bugs to https://bugs.launchpad.net/percona-project/+filebug and ask general questions in maillist Percona-discussions
I encountered problems using nc (netcat) to do streaming over-the-network backups where tar would report “Unexpected EOF” errors after just a few seconds of copying. Switching to netrw solved the EOF issues for our RHEL5 gigabit deployment.
Ammon Lauritzen, 2009/07/17 13:31
Standard tar has an inherent limit of 2gb per file, so streaming backups will quite possibly quit early if your ibdata is very large.
Yasufumi Kinoshita, 2009/08/08 18:48
tar format's limit is 64GB per file logically. anyway we need to implement the another format for the very large files…
David Sparks, 2009/09/15 14:40
Is this likely to be problematic then?
-rw-rw—- 1 mysql mysql 186G Sep 15 14:38 ibdata1
-rw-rw—- 1 mysql mysql 85G Sep 15 14:38 XXX.ibd
-rw-rw—- 1 mysql mysql 109G Sep 15 14:38 YYY.ibd
-rw-rw—- 1 mysql mysql 287G Sep 15 14:38 ZZZ.ibd
gzip: stdin: invalid compressed data–format violated
tar: Unexpected EOF in archive
tar: Unexpected EOF in archive
tar: Error is not recoverable: exiting now
$ tar xfziv ~/backup_2010-03-01_19h05m02s.tar.gz
any idea why we see that error? notice the options I am using..
percona-xtrabackup/innobackupex.txt · Last modified: 2010/03/21 06:56 (external edit)
Please report bugs to https://bugs.launchpad.net/percona-project/+filebug and ask general questions in maillist Percona-discussions
Discussion
I encountered problems using nc (netcat) to do streaming over-the-network backups where tar would report “Unexpected EOF” errors after just a few seconds of copying. Switching to netrw solved the EOF issues for our RHEL5 gigabit deployment.
Standard tar has an inherent limit of 2gb per file, so streaming backups will quite possibly quit early if your ibdata is very large.
tar format's limit is 64GB per file logically. anyway we need to implement the another format for the very large files…
Is this likely to be problematic then?
-rw-rw—- 1 mysql mysql 186G Sep 15 14:38 ibdata1
-rw-rw—- 1 mysql mysql 85G Sep 15 14:38 XXX.ibd -rw-rw—- 1 mysql mysql 109G Sep 15 14:38 YYY.ibd -rw-rw—- 1 mysql mysql 287G Sep 15 14:38 ZZZ.ibd
nextgen/FIELD.ibd nextgen/field_types.ibd nextgen/FIELD_VALUE.ibd
gzip: stdin: invalid compressed data–format violated tar: Unexpected EOF in archive tar: Unexpected EOF in archive tar: Error is not recoverable: exiting now $ tar xfziv ~/backup_2010-03-01_19h05m02s.tar.gz
any idea why we see that error? notice the options I am using..