From: "Stephen C. Tweedie" <sct@redhat.com>
To: Daniel Phillips <phillips@innominate.de>
Cc: Rik van Riel <riel@conectiva.com.br>,
linux-kernel@vger.kernel.org, Stephen Tweedie <sct@redhat.com>
Subject: Re: Journaling: Surviving or allowing unclean shutdown?
Date: Thu, 4 Jan 2001 19:21:04 +0000 [thread overview]
Message-ID: <20010104192104.C2034@redhat.com> (raw)
In-Reply-To: <Pine.LNX.4.30.0101031253130.6567-100000@springhead.px.uk.com> <Pine.LNX.4.21.0101031325270.1403-100000@duckman.distro.conectiva> <3A5352ED.A263672D@innominate.de>
In-Reply-To: <3A5352ED.A263672D@innominate.de>; from phillips@innominate.de on Wed, Jan 03, 2001 at 05:27:25PM +0100
Hi,
On Wed, Jan 03, 2001 at 05:27:25PM +0100, Daniel Phillips wrote:
>
> Tux2 is explicitly designed to legitimize pulling the plug as a valid
> way of shutting down. Metadata-only journalling filesystems are not
> designed to be used this way, and even with full-data journalling you
> should bear in mind that your on-disk filesystem image remains in an
> invalid state until the journal recovery program has run successfully.
ext3 does the recovery automatically during mount(8), so user space
will never see an unrecovered filesystem. (There are filesystem flags
set by the journal code to make sure that an unrecovered filesystem
never gets mounted by a kernel which doesn't know how to do the
appropriate recovery.)
--Stephen
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/
next prev parent reply other threads:[~2001-01-04 19:23 UTC|newest]
Thread overview: 58+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-01-03 12:55 Journaling: Surviving or allowing unclean shutdown? Dr. David Gilbert
2001-01-03 15:26 ` Rik van Riel
2001-01-03 15:38 ` Michael Rothwell
2001-01-03 16:18 ` Andi Kleen
2001-01-03 16:27 ` Daniel Phillips
2001-01-03 16:42 ` Alex Belits
2001-01-04 8:00 ` Daniel Phillips
2001-01-04 17:39 ` Alex Belits
2001-01-03 18:52 ` Dr. David Gilbert
2001-01-04 9:57 ` Helge Hafting
2001-01-04 10:14 ` Daniel Phillips
2001-01-04 10:25 ` David Woodhouse
2001-01-04 17:43 ` David Lang
2001-01-04 17:52 ` David Woodhouse
2001-01-04 18:00 ` David Lang
2001-01-04 18:11 ` Alan Cox
2001-01-05 4:12 ` Chipzz
2001-01-05 4:18 ` Alan Cox
2001-01-05 16:55 ` Mike Touloumtzis
2001-01-05 16:57 ` David Woodhouse
2001-01-05 22:09 ` Pavel Machek
2001-01-04 17:59 ` Alan Cox
2001-01-04 18:10 ` Chris Wedgwood
2001-01-04 18:15 ` Mo McKinlay
2001-01-04 18:19 ` David Lang
2001-01-04 18:20 ` Mo McKinlay
2001-01-04 19:42 ` Richard B. Johnson
2001-01-04 20:31 ` egger
2001-01-04 20:59 ` Richard B. Johnson
2001-01-04 21:05 ` egger
2001-01-04 22:45 ` Erik Mouw
2001-01-04 18:23 ` Chris Wedgwood
2001-01-05 12:04 ` David Woodhouse
2001-01-04 18:21 ` Dr. David Gilbert
2001-01-04 18:11 ` Mo McKinlay
2001-01-04 21:00 ` Brett G. Person
2001-01-05 22:05 ` Pavel Machek
2001-01-04 19:21 ` Stephen C. Tweedie [this message]
2001-01-04 21:08 ` Stefan Traby
2001-01-04 22:49 ` Stephen C. Tweedie
2001-01-05 1:01 ` Stefan Traby
2001-01-05 8:10 ` Andreas Dilger
2001-01-05 11:05 ` Stephen C. Tweedie
2001-01-05 11:58 ` David Woodhouse
2001-01-06 19:57 ` Marc Lehmann
2001-01-06 20:09 ` Stefan Traby
2001-01-06 20:35 ` Chris Mason
2001-01-06 21:49 ` Marc Lehmann
2001-01-08 12:02 ` Stephen C. Tweedie
2001-01-09 9:34 ` Roger Gammans
2001-01-05 0:31 ` Daniel Phillips
2001-01-05 8:00 ` Andreas Dilger
2001-01-05 12:46 ` Alan Cox
2001-01-05 12:59 ` Chris Wedgwood
2001-01-05 13:22 ` Stephen C. Tweedie
2001-01-05 10:31 ` Stephen C. Tweedie
[not found] <fa.e3022cv.v2ucim@ifi.uio.no>
[not found] ` <fa.naq8vev.74ai08@ifi.uio.no>
2001-01-04 22:38 ` Dan Maas
-- strict thread matches above, loose matches on Subject: below --
2001-01-08 23:19 Bernd Eckenfels
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=20010104192104.C2034@redhat.com \
--to=sct@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=phillips@innominate.de \
--cc=riel@conectiva.com.br \
/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