linux-btrfs.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Duncan <1i5t5.duncan@cox.net>
To: linux-btrfs@vger.kernel.org
Subject: Re: raid1: cannot add disk to replace faulty because can only mount fs as read-only.
Date: Wed, 1 Feb 2017 05:23:16 +0000 (UTC)	[thread overview]
Message-ID: <pan$be2e$8a233bb0$f63eb0cb$d3413db@cox.net> (raw)
In-Reply-To: a5262907-06f2-2c6f-d23a-2703b10429b7@deragon.biz

Hans Deragon posted on Tue, 31 Jan 2017 21:51:22 -0500 as excerpted:

> But the current scenario makes it difficult for me to put redundancy
> back into service!  How much time did I waited until I find the mailing
> list, subscribe to it, post my email and get an answer?  Wouldn't it be
> better if the user could actually add the disk at anytime, mostly ASAP?
> 
> And to fix this, I have to learn how to patch and compile the kernel.  I
> have not done this since the beginning of the century.  More delays,
> more risk added to the system (what if I compile the kernel with the
> wrong parameters?).

Comes with the territory.  Note that nobody with any knowledge of btrfs 
is claiming it's fully stable and mature, as you seem to expect.  Rather, 
the state is explicitly stabilizing, NOT fully stable and mature, backups 
very strongly recommended as there's a real possibility you'll need to 
use them, running current kernels and keeping up with the list if you 
choose to run btrfs strongly recommended, etc.

The patch fixing the problem and making return from degraded not the one-
shot thing it tends to be now will eventually be merged, but known 
problems, with or without patches available to fix them, are just part of 
running a still stabilizing filesystem, and if you choose to do so and 
run into those problems, you have the choice of waiting for a fix to make 
its way to you, or if a patch is already available, rebuilding with that 
patch.

Otherwise, you simply mkfs and restore from the backup that was strongly 
recommended if the data isn't of only trivial value in the first place.  
If you didn't have that backup, and the data was stored on a still 
stabilizing btrfs, well then, you defined it as of only trivial value by 
the inaction of not having that backup while running a filesystem known 
to be still stabilizing, didn't you?

Otherwise, run a filesystem more appropriately stable and mature 
according to your needs, as btrfs in its current state apparently doesn't 
meet those needs.

-- 
Duncan - List replies preferred.   No HTML msgs.
"Every nonfree program has a lord, a master --
and if you use the program, he is your master."  Richard Stallman


  reply	other threads:[~2017-02-01  5:23 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-01-24 18:57 raid1: cannot add disk to replace faulty because can only mount fs as read-only Hans Deragon
2017-01-24 19:48 ` Adam Borowski
     [not found] ` <W75Sc6PDCBok7W75TcCgc7@videotron.ca>
2017-01-27 16:47   ` Hans Deragon
2017-01-27 20:03     ` Austin S. Hemmelgarn
2017-01-27 20:28       ` Adam Borowski
2017-01-28  9:17       ` Andrei Borzenkov
2017-01-30 12:18         ` Austin S. Hemmelgarn
     [not found]         ` <YAvBcoM9EImXYYAvCcegSf@videotron.ca>
2017-02-01  2:51           ` Hans Deragon
2017-02-01  5:23             ` Duncan [this message]
2017-02-01 11:55               ` Adam Borowski
2017-02-01 22:48                 ` Duncan
2017-02-02 12:49                   ` Austin S. Hemmelgarn
2017-02-02 14:25                     ` Adam Borowski
2017-02-02 15:06                       ` Austin S. Hemmelgarn
     [not found]                       ` <ZIyPcL4cW36fIZIyQcB9Hs@videotron.ca>
2017-02-08  3:21                         ` Hans Deragon
2017-02-08 12:50                           ` Austin S. Hemmelgarn
2017-02-08 13:46                             ` Tomasz Torcz
2017-02-08 19:06                               ` Austin S. Hemmelgarn
2017-02-03  9:35                     ` Duncan

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='pan$be2e$8a233bb0$f63eb0cb$d3413db@cox.net' \
    --to=1i5t5.duncan@cox.net \
    --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).