From: "Carlos E. R." <carlos.e.r@opensuse.org>
To: xfs@oss.sgi.com
Subject: Re: Ideas on unified real-ro mount option across all filesystems
Date: Thu, 17 Dec 2015 15:35:18 +0100 [thread overview]
Message-ID: <5672C826.2010901@opensuse.org> (raw)
In-Reply-To: <20151217032652.GD10582@birch.djwong.org>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On 2015-12-17 04:26, Darrick J. Wong wrote:
> On Wed, Dec 16, 2015 at 09:15:59PM -0600, Eric Sandeen wrote:
>> I have always interpreted it as simply "no user changes to the
>> filesystem," and that is clearly what the vfs does with the
>> flag...
>
> That ("-o ro means no user changes") has always been my
> understanding too. You /want/ the FS to replay the journal on an
> RO mount so that regular FS operation picks up the committed
> transactions.
That's my understanding, too, but after some point in time. It was
explained to me some years ago after I found out that a disk image
mounted read only was modified. The trick was to make the image '-w'.
I have the vague feeling that once I found a problem when a mount
failed or crashed when the image was ro.
Just a user view on this :-)
- --
Cheers / Saludos,
Carlos E. R.
(from 13.1 x86_64 "Bottle" at Telcontar)
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.22 (GNU/Linux)
iEYEARECAAYFAlZyyBsACgkQtTMYHG2NR9VDYACfRd6Zzd60JzX6LoW1F2K4fSai
OJAAoJXgLlcrlFZy1U2MzCBaQ4cz0EmP
=s8oq
-----END PGP SIGNATURE-----
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
next prev parent reply other threads:[~2015-12-17 14:35 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <567212DA.8050808@cn.fujitsu.com>
2015-12-17 3:15 ` Ideas on unified real-ro mount option across all filesystems Eric Sandeen
2015-12-17 3:26 ` Darrick J. Wong
2015-12-17 14:35 ` Carlos E. R. [this message]
2015-12-17 14:58 ` Carlos E. R.
2015-12-17 14:08 ` Karel Zak
2015-12-18 1:29 ` Qu Wenruo
2015-12-18 2:01 ` Christoph Anton Mitterer
2015-12-18 2:51 ` Eric Sandeen
2015-12-18 4:20 ` Christoph Anton Mitterer
2015-12-23 23:22 ` Stewart Smith
2015-12-26 22:53 ` Dave Chinner
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=5672C826.2010901@opensuse.org \
--to=carlos.e.r@opensuse.org \
--cc=xfs@oss.sgi.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