linux-btrfs.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Qu Wenruo <wqu@suse.de>
To: Remi Gauvin <remi@georgianit.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 15:22:21 +0800	[thread overview]
Message-ID: <964481b6-e761-8d0d-3ef1-cbe19dbfae9e@suse.de> (raw)
In-Reply-To: <aabbd673-fdc0-77dd-7e1e-1b5d1ed12bff@georgianit.com>


[-- Attachment #1.1: Type: text/plain, Size: 517 bytes --]



On 2019/2/12 下午3:20, Remi Gauvin wrote:
> 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?

Yes, just as btrfs usually does.

Thanks,
Qu


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

  reply	other threads:[~2019-02-12  7:22 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
2019-02-12  7:22   ` Qu Wenruo [this message]
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=964481b6-e761-8d0d-3ef1-cbe19dbfae9e@suse.de \
    --to=wqu@suse.de \
    --cc=linux-btrfs@vger.kernel.org \
    --cc=remi@georgianit.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).