From: PiX <pix@devlife.org>
To: linux-fsdevel@vger.kernel.org
Subject: [ext3] Changes to block device after an ext3 mount point has been remounted readonly
Date: Thu, 18 Feb 2010 17:45:00 +0100 [thread overview]
Message-ID: <baaef4711002180845n29561ccif451fae62e49e520@mail.gmail.com> (raw)
I'm experiencing a strange behavior. After having remounted / to
readonly, I'm doing a sha1sum on /dev/sda1 (which is mounted on /)
Then, I reboot, GRUB starts the kernel with the ro option, when I do a
hash of /dev/sda1 the sum has changed.
This only happen when the rootfs hash been mounted ro, then remounted
rw to make some changes and remounted ro.
On the next reboot the hash will change, but only one time. Next
reboots will not alter the control sum, until of course I remount it
RW.
Here's a small shell script that show that some changes are made
between "mount -o remount,ro" and umount.
On my system the might run 1 time before failing as well as 20.
For the record:
$ uname -a
Linux cortex 2.6.32-ARCH #1 SMP PREEMPT Tue Feb 9 14:46:08 UTC 2010
i686 Intel(R) Core(TM)2 Duo CPU E4400 @ 2.00GHz GenuineIntel GNU/Linux
--
Camille Moncelier
http://devlife.org/
If Java had true garbage collection, most programs would
delete themselves upon execution.
--
To unsubscribe from this list: send the line "unsubscribe linux-fsdevel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
next reply other threads:[~2010-02-18 16:45 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-02-18 16:45 PiX [this message]
2010-02-18 16:50 ` [ext3] Changes to block device after an ext3 mount point has been remounted readonly Camille Moncelier
2010-02-18 21:41 ` Andreas Dilger
2010-02-19 7:38 ` Camille Moncelier
2010-02-22 22:32 ` Jan Kara
2010-02-22 23:05 ` Jan Kara
2010-02-22 23:09 ` Andreas Dilger
2010-02-23 8:42 ` Camille Moncelier
2010-02-23 13:55 ` Jan Kara
2010-02-24 16:01 ` Dmitry Monakhov
2010-02-24 16:26 ` Camille Moncelier
2010-02-24 16:59 ` Jan Kara
2010-02-24 16:56 ` Jan Kara
2010-03-02 9:34 ` Christoph Hellwig
2010-03-02 10:01 ` Dmitry Monakhov
2010-03-02 13:26 ` Jan Kara
2010-03-02 23:10 ` Joel Becker
2010-02-24 16:57 ` Eric Sandeen
2010-02-24 17:05 ` Jan Kara
2010-02-24 17:26 ` Dmitry Monakhov
2010-02-24 21:36 ` Jan Kara
2010-03-02 10:29 ` Nick Piggin
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=baaef4711002180845n29561ccif451fae62e49e520@mail.gmail.com \
--to=pix@devlife.org \
--cc=linux-fsdevel@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;
as well as URLs for NNTP newsgroup(s).