From: Roman Mamedov <rm@romanrm.net>
To: Phil Turmel <philip@turmel.org>
Cc: Matt Callaghan <matt_callaghan@sympatico.ca>, linux-raid@vger.kernel.org
Subject: Re: mdadm RAID6 "active" with spares and failed disks; need help
Date: Sat, 28 Mar 2015 15:11:42 +0500 [thread overview]
Message-ID: <20150328151142.11db8c9a@natsu> (raw)
In-Reply-To: <55160B0A.1090405@turmel.org>
[-- Attachment #1: Type: text/plain, Size: 607 bytes --]
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.
--
With respect,
Roman
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 198 bytes --]
next prev parent reply other threads:[~2015-03-28 10:11 UTC|newest]
Thread overview: 12+ 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 [this message]
2015-03-28 15:11 ` Read-only mounts (was mdadm RAID6 "active" with spares and failed disks; need help) Phil Turmel
[not found] ` <55161943.1090206@sympatico.ca>
[not found] ` <BLU436-SMTP135A84B36120ACD11B2783D81F70@phx.gbl>
2015-03-28 17:40 ` mdadm RAID6 "active" with spares and failed disks; need help Phil Turmel
2015-01-06 14:16 Matt Callaghan
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=20150328151142.11db8c9a@natsu \
--to=rm@romanrm.net \
--cc=linux-raid@vger.kernel.org \
--cc=matt_callaghan@sympatico.ca \
--cc=philip@turmel.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).