Michael Tokarev wrote:
Unfortunately an UPS does not *really* help here. Because unless
it has control program which properly shuts system down on the loss
of input power, and the battery really has the capacity to power the
system while it's shutting down (anyone tested this?
----
Yes. I must say, I am not connected or paid by APC.
With new UPS?
and after an year of use, when the battery is not new?), -- unless
the UPS actually has the capacity to shutdown system, it will cut
the power at an unexpected time, while the disk(s) still has dirty
caches...
--------
If you have a "SmartUPS" by "APC", their is a freeware demon that monitors
it's status. The UPS has USB and serial connections.
It's included in some distributions (SuSE). The config
file is pretty straight forward.
I recommend the "1000XL" (1000 peak Volt-Amp load -- usually at startup;
note, this is not the same as watts as some of us were taught in basic
electronics class since the unit isn't a simple resistor (like a light
bulb). over the 1500XL because with the 1000XL, you can buy several
"add-on batteries" that plug into the back.
One minor (but not fatal) design flaw: the add-on batteries give no indication
that they are "live" (I knocked a cord on one, and only got 7 minutes
of uptime before things shut-down instead of my expected 20.
I have 3-cells total (controller & 1 extra pack). So why is my run time
so short? I am being lazy in buying more extension packs.
The UPS is running 3 computers, the house-phone, (answering and wireless
handsets). a digital clock, 1 LCD (usually off), The real killer is a
new workstation with 2x2-Core-II chips and other comparable equipment.
The "1500XL" doesn't allow for adding more power packs.
The "2200XL" does allow extra packs but comes in a rack-mount format.
It's not just a battery backup -- it conditions the power -- to filter out
spikes and emit a pure sine wave. It will kick in during over or under
voltage conditions (you can set the sensitivity). Adjustable alarm
when on battery, setting of output volts (115, 230, 120, 240). It
selftests at least every 2 weeks or shorter (to your fancy).
It also has a network feature (that I haven't gotten to work yet -- they just
changed the format), that allows other computers on the same net to also be
notified and take action.
You specify what scripts to run at what times (power off, power on, getting
critically low, etc).
Hasn't failed me 'yet' -- cept when a charger died and was replaced free of
cost (within warantee). I have a separate setup another room for another
computer.
The upspowerd runs on linux or windows (under cygwin, I think).
You can specify when to shut down -- like "5 minutes of battery life left.
The controller unit has 1 battery. But the add-ons have 2 batteries
each, so the first add-on adds 3x to the run-time. When my system
did shut down "prematurely", it went through the full "halt" sequence,
which I'd presume flushes disk caches.
the drive claims to have metadata safe on disk but actually does not,
and you lose power, the data claimed safe will evaporate, there's not
much the fs can do. IO write barriers address this by forcing the drive
to flush order-critical data before continuing; xfs has them on by
default, although they are tested at mount time and if you have
something in between xfs and the disks which does not support barriers
(i.e. lvm...) then they are disabled again, with a notice in the logs.
Note also that with linux software raid barriers are NOT supported.
------
Are you sure about this? When my system boots, I used to have
3 new IDE's, and one older one. XFS checked each drive for barriers
and turned off barriers for a disk that didn't support it. ... or
are you referring specifically to linux-raid setups?
Would it be possible on boot to have xfs probe the Raid array,
physically, to see if barriers are really supported (or not), and disable
them if they are not (and optionally disabling write caching, but that's
a major performance hit in my experience.
Linda
-
To unsubscribe from this list: send the line "unsubscribe linux-raid" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at http://vger.kernel.org/majordomo-info.html
