On Thu, Jul 21, 2005 at 11:25:08AM -0400, LaValley, Brian E enlightened us: > Do you usually get lots of tar output when running amrecover's extract? > > > tar: ./forrest/nsmail/people.sbd/.Bob.summary: invalid sparse archive member > tar: Skipping to next header > tar: ./forrest/nsmail/people.sbd/.MIKE.summary: invalid sparse archive > member > tar: Skipping to next header > tar: ./forrest/nsmail/people.sbd/.jason.summary: invalid sparse archive > member > tar: Skipping to next header > tar: ./forrest/nsmail/people.sbd/.karl.summary: invalid sparse archive > member > tar: Skipping to next header > tar: ./forrest/nsmail/people.sbd/.yabu.summary: invalid sparse archive > member > tar: Skipping to next header > tar: > ./forrest/public_html/cadencejpgs/A1652_PRE_DR/SM_decoding/TM_for_A1652_gaf_ > Aug_3_04.ppt: invalid sparse archive member > tar: Skipping to next header > tar: ./gregs/.netscape/cert7.db: invalid sparse archive member > tar: Skipping to next header > tar: ./gregs/.netscape/history.dat: invalid sparse archive member > tar: Skipping to next header > tar: ./gregs/.netscape/key3.db: invalid sparse archive member > tar: Skipping to next header > tar: ./gregs/.netscape/secmodule.db: invalid sparse archive member
Let me guess, tar 1.14? See http://www.amanda.org/docs/faq.html#id2554919 -- Matt Hyclak Department of Mathematics Department of Social Work Ohio University (740) 593-1263
