The Semi-Official I'm Thread Part XV
Originally Posted by WestSideBilly' date='Feb 13 2005, 01:38 PM
I'm saying RAID stands for Redundant Array of Independant Drives and is a way of making multiple drives appear to be one to windows (or whatever OS you use). A RAID5 is a parity setup which uses one drive to store parity checks of the other 2-7 drives; using the basis that any binary file XORed with a parity file of the same size will result in a desired 3rd file.
Essentially... if one hard drive fails, the parity drive can be used to rebuild the data on the failed drive. Very handy if, say, you have 7 years of mp3 burning and compilation to store.

Essentially... if one hard drive fails, the parity drive can be used to rebuild the data on the failed drive. Very handy if, say, you have 7 years of mp3 burning and compilation to store.

Originally Posted by ACLR8' date='Feb 13 2005, 11:07 AM
I'm on a soap box now:
As a leader I always want to believe than any mission failure is based on requirements >> resources. That is to say I always want to believe that teams do the best they can with what they have.
However, if it just a matter of piss poor performance, then I believe it could be rectified with good leadership and proper prior planning (the 6 p's of mission success).
As a leader I always want to believe than any mission failure is based on requirements >> resources. That is to say I always want to believe that teams do the best they can with what they have.
However, if it just a matter of piss poor performance, then I believe it could be rectified with good leadership and proper prior planning (the 6 p's of mission success).
It starts with understanding the requirements from both a system and user perspective and then you factor in compromises necessitated by the amount of resources available for the task.
I could go on, but it'll just force me to go find a bigger soapbox and I'm suffering from a food coma right now and don't have the energy...
Originally Posted by brantshali' date='Feb 13 2005, 04:54 PM
I'm saying I have a background in IT, project management, program management and process design and watching a cluster
happen boggles my mind when some or all of the variables were predictable and could have been avoided with a well reasoned plan.
It starts with understanding the requirements from both a system and user perspective and then you factor in compromises necessitated by the amount of resources available for the task.
I could go on, but it'll just force me to go find a bigger soapbox and I'm suffering from a food coma right now and don't have the energy...
It starts with understanding the requirements from both a system and user perspective and then you factor in compromises necessitated by the amount of resources available for the task.
I could go on, but it'll just force me to go find a bigger soapbox and I'm suffering from a food coma right now and don't have the energy...








