From: Duncan <1i5t5.duncan@cox.net>
To: linux-btrfs@vger.kernel.org
Subject: Re: raid1: cannot add disk to replace faulty because can only mount fs as read-only.
Date: Fri, 3 Feb 2017 09:35:22 +0000 (UTC) [thread overview]
Message-ID: <pan$d2936$66aa094e$a8f4cf32$a805f7b0@cox.net> (raw)
In-Reply-To: 7cb699fd-44a7-d8eb-e492-c448f67b0eac@gmail.com
Austin S. Hemmelgarn posted on Thu, 02 Feb 2017 07:49:50 -0500 as
excerpted:
> I think (although I'm not sure about it) that this:
> http://www.spinics.net/lists/linux-btrfs/msg47283.html is the first
> posting of the patch series.
Yes. That looks like it. Thanks.
--
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
prev parent reply other threads:[~2017-02-03 9:35 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-24 18:57 raid1: cannot add disk to replace faulty because can only mount fs as read-only Hans Deragon
2017-01-24 19:48 ` Adam Borowski
[not found] ` <W75Sc6PDCBok7W75TcCgc7@videotron.ca>
2017-01-27 16:47 ` Hans Deragon
2017-01-27 20:03 ` Austin S. Hemmelgarn
2017-01-27 20:28 ` Adam Borowski
2017-01-28 9:17 ` Andrei Borzenkov
2017-01-30 12:18 ` Austin S. Hemmelgarn
[not found] ` <YAvBcoM9EImXYYAvCcegSf@videotron.ca>
2017-02-01 2:51 ` Hans Deragon
2017-02-01 5:23 ` Duncan
2017-02-01 11:55 ` Adam Borowski
2017-02-01 22:48 ` Duncan
2017-02-02 12:49 ` Austin S. Hemmelgarn
2017-02-02 14:25 ` Adam Borowski
2017-02-02 15:06 ` Austin S. Hemmelgarn
[not found] ` <ZIyPcL4cW36fIZIyQcB9Hs@videotron.ca>
2017-02-08 3:21 ` Hans Deragon
2017-02-08 12:50 ` Austin S. Hemmelgarn
2017-02-08 13:46 ` Tomasz Torcz
2017-02-08 19:06 ` Austin S. Hemmelgarn
2017-02-03 9:35 ` Duncan [this message]
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$d2936$66aa094e$a8f4cf32$a805f7b0@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).