Long as everything remains in production flow, specially the assimilation to continue clearing space used by complete quorums, there's no reason to irk the nerves.

If they get caught off guard again on , when these sizes are actually specified as possible on the system requirement page, they may have to think about a career change.

Currently the system is caught up on all assimilation as well as the file system sitting at 44% full. We are not running MCM at full speed right now so that helps keep the filesystem with more space. We are still working with the researchers to help them keep the file return size low.

We do appreciate the information and hopefully there is not a career change in the future :)

Thanks,
-Uplinger

So we have multiple file systems that are utilized behind the scenes. Each file system can be considered at a high level like a C: drive or D: drive on windows (they are a little bit more sophisticated than that). But the file system where members upload results to which is shared between 3 upload servers is sitting at 44% full. If there is say 1TB of storage for that filesystem, then we are using 440GB of storage out of the 1000GB total.

During assimilation we take results that have been validated and move them to another filesystem that has more storage and is used for more than the purpose of upload and download of work units/results.

Thanks,
-Uplinger

As of the latest statistics update (5/4/14 00:06:03 UTC) (5 hours ago) was not returned today was 265,693. I am unsure whether or not the project is back to full speed but it is clipping along at a reasonable pace. Statistic information was found under the Community tab