From: Marc Lehmann <schmorp@schmorp.de>
To: Zygo Blaxell <ce3g8jdj@umail.furryterror.org>
Cc: linux-btrfs@vger.kernel.org
Subject: Re: experiment: suboptimal behaviour with write errors and multi-device filesystems
Date: Sat, 2 May 2020 20:27:36 +0200 [thread overview]
Message-ID: <20200502182736.GE1069@schmorp.de> (raw)
In-Reply-To: <20200501033720.GF10769@hungrycats.org>
On Thu, Apr 30, 2020 at 11:37:20PM -0400, Zygo Blaxell <ce3g8jdj@umail.furryterror.org> wrote:
> > My concern is merely that btrfs stubbornly insists a completely missing
> > disk is totally fine to write to, essentially forever :)
>
> That's an administrator decision, but btrfs does currently lack the tool
> to implement the "remove the failing device" decision. A workaround is
> 'echo 1 > /sys/block/sdX/dev/delete'.
Ah, I forgot to mention, the kernel did this automatically in my
experiment (as I described - the device node was gone).
The problem is the upper layers (lvm/dm and btrfs) didn't react to this
- dm becaus eit leaves error handling to the fs, and btrfs, because it
didn't have error handling other than "ignore an continue".
--
The choice of a Deliantra, the free code+content MORPG
-----==- _GNU_ http://www.deliantra.net
----==-- _ generation
---==---(_)__ __ ____ __ Marc Lehmann
--==---/ / _ \/ // /\ \/ / schmorp@schmorp.de
-=====/_/_//_/\_,_/ /_/\_\
prev parent reply other threads:[~2020-05-02 18:27 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-26 12:46 experiment: suboptimal behaviour with write errors and multi-device filesystems Marc Lehmann
2020-04-28 6:19 ` Zygo Blaxell
2020-04-28 18:14 ` Marc Lehmann
2020-04-28 21:35 ` Zygo Blaxell
2020-05-01 1:55 ` Marc Lehmann
2020-05-01 3:37 ` Zygo Blaxell
2020-05-02 18:23 ` Marc Lehmann
2020-05-02 18:49 ` Remi Gauvin
2020-05-03 4:16 ` Zygo Blaxell
2020-05-02 18:27 ` Marc Lehmann [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=20200502182736.GE1069@schmorp.de \
--to=schmorp@schmorp.de \
--cc=ce3g8jdj@umail.furryterror.org \
--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).