From: Stephen Satchell <satch@fluent-access.com>
To: Torrey Hoffman <torrey.hoffman@myrio.com>,
"'otto.wyss@bluewin.ch'" <otto.wyss@bluewin.ch>,
linux-kernel@vger.kernel.org
Subject: RE: Linux should better cope with power failure
Date: Mon, 19 Mar 2001 14:28:15 -0800 [thread overview]
Message-ID: <4.3.2.7.2.20010319142441.00b2e9f0@mail.fluent-access.com> (raw)
In-Reply-To: <B65FF72654C9F944A02CF9CC22034CE22E1B40@mail0.myrio.com>
At 01:16 PM 3/19/01 -0800, Torrey Hoffman wrote:
>Yes. Some of this is your responsibility. You have several options:
>1. Get a UPS. That would not have helped your particular problem,
> but it's a good idea if you care about data integrity.
>2. Use a journaling file system. These are much more tolerant of
> abuse. Reiserfs seems to work for me on embedded systems I am
> building where the user can (and does) remove the power any time.
>3. Use RAID. Hard drives are very cheap and software raid is very
> easy to set up.
Sorry, but you really should have read the ENTIRE thread before
commenting. This guy's original complaint was that his USB keyboard locks
up, and the only way to get it back is to do a very rude restart. In
combatting this problem, the guy was observing the "shortcomings" of the
file system.
To be more to the point of the guy's problem, he should consider using
software specifically intended for UPS hardware to notify a system when the
power is going to go, and wire up an appropriate switch to signal his
system to enter shutdown when his keyboard goes south. By forcing an
orderly shutdown, he doesn't see the fsck-ing messages, he gets his USB
keyboard back, and all is well with the world.
Of course, the other option is to use a regular keyboard instead of a USB
keyboard, but why point out the really easy solution? "Hey Doc, it hurts
when I do this." "Then don't do it."
Satch
next prev parent reply other threads:[~2001-03-19 22:29 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-03-19 21:16 Torrey Hoffman
2001-03-19 22:28 ` Stephen Satchell [this message]
2001-03-19 23:05 ` Andre Hedrick
-- strict thread matches above, loose matches on Subject: below --
2001-03-23 15:28 David Balazic
2001-03-23 18:22 ` Gerhard Mack
2001-03-26 9:34 ` David Balazic
2001-03-23 19:29 ` Otto Wyss
2001-03-23 22:41 ` David Ford
2001-03-24 8:44 ` Otto Wyss
2001-03-24 9:47 ` David Ford
2001-03-24 10:28 ` Otto Wyss
2001-03-26 10:22 ` David Balazic
2001-03-26 10:17 ` David Balazic
2001-03-19 22:35 Otto Wyss
2001-03-19 23:12 ` John R Lenton
2001-03-19 22:11 Stephen Gutknecht (linux-kernel)
2001-03-19 22:39 ` Otto Wyss
2001-03-20 21:38 ` H. Peter Anvin
2001-03-19 19:46 Otto Wyss
2001-03-19 19:59 ` Charles Cazabon
2001-03-19 20:15 ` Richard B. Johnson
2001-03-19 20:51 ` Brian Gerst
2001-03-19 21:08 ` Jeremy Jackson
2001-03-19 21:35 ` Richard B. Johnson
2001-03-19 21:59 ` Brian Gerst
2001-03-19 22:15 ` Jeremy Jackson
2001-03-19 15:14 ` Ben Ford
2001-03-19 23:07 ` Werner Almesberger
2001-03-19 20:19 ` William T Wilson
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4.3.2.7.2.20010319142441.00b2e9f0@mail.fluent-access.com \
--to=satch@fluent-access.com \
--cc=linux-kernel@vger.kernel.org \
--cc=otto.wyss@bluewin.ch \
--cc=torrey.hoffman@myrio.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®