From: "Sean Hunter" <sean@uncarved.com>
To: ext3-users@redhat.com
Cc: linux-kernel@vger.kernel.org
Subject: Strane remount behaviour with ext3-2.4-0.9.4
Date: Fri, 27 Jul 2001 10:40:49 +0100 [thread overview]
Message-ID: <20010727104049.B6311@uncarved.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 1402 bytes --]
Following the announcement on lkml, I have started using ext3 on one of my
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.
I converted this partition to run ext3 with the mount options
"nodev,ro,data=writeback,defaults" figuring that when I need to install new
packages etc, that I could just mount rw as before and that metadata-only
journalling would be ok for this partition as it really sees very little write
activity.
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.
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.
Wierdly, "mount" lists it as being still an ext3 partition even though it has
been remounted as ext2. I can't umount /usr because kjournald is currently
listed as using the partition.
The box in question is more-or-less RedHat 7.1, with ext3-2.4-0.9.4, kernel
2.4.7 and with the following relevant package versions:
mount-2.11g-4
util-linux-2.11f-3
e2fsprogs-1.22-2
...all from rawhide rpms.
I'm going to try one of the partitions mounted "data=ordered" to see if I see
the same sort of thing.
Sean
[-- Attachment #2: Type: application/pgp-signature, Size: 232 bytes --]
next reply other threads:[~2001-07-27 9:41 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-07-27 9:40 Sean Hunter [this message]
2001-07-27 17:15 ` Strane remount behaviour with ext3-2.4-0.9.4 Andreas Dilger
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=20010727104049.B6311@uncarved.com \
--to=sean@uncarved.com \
--cc=ext3-users@redhat.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