From: Pavel Machek <pavel@ucw.cz>
To: Mark Lord <lkml@rtr.ca>
Cc: Andrew Morton <akpm@linux-foundation.org>,
Stephen Tweedie <sct@redhat.com>, "Theodore Ts'o" <tytso@mit.edu>,
Linux Kernel <linux-kernel@vger.kernel.org>
Subject: Re: ext3fs: umount+sync not enough to guarantee metadata-on-disk
Date: Sun, 10 Jun 2007 18:27:47 +0000 [thread overview]
Message-ID: <20070610182746.GA4272@ucw.cz> (raw)
In-Reply-To: <46682BE7.6080802@rtr.ca>
Hi!
> >Did this succeed? If the application is still
> >truncating that file, the
> >umount should have failed.
>
> Actually, what I expect to happen is for the remount,ro
> to block until the file deletion completes. But it
> doesn't.
>
> Once a f/s is read-only, there should be NO writing to
> it. Right?
Linux happily writes to filesystems mounted read-only. It will replay
journal on them.
Pavel
--
(english) http://www.livejournal.com/~pavelmachek
(cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html
next prev parent reply other threads:[~2007-06-12 14:41 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-06-07 13:44 ext3fs: umount+sync not enough to guarantee metadata-on-disk Mark Lord
2007-06-07 15:41 ` Andrew Morton
2007-06-07 16:01 ` Mark Lord
2007-06-07 17:09 ` Stephen C. Tweedie
2007-06-10 18:27 ` Pavel Machek [this message]
2007-06-12 15:15 ` Stephen C. Tweedie
2007-06-14 19:01 ` Phillip Susi
2007-06-07 16:11 ` Chuck Ebbert
2007-06-07 19:45 ` Andrew Morton
2007-06-07 21:38 ` Mark Lord
2007-06-07 22:04 ` Andrew Morton
2007-06-08 14:51 ` Mark Lord
2007-06-09 2:58 ` Mark Lord
2007-06-11 11:14 ` Jan Kara
2007-06-11 22:47 ` Mark Lord
2007-06-12 10:00 ` Jan Kara
2007-06-07 21:43 ` Mark Lord
2007-06-10 18:31 ` Pavel Machek
2007-06-11 11:05 ` Jan Kara
2007-06-11 22:46 ` Mark Lord
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=20070610182746.GA4272@ucw.cz \
--to=pavel@ucw.cz \
--cc=akpm@linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lkml@rtr.ca \
--cc=sct@redhat.com \
--cc=tytso@mit.edu \
/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