[Bug 45615] "Large Files not supported" with 64-bit build

2017-01-10 Thread Dennis Clarke
re: https://bz.apache.org/bugzilla/show_bug.cgi?id=45615 I think it best to follow up here as per suggestions by Yann and Rainer wherein I can run further tests and experiments to determine what is happening here in these Niagara class systems. Firstly, sorry for awaking what seems like a long

Re: [Bug 45615] "Large Files not supported" with 64-bit build

2017-01-10 Thread Yann Ylavic
On Tue, Jan 10, 2017 at 1:36 PM, Dennis Clarke wrote: > > re: https://bz.apache.org/bugzilla/show_bug.cgi?id=45615 > re: long running (blocking?) apr_skiplist test. First, is it this test that takes a huge time to complete or was it the same for the previous tests too (and which ones)? > > As f

Re: [Bug 45615] "Large Files not supported" with 64-bit build

2017-01-10 Thread Rainer Jung
Hi Dennis, Am 10.01.2017 um 13:36 schrieb Dennis Clarke: re: https://bz.apache.org/bugzilla/show_bug.cgi?id=45615 I think it best to follow up here as per suggestions by Yann and Rainer wherein I can run further tests and experiments to determine what is happening here in these Niagara class s

Re: [Bug 45615] "Large Files not supported" with 64-bit build

2017-01-10 Thread Dennis Clarke
On 01/10/2017 12:57 PM, Yann Ylavic wrote: On Tue, Jan 10, 2017 at 1:36 PM, Dennis Clarke wrote: re: https://bz.apache.org/bugzilla/show_bug.cgi?id=45615 re: long running (blocking?) apr_skiplist test. I think we can close the bug about Large File Support and make a note that this is a po

Re: [Bug 45615] "Large Files not supported" with 64-bit build

2017-01-10 Thread Dennis Clarke
On 01/10/2017 01:12 PM, Rainer Jung wrote: Hi Dennis, Good day fine Sir. Firstly, sorry for awaking what seems like a long dead cold bug but it really isn't a "Large Files not supported" bug as opposed to just a message that needs to be tweaked. Indeed yes this is a 64 bit build and so off

Re: [Bug 45615] "Large Files not supported" with 64-bit build

2017-01-10 Thread Yann Ylavic
On Tue, Jan 10, 2017 at 6:50 PM, Dennis Clarke wrote: >> >> Could you strace (truss?) a simple main() that calls rand() to confirm? > > Even better, Dtrace. > > Regardless I am juggling a few things and will get right on this. Thanks for investigating. Also, when at this, could you please provid

Re: [Bug 45615] "Large Files not supported" with 64-bit build

2017-01-10 Thread Dennis Clarke
On 01/10/2017 06:03 PM, Yann Ylavic wrote: On Tue, Jan 10, 2017 at 6:50 PM, Dennis Clarke wrote: Could you strace (truss?) a simple main() that calls rand() to confirm? Even better, Dtrace. Regardless I am juggling a few things and will get right on this. Thanks for investigating. Also,

Re: [Bug 45615] "Large Files not supported" with 64-bit build

2017-01-10 Thread Dennis Clarke
On 01/10/2017 06:03 PM, Yann Ylavic wrote: On Tue, Jan 10, 2017 at 6:50 PM, Dennis Clarke wrote: Could you strace (truss?) a simple main() that calls rand() to confirm? Even better, Dtrace. Regardless I am juggling a few things and will get right on this. Thanks for investigating. Also,

Re: [Bug 45615] "Large Files not supported" with 64-bit build

2017-01-10 Thread Dennis Clarke
On 01/10/2017 06:03 PM, Yann Ylavic wrote: On Tue, Jan 10, 2017 at 6:50 PM, Dennis Clarke wrote: Could you strace (truss?) a simple main() that calls rand() to confirm? Even better, Dtrace. Regardless I am juggling a few things and will get right on this. Thanks for investigating. Also,

Re: [Bug 45615] "Large Files not supported" with 64-bit build

2017-01-10 Thread Yann Ylavic
On Tue, Jan 10, 2017 at 9:45 PM, Dennis Clarke wrote: > On 01/10/2017 06:03 PM, Yann Ylavic wrote: >> >> On Tue, Jan 10, 2017 at 6:50 PM, Dennis Clarke >> wrote: Could you strace (truss?) a simple main() that calls rand() to confirm? >>> >>> >>> Even better, Dtrace. >>> >>> Regardl

Re: [Bug 45615] "Large Files not supported" with 64-bit build

2017-01-10 Thread Dennis Clarke
Thanks Dennis for the follow up. /dev/urandom is the default (if existing), so if you don't ./configure --with-devrandom explicitly it should work too. Well clearly we found the problem and here is some offensive performance data to reveal the horrible truth : node000 $ /usr/bin/time -p dd