Doesn't look so good. Five CEP 2 Units which are finished refuse absolutely to upload. It's said "retrait de projet" whatever it may mean...

Same here with one CFSW result uploaded at 19:24:58 GMT/UTC and reported at 19:30:19 GMT. No error in the Result Log, but status is Error . Looks like the filesystem fault caused some collateral damage.
(Times below are local, UTC+1).
-----------------------------------------------
Result Name: cfsw_ 1830_ 01830287_ 0--

<core_client_version>6.10.58</core_client_version>
<![CDATA[
<stderr_txt>
[17:27:18] INFO:Beginning simulation: 1990:240:1484161844
[17:32:06] INFO: Finished tick number 4
[17:35:49] INFO: Finished tick number 9
[17:39:02] INFO: Finished tick number 14
[17:43:07] INFO: Finished tick number 19
[17:46:14] INFO: Finished tick number 24
[17:50:18] INFO: Finished tick number 29
[17:53:51] INFO: Finished tick number 34
[17:57:25] INFO: Finished tick number 39
[18:01:22] INFO: Finished tick number 44
[18:04:22] INFO: Finished tick number 49
[18:08:32] INFO: Finished tick number 54
[18:11:52] INFO: Finished tick number 59
[18:15:53] INFO: Finished tick number 64
[18:19:41] INFO: Finished tick number 69
[18:22:59] INFO: Finished tick number 74
[18:27:11] INFO: Finished tick number 79
[18:30:20] INFO: Finished tick number 84
[18:34:40] INFO: Finished tick number 89
[18:38:21] INFO: Finished tick number 94
[18:42:05] INFO: Finished tick number 99
[18:46:09] INFO: Finished tick number 104
[18:49:14] INFO: Finished tick number 109
[18:53:25] INFO: Finished tick number 114
[18:56:46] INFO: Finished tick number 119
[19:00:41] INFO: Finished tick number 124
[19:04:27] INFO: Finished tick number 129
[19:07:47] INFO: Finished tick number 134
[19:11:56] INFO: Finished tick number 139
[19:15:07] INFO: Finished tick number 144
[19:19:12] INFO: Finished tick number 149
[19:22:43] INFO: Finished tick number 154
[19:26:14] INFO: Finished tick number 159
[19:30:12] INFO: Finished tick number 164
[19:33:13] INFO: Finished tick number 169
[19:37:22] INFO: Finished tick number 174
[19:40:41] INFO: Finished tick number 179
[19:44:34] INFO: Finished tick number 184
[19:48:23] INFO: Finished tick number 189
[19:51:43] INFO: Finished tick number 194
[19:55:54] INFO: Finished tick number 199
[19:59:05] INFO: Finished tick number 204
[20:03:09] INFO: Finished tick number 209
[20:06:42] INFO: Finished tick number 214
[20:10:18] INFO: Finished tick number 219
[20:14:17] INFO: Finished tick number 224
[20:17:19] INFO: Finished tick number 229
[20:21:29] INFO: Finished tick number 234
[20:24:49] INFO: Finished tick number 239
20:24:49 (1000): called boinc_finish

</stderr_txt>
]]>
-----------------------------------------------
The WU Status is interesting - a 2nd version has been sent out, but the replication is still one.

Created: 05/17/2012 03:48:36
Name: cfsw_1830_01830287
Minimum Quorum: 1
Replication: 1

cfsw_ 1830_ 01830287_ 1-- - In Progress 20/05/12 23:33:31 24/05/12 23:33:31 0.00 0.0 / 0.0
cfsw_ 1830_ 01830287_ 0-- 605 Error 18/05/12 22:05:43 20/05/12 19:38:21 2.92 101.9 / 0.0

Midnight stats of 330 runtime years for Sunday suggest a slip & slide of about 45-50 years onto the Monday stats. Don't be surprised of being overtaken in the ranks by a few that backed off till the new day.

--//--

P.S. The Official All Clear: https://secure.worldcommunitygrid.org/forums/wcg/printpost_post,378424

Think it's a quasi falsehood, tonyh25. Someone else's machine that needed a wingman anyhow, had you to do that and vice versa [20%+ has this]. Reports were like... you and who else, meaning the fall out was more than minimal... possibly you were to quick to reconnect, when I have the habit to suspend client networking until I see forums and result status pages being live and responsive... and miss out on the [I'm in a rush] traffic jam. For zero redundant it's 5, not 34 sequential actual valids, before the 'alone' is granted again [which does not constitute a 'A++ status of being rated as repair man].

Some have them quick, some have them slow, these sequential validations. If it does not do that as per design, then something is broken, but it requires demonstration. Don't know how to hard evidence that easily, but I just know that I had 49 CFSW, with wingman, before the 5th validation came through as needed before the 50th assignment had no wingman. The mistake was running a larger cache on a quad, whereas if no / very low cache, probably would have moved that 5th validation point to an earlier assignment (mix crunching reduces that pain btw).

--//--