From: "Stephen C. Tweedie" <sct@redhat.com>
To: ext3-users@redhat.com
Cc: Sean Hunter <sean@uncarved.com>, linux-kernel@vger.kernel.org
Subject: Re: Strane remount behaviour with ext3-2.4-0.9.4
Date: Wed, 1 Aug 2001 17:39:51 +0100 [thread overview]
Message-ID: <20010801173951.I3744@redhat.com> (raw)
In-Reply-To: <20010727104049.B6311@uncarved.com> <200107271715.f6RHFea24226@lynx.adilger.int>
In-Reply-To: <200107271715.f6RHFea24226@lynx.adilger.int>; from adilger@turbolinux.com on Fri, Jul 27, 2001 at 11:15:39AM -0600
Hi,
On Fri, Jul 27, 2001 at 11:15:39AM -0600, Andreas Dilger wrote:
> > servers. Since the server in question is a farily security-sensitive box, my
> > /usr partition is mounted read only except when I remount rw to install
> > packages.
>
> If it is a security-sensitive box, you need to at least use data=ordered or
> data=journal. Using data=writeback allows the possibility that after a crash
> one user might be able to read data from deleted files of another user (note
> that reiserfs currently only runs the equivalent of data=writeback).
Agreed, and for most workloads data=ordered will have very little
performance difference from data=writeback.
> You _could_ leave out the data=writeback from /etc/fstab (default is ordered),
> and you will be able to remount OK. Also, Andrew made a patch which allowed
> you to specify the data= mode on remount, as long it is the same.
Indeed, but I'll need to make sure that the remount with no data= mode
also works (that should be legal.)
Cheers,
Stephen
prev parent reply other threads:[~2001-08-01 17:08 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-07-27 9:40 Strane remount behaviour with ext3-2.4-0.9.4 Sean Hunter
2001-07-27 17:15 ` Andreas Dilger
2001-08-01 16:39 ` Stephen C. Tweedie [this message]
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=20010801173951.I3744@redhat.com \
--to=sct@redhat.com \
--cc=ext3-users@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=sean@uncarved.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 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.