From: Anand Jain <anand.jain@oracle.com>
To: kreijack@inwind.it
Cc: linux-btrfs@vger.kernel.org, Liu Bo <bo.li.liu@oracle.com>
Subject: Re: [PATCH v2] btrfs: handle dynamically reappearing missing device
Date: Mon, 4 Dec 2017 15:09:42 +0800 [thread overview]
Message-ID: <c1b50109-1e43-e341-9502-d08d3962b5b8@oracle.com> (raw)
In-Reply-To: <73ef4477-0497-fe24-ae17-5c4c08992c9c@libero.it>
> [..] would be better an explicit user intervention instead of an automatic one ?
What is the user intervention method steps that you have in mind ?
Just curious. Pls remember downtime is not a choice of recovery
from this context which means FS should be available for the
applications to perform read/write.
-o remount was one this which I had skipped for sometime as
theoretically it can't solve the problem (to bring back missing
device) as well, but now I have verified it, it won't.
There is no record of what is the original idea to perform this
basic volume manager step.
Thanks, Anand
prev parent reply other threads:[~2017-12-04 7:09 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-12 10:56 [PATCH] btrfs: handle dynamically reappearing missing device Anand Jain
2017-11-15 7:38 ` kbuild test robot
2017-11-15 10:18 ` Anand Jain
2017-11-16 19:08 ` Nikolay Borisov
2017-11-17 7:46 ` Anand Jain
2017-11-16 23:28 ` Liu Bo
2017-11-17 11:53 ` Anand Jain
2017-11-28 22:52 ` Liu Bo
2017-11-17 12:36 ` [PATCH v2] " Anand Jain
2017-11-18 13:52 ` Goffredo Baroncelli
2017-11-20 8:19 ` Anand Jain
2017-11-20 19:28 ` Goffredo Baroncelli
2017-11-20 21:14 ` Anand Jain
2017-12-04 7:09 ` Anand Jain [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=c1b50109-1e43-e341-9502-d08d3962b5b8@oracle.com \
--to=anand.jain@oracle.com \
--cc=bo.li.liu@oracle.com \
--cc=kreijack@inwind.it \
--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).