From: "H. Peter Anvin" <hpa@zytor.com>
To: linux-kernel@vger.kernel.org
Subject: Re: Linux should better cope with power failure
Date: 20 Mar 2001 13:38:04 -0800 [thread overview]
Message-ID: <998ijs$ord$1@cesium.transmeta.com> (raw)
In-Reply-To: <3FA68C00B3E3A3418373DA6446330DD30328E0@spike.i405.net> <3AB68A91.9785A9D0@bluewin.ch>
Followup to: <3AB68A91.9785A9D0@bluewin.ch>
By author: Otto Wyss <otto.wyss@bluewin.ch>
In newsgroup: linux.dev.kernel
>
> It was just a simple test machine where it didn't matter what was lost.
> Still that doesn't justify this behaviour.
>
Then use a journalling filesystem. If not, give it a few minutes of
idle time; fsck will complain on boot but it should be able to clean
up the mess.
-hpa
--
<hpa@transmeta.com> at work, <hpa@zytor.com> in private!
"Unix gives you enough rope to shoot yourself in the foot."
http://www.zytor.com/~hpa/puzzle.txt
next prev parent reply other threads:[~2001-03-20 21:39 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-03-19 22:11 Linux should better cope with power failure Stephen Gutknecht (linux-kernel)
2001-03-19 22:39 ` Otto Wyss
2001-03-20 21:38 ` H. Peter Anvin [this message]
-- 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 21:16 Torrey Hoffman
2001-03-19 22:28 ` Stephen Satchell
2001-03-19 23:05 ` Andre Hedrick
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='998ijs$ord$1@cesium.transmeta.com' \
--to=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.org \
/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