From: Phil Turmel <philip@turmel.org>
To: Roman Mamedov <rm@romanrm.net>
Cc: Matt Callaghan <matt_callaghan@sympatico.ca>, linux-raid@vger.kernel.org
Subject: Read-only mounts (was mdadm RAID6 "active" with spares and failed disks; need help)
Date: Sat, 28 Mar 2015 11:11:29 -0400 [thread overview]
Message-ID: <5516C4A1.9030604@turmel.org> (raw)
In-Reply-To: <20150328151142.11db8c9a@natsu>
On 03/28/2015 06:11 AM, Roman Mamedov wrote:
> On Fri, 27 Mar 2015 21:59:38 -0400
> Phil Turmel <philip@turmel.org> wrote:
>
>> I read through this. Given all of the destructive actions you took, I
>> am doubtful you will ever get your data. Like mounting "readonly".
>> That gives you a readonly filesystem, but it writes to the device.
>> Possibly a great deal if there's a journal to replay.
>
> Are you sure, which FS does that? I remember some discussion on FS lists
> (Btrfs?), and IIRC the consensus and the implemented behavior was that the
> device shouldn't ever be touched with writes on RO mounts, no matter what.
I remember people being burned by it with ext3/4 a couple years ago.
Which is why all of the array disaster recoveries I've helped with
called for fsck -n to verify a reconstruction attempt, not a mount -o ro.
I will set up a small VM and see what recent kernels do.
Phil
next prev parent reply other threads:[~2015-03-28 15:11 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <54ABEE54.6020707@sympatico.ca>
2015-01-07 13:34 ` mdadm RAID6 "active" with spares and failed disks; need help Matt Callaghan
2015-01-11 20:26 ` Matt Callaghan
2015-01-11 23:22 ` Valentijn Sessink
2015-01-12 16:35 ` Wols Lists
2015-01-21 0:34 ` Matt Callaghan
2015-01-22 9:47 ` Valentijn
2015-03-27 23:48 ` Matt Callaghan
2015-03-28 1:59 ` Phil Turmel
2015-03-28 10:11 ` Roman Mamedov
2015-03-28 15:11 ` Phil Turmel [this message]
[not found] ` <55161943.1090206@sympatico.ca>
[not found] ` <BLU436-SMTP135A84B36120ACD11B2783D81F70@phx.gbl>
2015-03-28 17:40 ` Phil Turmel
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=5516C4A1.9030604@turmel.org \
--to=philip@turmel.org \
--cc=linux-raid@vger.kernel.org \
--cc=matt_callaghan@sympatico.ca \
--cc=rm@romanrm.net \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.