sk suggested checking with ulimit
ettest:/usr/local/tmp $ulimit
unlimited
Lying scum. As BrowserUK pointed out the failures are happening around the 4GB mark.
I wrote a bit of code to test seeking and reading:
#!/usr/bin/perl
# try seek to get around my problems with 11G file
# $have value derived from the total size of the splits I've extracted
$have = 4912152576;
open BIG, "<QAPI.0.log" or die "cannot open QAPI ... $@";
$ret = sysseek BIG, $have, 0;
print STDERR "sysseeked to $ret \n";
$ret = sysread BIG, $data, 1024;
print STDERR "sysread $ret\n";
print $data;
And that fails.
Folks,
Thank You for the suggestions. I'm going to try to compress(1) the file. If that fails I'm going to scrub it and redo the process and regenerate the log as a series of smaller files. I can't take up any more of my employer's time on this one off problem.
Now to recreate it at home...
Be Appropriate && Follow Your Curiosity
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: |
| & | | & |
| < | | < |
| > | | > |
| [ | | [ |
| ] | | ] |
Link using PerlMonks shortcuts! What shortcuts can I use for linking?
See Writeup Formatting Tips and other pages linked from there for more info.