A conflict in linux formatall ws label and other fixes

[sparshev]

Found a couple of nasty bugs in the disk init scripts and fixed them.

• formatall in linux can easily create another ws to the existing one and mount it over the same mountpoint which leads to empty workspace instead of cached one
• warmup scripts:
  • used base 10 instead of base 2 for bytes size
  • windows could skip the disks because they were not populated at the time and terminate the running fio processes because did not wait properly for them
  • fio now outputs to separated file to keep an eye on warmed up disks results
• added jenkins user on linux to be in journal group to read logs from the system
• quick fix for file upload due to obvious bug in the logic

Related Issue

57

Motivation and Context

Conflicts in disks mounts are bad

How Has This Been Tested?

Manually

Screenshots (if appropriate):

Types of changes

• [x] Bug fix (non-breaking change which fixes an issue)
• [ ] New feature (non-breaking change which adds functionality)
• [ ] Breaking change (fix or feature that would cause existing functionality to change)

Checklist:

• [x] I have signed the Adobe Open Source CLA.
• [x] My code follows the code style of this project.
• [ ] My change requires a change to the documentation.
• [ ] I have updated the documentation accordingly.
• [x] I have read the CONTRIBUTING document.
• [ ] I have added tests to cover my changes.
• [x] All new and existing tests passed.