From: Ed Tomlinson <edt@aei.ca>
To: Chris Mason <clm@fb.com>
Cc: <fdmanana@kernel.org>, <linux-btrfs@vger.kernel.org>,
Filipe Manana <fdmanana@suse.com>
Subject: Re: [GIT PULL] Btrfs bug fixes
Date: Wed, 01 Jul 2015 17:00:28 -0400 [thread overview]
Message-ID: <6080f1b0-4b14-4fe0-a01d-2df947782bb0@aei.ca> (raw)
In-Reply-To: <20150701172441.GG23627@ret.masoncoding.com>
Chris,
Have you looked at Omar Sandoval's
[PATCH v2 0/5] Btrfs: RAID 5/6 missing device scrub+replace
It would be really nice to have these when/if a disk dies... I
been running with them since v1 without issue.
Thanks
Ed Tomlinson
On Wednesday, July 1, 2015 1:24:41 PM EDT, Chris Mason wrote:
> On Tue, Jun 30, 2015 at 11:20:31PM +0100, fdmanana@kernel.org wrote:
>> From: Filipe Manana <fdmanana@suse.com>
>>
>> Hi Chris,
>>
>> Please consider the following changes (or a subset at your will in case
>> they are too many or too large) for the kernel 4.2 release. All these
>> patches have been available in the mailing list for at least 2 weeks. ...
>
> Thanks! These are queued along with a few others I pulled from the list,
> Mark's dedup fixes, and the ones Qu mentioned. Once it passes tests
> here I'll push out.
>
> -chris
> --
> To unsubscribe from this list: send the line "unsubscribe linux-btrfs" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
>
>
>
next prev parent reply other threads:[~2015-07-01 21:00 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-06-30 22:20 [GIT PULL] Btrfs bug fixes fdmanana
2015-07-01 17:24 ` Chris Mason
2015-07-01 21:00 ` Ed Tomlinson [this message]
-- strict thread matches above, loose matches on Subject: below --
2015-09-15 2:22 fdmanana
2015-09-15 11:49 ` Holger Hoffstätte
2015-09-15 12:58 ` Filipe Manana
2015-09-15 13:43 ` Holger Hoffstätte
2015-09-15 13:53 ` Josef Bacik
2015-09-15 14:07 ` 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=6080f1b0-4b14-4fe0-a01d-2df947782bb0@aei.ca \
--to=edt@aei.ca \
--cc=clm@fb.com \
--cc=fdmanana@kernel.org \
--cc=fdmanana@suse.com \
--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).