From: Stephen Tweedie <sct@redhat.com>
To: linux-lvm@sistina.com
Cc: Stephen Tweedie <sct@redhat.com>,
Steve Wray <steve.wray@paradise.net.nz>
Subject: Re: [linux-lvm] EXT2 to EXT3 LVM volume on Redhat
Date: Mon Jun 24 08:41:01 2002 [thread overview]
Message-ID: <20020623164611.A1993@redhat.com> (raw)
In-Reply-To: <000c01c20ccf$fcac9e90$0201a8c0@fosi>; from steve.wray@paradise.net.nz on Thu, Jun 06, 2002 at 08:31:30AM +1200
Hi,
On Thu, Jun 06, 2002 at 08:31:30AM +1200, Steve Wray <steve.wray@paradise.net.nz> wrote:
> /dev/system/home /home ext3 data=journal 1 2
>
> Its the bomb. I have a hell of a lot of dynamic data
> in that /home so in event of a crash there was a big
> chance of corruption. Not Any More!!!!!
> 8-)
I'm not quite sure why people think that data=journal is any "safer"
than the default data=ordered mode. In fact, data=ordered could well
be safer simply because the default mode is probably in use on more
systems, and so is better tested. :-)
data=journal writes the data to the journal as well as the metadata,
but *both* ordered and data modes flush data to disk carefully as part
of their transaction commit. If you create new files with the default
of data=ordered, there is still an absolute guarantee that a
transaction commit will show all the data safe on disk, and you will
never see stale data blocks show up on disk after a crash.
Only the looser "data=writeback" mode of ext3 relaxes this guarantee
and makes data writes independent of metadata writes, as they are for
most other filesystems.
Cheers,
Stephen
next prev parent reply other threads:[~2002-06-24 8:41 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-06-04 15:17 [linux-lvm] EXT2 to EXT3 LVM volume on Redhat Aslak Sommerfelt Skretting
2002-06-04 15:30 ` Ben Lutgens
2002-06-04 16:04 ` Aslak Sommerfelt Skretting
2002-06-04 16:16 ` Steve Wray
2002-06-04 16:29 ` Aslak Sommerfelt Skretting
2002-06-05 15:32 ` Steve Wray
2002-06-24 8:41 ` Stephen Tweedie [this message]
2002-06-04 21:04 ` Wolfgang Weisselberg
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=20020623164611.A1993@redhat.com \
--to=sct@redhat.com \
--cc=linux-lvm@sistina.com \
--cc=steve.wray@paradise.net.nz \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.