On 12/23/2014 10:31 AM, jdd wrote:
Le 23/12/2014 16:15, Anton Aylward a écrit :
"Expensive" ??!!?? Many of my clients are banks. The expense of downtime or data loss would exceed the cost of "mirrored" equipment or running a 'hot backup' site on another tectonic plate & power grid.
then, why run the server on openSUSE? As I said, I have no way to know what is the OP system for.
Indeed. For many it seems more to do with salesmen and a "you don't get fired for ..." policies than any rationale. Mind you, it sometimes does work to a rationale: another client is nominally a Microsoft shop in that there is a MS PC on every desk, but the servers are a brace of high end HP machines running SAMBA. More reliable than any PC running MS-Server. Another, a brokerage now taken over by a bank, dumped all its high end SUN workstations running multi-windows brokerage stuff and put in RedHat Linux workstations with bigger screens running equivalent software, even though Linux was unknown elsewhere in the bank. Go figure.
For SMB/home users the large drives and the vendor's shift to drives that don't live forever as the old 20G and 30G drives seem to
I always had hard drive failures, randomly and not often (but often at the bad time as always :-()
Hardware failure is always inconvenient! Always frustrating! Its why we have 'hot spares' and backups and ... Strictly speaking, hardware failure seems to be predictable, if you have the right tools and do the right analysis. I've read of military programs for 'copter maintenance that can predict when something needs replacing with un-nerving accuracy! I'm sure the same could be applied to, for example, disk drives, if one was willing to do the detailed analysis of things like bearing vibration, retry. But is that actually available under SMART?
I'm experimenting with SATA/ATA converters but they don't seem to want to allow writes. *sigh*
?? go through usb adapters...
WTF? These things clip on the back of my ATA drives and let the SATA plug in ... Damn, not enough drive bays in this Dell box!
I guess we, at openSUSE deal with home or small business products, not large money capable systems that can afford SLES or SLED
the initial problem was grub2 not allowing install on raid.md mix. It's only in this case that I propose to boot, why not on sd card or usb flash key for /boot is nothing more is available (as in all the sata places are used by the raid disks)
My big complaint about many of the RAID models is that they require "similar disks". That's why I like LVM and BtrFS. My idea of a proper setup would be to have something like /boot on *every* disk :-) That way, if any disk died (or even a couple) there would still be one to boot from.
I certainly wont discuss banks or insurance companies systems
Why not? Once upon a time, the "Cold War" days, it was the military who paid for an pioneered many of the software techniques and tools we consider normal today. The internet was a DARPA project; accurate GPS was a military feature. A friend has a private single prop 2-seater plane that has C3I/NAV which 25 years ago was developed for the military. Jet engines were originally developed for warplanes. So it goes. These days the people paying for innovation are the consumer giants, of not the likes of Google then the banks and their ilk. Much of what we have in Linux comes from those large firms. One reason I like LVM is that long before it was available for Linux I was using what amounted to the same thing on an large IBM AIX setup, experiment with balancing and load with BD2. Ditto various RAID with IBM, HP. I'm not alone in this learning experience. Many of us here are still in such settings. -- /"\ \ / ASCII Ribbon Campaign X Against HTML Mail / \ -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org