IMHO in your code: 
    #Replace / with \
    (my $fn = $File::Find::name) =~ tr#/#\\#;
    #Replace gpfs_data with nas\rdds
    $fn =~ s/gpfs_data/nas\\rdds/;
    #Push into the @allpathlisting array any paths matching the patter
+n.
    push @allpathlisting, $fn if /[IPDLMY]\d{8}$/; 
    # How big is it?
    my $fsize = (stat($fn))[7];

[download]
You modify the original file name twice, and only then, you stat the modified file name.
so, if your original path /some/path/gpfs_data/some_file.ext
you stat: \some\path\nas\rdds\some_file.ext
That's a copletley different file, that probably doesn't exist
Shouldn't you stat the file before modifying?

In reply to Re: File::Find stat question by igoryonya
in thread File::Find stat question by Anonymous Monk

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.