linux-btrfs.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Remi Gauvin <remi@georgianit.com>
To: Qu Wenruo <wqu@suse.com>, linux-btrfs@vger.kernel.org
Subject: Re: [PATCH RFC] btrfs: Don't create SINGLE or DUP chunks for degraded rw mount
Date: Tue, 12 Feb 2019 02:20:51 -0500	[thread overview]
Message-ID: <aabbd673-fdc0-77dd-7e1e-1b5d1ed12bff@georgianit.com> (raw)
In-Reply-To: <20190212070319.30619-1-wqu@suse.com>


[-- Attachment #1.1.1: Type: text/plain, Size: 400 bytes --]

On 2019-02-12 2:03 a.m., Qu Wenruo wrote:

> So we only need to consider missing devices as writable, and calculate
> our chunk allocation profile with missing devices too.
> 
> Then every thing should work as expected, without annoying SINGLE/DUP
> chunks blocking later degraded mount.
> 
>

Does this mean you would rely on scrub/CSUM to repair the missing data
if device is restored?

[-- Attachment #1.1.2: remi.vcf --]
[-- Type: text/x-vcard, Size: 203 bytes --]

begin:vcard
fn:Remi Gauvin
n:Gauvin;Remi
org:Georgian Infotech
adr:;;3-51 Sykes St. N.;Meaford;ON;N4L 1X3;Canada
email;internet:remi@georgianit.com
tel;work:226-256-1545
version:2.1
end:vcard


[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 473 bytes --]

  reply	other threads:[~2019-02-12  7:20 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-02-12  7:03 [PATCH RFC] btrfs: Don't create SINGLE or DUP chunks for degraded rw mount Qu Wenruo
2019-02-12  7:20 ` Remi Gauvin [this message]
2019-02-12  7:22   ` Qu Wenruo
2019-02-12  7:43     ` Remi Gauvin
2019-02-12  7:47       ` Qu Wenruo
2019-02-12  7:55         ` Remi Gauvin
2019-02-12  7:57           ` Qu Wenruo
2019-02-12 18:42         ` Andrei Borzenkov
2019-02-12 19:09           ` Remi Gauvin
2019-02-13  0:44           ` Qu Wenruo
     [not found] <173bc320-4d67-6752-86cb-119dc9fb9a69@dial.pipex.com>
2021-02-21  9:36 ` tai63

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=aabbd673-fdc0-77dd-7e1e-1b5d1ed12bff@georgianit.com \
    --to=remi@georgianit.com \
    --cc=linux-btrfs@vger.kernel.org \
    --cc=wqu@suse.com \
    /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).