From: Roman Mamedov <rm@romanrm.net>
To: Stefan Behrens <sbehrens@giantdisaster.de>
Cc: Wang Shilong <wangsl.fnst@cn.fujitsu.com>,
Ilya Dryomov <idryomov@gmail.com>,
linux-btrfs@vger.kernel.org,
Chris Mason <chris.mason@fusionio.com>
Subject: Re: [PATCH] Btrfs: disallow 'btrfs {balance,replace} cancel' on ro mounts
Date: Fri, 11 Oct 2013 15:35:46 +0600 [thread overview]
Message-ID: <20131011153546.424d69c4@natsu> (raw)
In-Reply-To: <5257C378.1060507@giantdisaster.de>
[-- Attachment #1: Type: text/plain, Size: 965 bytes --]
On Fri, 11 Oct 2013 11:23:04 +0200
Stefan Behrens <sbehrens@giantdisaster.de> wrote:
> On Fri, 11 Oct 2013 09:13:24 +0800, Wang Shilong wrote:
> > On 10/11/2013 01:40 AM, Ilya Dryomov wrote:
> >
> > I have a question in my mind.
> >
> > Can we reach a state that there is operation in progress when filesystem
> > has been readonly?If we do cancel operations on a ro filesystem, we should
> > get "No operations in progress" .
>
> Well, it's arguable what ro means. No write to the devices at all?
If I had an FS image and mounted it as -o loop,ro I'd simply expect md5sum of
that image to match before mount and after unmount, i.e. no writes at all.
Really, how can one argue with what "read only" means? If it will mean
something else than a complete absence of writes, then how can we mount
devices or FS images to do forensics, etc? Or do a recovery from a difficult
corruption or try to debug an FS crash.
--
With respect,
Roman
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 198 bytes --]
next prev parent reply other threads:[~2013-10-11 9:46 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-10-10 17:40 [PATCH] Btrfs: disallow 'btrfs {balance,replace} cancel' on ro mounts Ilya Dryomov
2013-10-11 1:13 ` Wang Shilong
2013-10-11 9:23 ` Stefan Behrens
2013-10-11 9:28 ` Remco Hosman - Yerf-IT
2013-10-11 9:39 ` Ilya Dryomov
2013-10-11 9:35 ` Roman Mamedov [this message]
2013-10-11 9:55 ` Hugo Mills
2013-10-11 9:36 ` Ilya Dryomov
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=20131011153546.424d69c4@natsu \
--to=rm@romanrm.net \
--cc=chris.mason@fusionio.com \
--cc=idryomov@gmail.com \
--cc=linux-btrfs@vger.kernel.org \
--cc=sbehrens@giantdisaster.de \
--cc=wangsl.fnst@cn.fujitsu.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;
as well as URLs for NNTP newsgroup(s).