From: Duncan <1i5t5.duncan@cox.net>
To: linux-btrfs@vger.kernel.org
Subject: Re: What is the vision for btrfs fs repair?
Date: Thu, 9 Oct 2014 13:49:27 +0000 (UTC) [thread overview]
Message-ID: <pan$be94c$47b1139c$477c562b$8f545371@cox.net> (raw)
In-Reply-To: 54368B1E.4040901@gmail.com
Austin S Hemmelgarn posted on Thu, 09 Oct 2014 09:18:22 -0400 as
excerpted:
> On 2014-10-09 08:34, Duncan wrote:
>> The only way a read-only
>> mount should be writable is if it's mounted (bind-mounted or
>> btrfs-subvolume-mounted) read-write elsewhere, and the write occurs to
>> that mount, not the read-only mounted location.
> In theory yes, but there are caveats to this, namely:
> * atime updates still happen unless you have mounted the fs with noatime
I've been mounting noatime for well over a decade now, exactly due to
such problems. But I believe at least /some/ filesystems are truly read-
only when they're mounted as such, and atime updates don't happen on them.
These days I actually apply a patch that changes the default relatime to
noatime, so I don't even have to have it in my mount-options. =:^)
> * The superblock gets updated if there are 'any' writes
Yeah. At least in theory, there shouldn't be, however. As I said, in
theory, even journal replay and orphan delete shouldn't hit media, altho
handling it in memory and dirtying the cache, so if the filesystem is
ever remounted read-write they get written, is reasonable.
> * The free space cache 'might' be updated if there are any writes
Makes sense. But of course that's what I'm arguing, there shouldn't /be/
any writes. Read-only should mean exactly that, don't touch media,
period.
I remember at one point activating an mdraid1 degraded, read-only, just a
single device of the 4-way raid1 I was running at the time, to recover
data from it after the system it was running in died. The idea was don't
write to the device at all, because I was still testing the new system,
and in case I decided to try to reassemble the raid at some point. Read-
only really NEEDS to be read-only, under such conditions.
Similarly for forensic examination, of course. If there's a write, any
write, it's evidence tampering. Read-only needs to MEAN read-only!
--
Duncan - List replies preferred. No HTML msgs.
"Every nonfree program has a lord, a master --
and if you use the program, he is your master." Richard Stallman
next prev parent reply other threads:[~2014-10-09 13:49 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-08 19:11 What is the vision for btrfs fs repair? Eric Sandeen
2014-10-09 11:29 ` Austin S Hemmelgarn
2014-10-09 11:53 ` Duncan
2014-10-09 11:55 ` Hugo Mills
2014-10-09 12:07 ` Austin S Hemmelgarn
2014-10-09 12:12 ` Hugo Mills
2014-10-09 12:32 ` Austin S Hemmelgarn
[not found] ` <107Y1p00G0wm9Bl0107vjZ>
2014-10-09 12:34 ` Duncan
2014-10-09 13:18 ` Austin S Hemmelgarn
2014-10-09 13:49 ` Duncan [this message]
2014-10-09 15:44 ` Eric Sandeen
[not found] ` <0zvr1p0162Q6ekd01zvtN0>
2014-10-09 12:42 ` Duncan
2014-10-10 1:58 ` Chris Murphy
2014-10-10 3:20 ` Duncan
2014-10-10 10:53 ` Bob Marley
2014-10-10 10:59 ` Roman Mamedov
2014-10-10 11:12 ` Bob Marley
2014-10-10 15:18 ` cwillu
2014-10-10 14:37 ` Chris Murphy
2014-10-10 17:43 ` Bob Marley
2014-10-10 17:53 ` Bardur Arantsson
2014-10-10 19:35 ` Austin S Hemmelgarn
2014-10-10 22:05 ` Eric Sandeen
2014-10-13 11:26 ` Austin S Hemmelgarn
2014-10-12 10:14 ` Martin Steigerwald
2014-10-12 23:59 ` Duncan
2014-10-13 11:37 ` Austin S Hemmelgarn
2014-10-13 11:48 ` Rich Freeman
2014-10-11 7:29 ` Goffredo Baroncelli
2014-11-17 20:55 ` Phillip Susi
2014-10-12 10:06 ` Martin Steigerwald
2014-10-12 10:17 ` Martin Steigerwald
2014-10-13 21:09 ` Josef Bacik
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='pan$be94c$47b1139c$477c562b$8f545371@cox.net' \
--to=1i5t5.duncan@cox.net \
--cc=linux-btrfs@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).