Hi Jens, Well, that's the thing. We can't get rid of the fallocate error regardless of how we set fallocate= in the job file. We've tried 0,1,none,posix and keep (which seems to be invalid now) and we ALWAYS get the fallocate error. Sometimes the job continues to run, but the output file is only created at zero byte length.
Regards. Mario Carino AIG Database Administrator IT Infrastructure | AIG Property Casualty 5 Wood Hollow Rd, 3rd Floor, Parsippany, NJ 07054 Tel +1 817 490-7145 | Cell +1 551 655-1443 | Direct +1 973 331-8558 (Mon/Wed/Thu) [email protected] | www.aig.com -----Original Message----- From: Jens Axboe [mailto:[email protected]] Sent: Thursday, April 10, 2014 10:00 AM To: Carino, Mario; [email protected] Subject: Re: fio on AIX - fallocate error On 2014-04-09 20:52, Carino, Mario wrote: > Hi. > We're trying to run fio 2.1.7 on AIX 6 and we can't seem to eliminate these > errors: > > fio: posix_fallocate fails: Invalid argument This one you can ignore, or you can get rid of it by adding: fallocate=none to the job file. > fio: pid=0, err=22/file:filesetup.c:418, func=invalidate_cache, > error=Invalid argument Fio should probably just ignore these flush-cache warnings and continue on, it's not really a fatal condition. I have attached a patch for you, can you apply that and give it a go? > we always get one or the other. It doesn't matter too much what > command we run, what options, etc. We saw a web page which indicates > that fio requires an Asynch IO package to be installed and running on > AIX. Is that correct? We're > trying to find out if we have it installed on our test box. You'd get a different error if that was your issue. > (We're lowly non-root > DBA's so getting anything done requires a committee.) Isn't that always the case with AIX? :-) -- Jens Axboe -- To unsubscribe from this list: send the line "unsubscribe fio" in the body of a message to [email protected] More majordomo info at http://vger.kernel.org/majordomo-info.html
