Thread (11 messages) 11 messages, 9 authors, 2015-12-26

Re: Ideas on unified real-ro mount option across all filesystems

From: Carlos E. R. <hidden>
Date: 2015-12-17 14:35:25

-----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:
quoted
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
Keyboard shortcuts
hback out one level
jnext message in thread
kprevious message in thread
ldrill in
Escclose help / fold thread tree
?toggle this help