If you chomped line-ends as kennethk suggested, but things still look funny,

here's another one, typically encountered with Unix servers in a larger compute center:

Do check mount output and every mtab / fstab you can lay your hands on, both locally and on remote NFS servers: grep for a mount option like noatime or similar (note that Linux offers some fake-atime options between accurate atime and noatime).

Note that in such setups, there's a high likelihood of e.g. /sasdata and and /sasdata/it/development/ actually being different (NFS?) filesystems.
{"Millions of files and 5 TB" sounds like a slow and well-known scenario} (comment below)

Consider using _ as "filename", as it allows you to reuse your stat w/o going again all the way to file cache or blockbuffer. Depending on flux, it might be worthwhile to redirect find output to a file. Better yet fold the find into Perl proper, possibly doing a test with File::Find vs readdir. Assuming seek times are dominant and the system's under load, you might nearly half your number of seeks.

In reply to Re: stat on find output by jakobi
in thread stat on find output by hitesh_ofdoon

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.