I logged perhaps the original service request on this but must admit we haven’t tried it of late as have worked around the issue. From: gpfsug-discuss-bounces at spectrumscale.org [mailto:gpfsug-discuss-bounces at spectrumscale.org] On Behalf Of Knister, Aaron S. (GSFC-606.2)[COMPUTER SCIENCE CORP] Sent: Thursday, 23 November 2017 4:21 PM To: gpfsug-discuss at spectrumscale.org Subject: [gpfsug-discuss] tar sparse file data loss Somehow this nugget of joy (that’s most definitely sarcasm, this really sucks) slipped past my radar: http://www-01.ibm.com/support/docview.wss?uid=isg1IV96475 Anyone know if there’s a fix in the 4.1 stream? In my opinion this is 100% a tar bug as the APAR suggests but GPFS has implemented a workaround. See this post from the tar mailing list: https://www.mail-archive.com/bug-tar@gnu.org/msg04209.html It looks like the troublesome code may still exist upstream: http://git.savannah.gnu.org/cgit/tar.git/tree/src/sparse.c#n273 No better way to ensure you’ll hit a problem than to assume you won’t :) -Aaron -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://gpfsug.org/pipermail/gpfsug-discuss_gpfsug.org/attachments/20171123/9cfba7e8/attachment.html>