To start with there isn’t any extent for synchronous drive availability
disk!servers!almost every other There are various properties available on the internet as well as regardless if of several had been place some regarding the tincture from the web. Nevertheless, properties such as for instance Servers Guidance
drive!machine!guidance Host today need large numbers of higher disks to function satisfactorily during the commercial configurations. Given that mean-time anywhere between failure (MTBF) decreases rapidly due to the fact quantity of areas improve it’s best to look into the having fun with RAID for coverage and make use of several out of mid-sized pushes in place of a single huge drive. More details can be obtained at the . and at associated There’s also a post into the Byte named with many issues that is actually relevant to Linux. Problems
disk!pitfalls The dangers of splitting up everything into separate partitions are briefly mentioned in the section about volume management. Still, several people have asked me to emphasize this point more strongly: when one partition fills up it cannot grow any further, no matter if there is plenty of space in other partitions. In particular look out for explosive growth in the news spool (/var/spool/information). For multi user machines with quotas keep an eye on /tmp and /var/tmp as some people try to hide their files there, just look out for filenames ending in gif or jpeg. In fact, for single physical drives this scheme offers very little gains at all, other than making file growth monitoring easier (using ‘df‘) and physical track positioning. A freely available volume management system would solve this but this is still some time in the future. However, when more specialised file systems become available even a single disk could benefit from being divided into several partitions. For more information see section .