reiserfs, but it gives me no problem with either SETI and QMC.
Well, the immediate syncing is a new feature, currently probably unique to E@h. ReiserFS is rather unusual, in fact I have not used it for years (and not tested the App on this); this might be the reason for the problems you see. Try to switch off syncing.
BM
I'm also using reiserfs and the next WU that gets downloaded will be crunched by the 4.14 app, so we might see if I get this error too.
Btw, Bernd, did you read my report about a lot of errors with the 4.09 app on a system under heavy load in the 4.09 thread? Since the code didn't change so much, this might still be relevant with 4.14.
cu,
Michael
I'm using ReiserFs (it used to be Suse's default FS some time ago IIRC) without any problem so far with 4.14 on one host. So it's not a general ReiserFS problem .
reiserfs, but it gives me no problem with either SETI and QMC.
Well, the immediate syncing is a new feature, currently probably unique to E@h. ReiserFS is rather unusual, in fact I have not used it for years (and not tested the App on this); this might be the reason for the problems you see. Try to switch off syncing.
BM
I'm also using reiserfs and the next WU that gets downloaded will be crunched by the 4.14 app, so we might see if I get this error too.
Btw, Bernd, did you read my report about a lot of errors with the 4.09 app on a system under heavy load in the 4.09 thread? Since the code didn't change so much, this might still be relevant with 4.14.
cu,
Michael
I'm using ReiserFs (it used to be Suse's default FS some time ago IIRC) without any problem so far with 4.14 on one host. So it's not a general ReiserFS problem .
CU
H-B
Same here. I have ReiserFS installed on several machines. Two are currently running, happily crunching away with the Einstein 4.14 app. So far, no problems at all.
Bernd, did you read my report about a lot of errors with the 4.09 app on a system under heavy load in the 4.09 thread? Since the code didn't change so much, this might still be relevant with 4.14.
I read it. The signal handler used in 4.14 is supposed to give some more information about what's happening there. Actually I'm hoping this error occurs with a 4.14 App. Maybe you can help reproduce it?
BM
While running one 4.09 and one 4.12 WU, I tried really hard to reproduce the error, but without luck. I managed to reach an average 1 minute load of about 12 and system again was barely responsive sometimes. But responsiveness was better than last time when the errors occurred.
Maybe I must concentrate on disk I/O on the reiserfs, where the BOINC folder is located and not generally shared over all disks. I'll give this another try, probably at the weekend.
I started 87897850 with 4.09, but finished it with 4.14. It ran and validated successfully, and this system runs reiserfs as well. The time dropped noticeably from 4.09 as well.
Hope things get sorted out fast so a new official GNU/Linux app can come out soon, the linux rig that used to be #2 has dropped to #19 since S5R3 started, linux users have taken a serious RAC drop with 4.02.
The performance of 4.12/4.14 is beautiful, my xeon reached #80 in the top hosts list today. Doesnt sound very impressive maybe, but considered its only a single socket dual core i think its great. But... Without 4.02 it wouldnt be possible for my rig to go there, single socket quads running Linux/4.02 have fallen out of the Top100 at an increasing rate.
You might know, right after I'd said that I'd never had trouble with the 4.14 app and ReiserFS, two 4.14 workunits simultaneously fail on my Compaq dual-processor P-III 733 machine.
For anyone who needs to look at this, its ID number is 764145.
For the record, it's running Feisty Fawn Ubuntu from a SCSI hard drive that's formatted with ReiserFS. I don't know that it is Reiser-related, but wanted to let everyone know just-in-case.
And after all, this is beta software, so basically every error detected here will actually help to improve the app. This means running the risk of losing a few credits but every undetected error that goes into production might cost you credits as well (or wasted electricity, if you are not afetr credits).
RE: RE: RE: reiserfs,
)
I'm using ReiserFs (it used to be Suse's default FS some time ago IIRC) without any problem so far with 4.14 on one host. So it's not a general ReiserFS problem .
CU
H-B
RE: RE: RE: RE: reise
)
Same here. I have ReiserFS installed on several machines. Two are currently running, happily crunching away with the Einstein 4.14 app. So far, no problems at all.
All I can say is that 4.02 is
)
All I can say is that 4.02 is crunching the same WU that gave errors in 4.14 with no problem at all. All went well up to 4.12.
Tullio
RE: RE: Bernd, did you
)
While running one 4.09 and one 4.12 WU, I tried really hard to reproduce the error, but without luck. I managed to reach an average 1 minute load of about 12 and system again was barely responsive sometimes. But responsiveness was better than last time when the errors occurred.
Maybe I must concentrate on disk I/O on the reiserfs, where the BOINC folder is located and not generally shared over all disks. I'll give this another try, probably at the weekend.
cu,
Michael
I started 87897850 with 4.09,
)
I started 87897850 with 4.09, but finished it with 4.14. It ran and validated successfully, and this system runs reiserfs as well. The time dropped noticeably from 4.09 as well.
Hope things get sorted out
)
Hope things get sorted out fast so a new official GNU/Linux app can come out soon, the linux rig that used to be #2 has dropped to #19 since S5R3 started, linux users have taken a serious RAC drop with 4.02.
The performance of 4.12/4.14 is beautiful, my xeon reached #80 in the top hosts list today. Doesnt sound very impressive maybe, but considered its only a single socket dual core i think its great. But... Without 4.02 it wouldnt be possible for my rig to go there, single socket quads running Linux/4.02 have fallen out of the Top100 at an increasing rate.
Team Philippines
You might know, right after
)
You might know, right after I'd said that I'd never had trouble with the 4.14 app and ReiserFS, two 4.14 workunits simultaneously fail on my Compaq dual-processor P-III 733 machine.
For anyone who needs to look at this, its ID number is 764145.
For the record, it's running Feisty Fawn Ubuntu from a SCSI hard drive that's formatted with ReiserFS. I don't know that it is Reiser-related, but wanted to let everyone know just-in-case.
Maybe give 4.12 a try, its as
)
Maybe give 4.12 a try, its as fast as 4.14 and hopefully doesnt have this problem...
4.12
Team Philippines
RE: Maybe give 4.12 a try,
)
I'll keep that in mind. But, since this is the only problem I've had with 4.14 so far, I'll give this machine one more chance, first.
And after all, this is beta
)
And after all, this is beta software, so basically every error detected here will actually help to improve the app. This means running the risk of losing a few credits but every undetected error that goes into production might cost you credits as well (or wasted electricity, if you are not afetr credits).
CU
Bikeman