From: Andreas Dilger <adilger@turbolinux.com>
To: sean@uncarved.com (Sean Hunter)
Cc: ext3-users@redhat.com, linux-kernel@vger.kernel.org
Subject: Re: Strane remount behaviour with ext3-2.4-0.9.4
Date: Fri, 27 Jul 2001 11:15:39 -0600 (MDT) [thread overview]
Message-ID: <200107271715.f6RHFea24226@lynx.adilger.int> (raw)
In-Reply-To: <20010727104049.B6311@uncarved.com> from "Sean Hunter" at Jul 27, 2001 10:40:49 AM
Sean writes:
> 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).
> When I try to remount it r/w I get a log message saying:
> Jul 27 09:54:29 henry kernel: EXT3-fs: cannot change data mode on remount
>
> ...even if I give the full mount option list (including data=writeback) with
> the remount instruction.
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.
> I can, however, remount it as ext2 read-write, but when I try to remount as
> ext3 (even read only) I get the same problem.
You can't change filesystem types via remount (ext2 and ext3 are different
filesystem drivers). In the future, you might be able to use the ext3
driver to mount a filesystem in totally unjournaled (ext2) mode.
Cheers, Andreas
--
Andreas Dilger
http://sourceforge.net/projects/ext2resize/
http://www-mddsp.enel.ucalgary.ca/People/adilger/
next prev parent reply other threads:[~2001-07-27 17:18 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-07-27 9:40 Sean Hunter
2001-07-27 17:15 ` Andreas Dilger [this message]
2001-08-01 16:39 ` Stephen C. Tweedie
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=200107271715.f6RHFea24226@lynx.adilger.int \
--to=adilger@turbolinux.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 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®