linux-btrfs.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Anand Jain <anand.jain@oracle.com>
To: Qu Wenruo <quwenruo@cn.fujitsu.com>,
	Qu Wenruo <quwenruo.btrfs@gmx.com>,
	linux-btrfs@vger.kernel.org
Subject: Re: [PATCH 2/2] btrfs: Remove unneeded missing device number check
Date: Fri, 18 Sep 2015 14:45:11 +0800	[thread overview]
Message-ID: <55FBB2F7.4040402@oracle.com> (raw)
In-Reply-To: <55FB71A8.3000004@cn.fujitsu.com>


Hi Qu,

  Thanks for the comments on patch [1].

> For example, if one use single metadata for 2 disks,
 > and each disk has one metadata chunk on it.

  how that can be achieved ?

> One device got missing later.

  it would surely depend on which one of the device ? (initial only 
devid 1 mountable, with other missing)


Thanks, Anand

> Then your patch will allow the fs to be mounted as rw, even some tree
> block can be in the missing device.
> For RO case, it won't be too dangerous, but if we mounted it as RW, who
> knows what will happen.
> (Normal tree COW thing should fail before real write, but I'm not sure
> about other RW operation like scrub/replace/balance and others)
>
> And I think that's the original design concept behind the old missing
> device number check, and it's not a bad idea to follow it anyway.
>
> For the patch size, I find a good idea to handle it, and should make the
> patch(set) size below 200 lines.
>
> Further more, it's even possible to make btrfs change mount option to
> degraded for runtime device missing.
>
> Thanks,
> Qu
>>
>>   I tried to break both the approaches (this patch set and [1]) but I
>> wasn't successful. sorry if I am missing something.
>>
>> Thanks, Anand
>>
>> [1] [PATCH 23/23] Btrfs: allow -o rw,degraded for single group profile




  reply	other threads:[~2015-09-18  6:46 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-09-16  3:43 [PATCH 1/2] btrfs: Do per-chunk degrade mode check at mount time Qu Wenruo
2015-09-16  3:43 ` [PATCH 2/2] btrfs: Remove unneeded missing device number check Qu Wenruo
2015-09-17  9:43   ` Anand Jain
2015-09-17 10:01     ` Qu Wenruo
2015-09-18  1:47       ` Anand Jain
2015-09-18  2:06         ` Qu Wenruo
2015-09-18  6:45           ` Anand Jain [this message]
2015-09-20  0:31             ` Qu Wenruo
2015-09-20  5:37               ` Anand Jain
2015-09-21  2:09                 ` Qu Wenruo
2015-09-17  1:48 ` [PATCH 1/2] btrfs: Do per-chunk degrade mode check at mount time Qu Wenruo
2015-09-17  9:37   ` Anand Jain

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=55FBB2F7.4040402@oracle.com \
    --to=anand.jain@oracle.com \
    --cc=linux-btrfs@vger.kernel.org \
    --cc=quwenruo.btrfs@gmx.com \
    --cc=quwenruo@cn.fujitsu.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).