AFAICT from a quick look at the source and some experimentation, PerlIO::gzip doesn't do integrity checking, so if you can't avoid encountering corrupt files occasionally, you'll probably have to resort to an external tool (even though this is of course suboptimal from a performance point of view...). For example, the good old gzip/gunzip program has a -t/--test option to perform integrity checking.

Update: you could also try IO::Uncompress::Gunzip intead of the PerlIO layer. It has a Strict option which performs a number of integrity checks...

In reply to Re: PerlIO::gzip - Handling Corrupt tar file by almut
in thread PerlIO::gzip - Handling Corrupt tar file by snra_perl

Title:
Use:  <p> text here (a paragraph) </p>
and:  <code> code here </code>
to format your post, it's "PerlMonks-approved HTML":


  • Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
  • Titles consisting of a single word are discouraged, and in most cases are disallowed outright.
  • Read Where should I post X? if you're not absolutely sure you're posting in the right place.
  • Please read these before you post! —
  • Posts may use any of the Perl Monks Approved HTML tags:
    a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, details, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, summary, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
  • You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
            For:     Use:
    & &amp;
    < &lt;
    > &gt;
    [ &#91;
    ] &#93;
  • Link using PerlMonks shortcuts! What shortcuts can I use for linking?
  • See Writeup Formatting Tips and other pages linked from there for more info.