I would suggest changing your create_entry function to look like this: 

sub create_entry {
    # If only two fields are present, the index must
    # be "expired" (rather than expiring.)
    $_[1] = 'expired' if @_ == 2;

    my ($tape_id, @rest) = @_;
    push (@{$tape_index{$tape_id}}, [$tape_id, @rest]);
}

[download]

The problem you're experiencing is that when you have a line like: 

 ST4910 (FROZEN)

[download]
you are only getting two fields in your hash. The tape_id, and "(FROZEN)" for the expired field. You then are searching on the "expired" key, which is not present. By changing your create_entry function to the above, both the "expired" and "expires" keys will be properly created.

In reply to Re: ^7 Parse backup log by Belgarion
in thread Parse backup log by mrbbq

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.