All of lore.kernel.org
 help / color / mirror / Atom feed
From: Duncan <1i5t5.duncan@cox.net>
To: linux-btrfs@vger.kernel.org
Subject: Re: btrfs raid1 and btrfs raid10 arrays NOT REDUNDANT
Date: Sun, 5 Jan 2014 11:16:45 +0000 (UTC)	[thread overview]
Message-ID: <pan$c5d0$eef130d$a5ee78f5$e77e7cd9@cox.net> (raw)
In-Reply-To: 2354723.OENPHvUuC6@quad

Chris Samuel posted on Sun, 05 Jan 2014 20:20:26 +1100 as excerpted:

> On Sat, 4 Jan 2014 02:56:39 PM Chris Mason wrote:
> 
>> Seconded +ADs-)  We're really focused on nailing down these problems
>> instead of hiding behind the experimental flag.  I know we won't be
>> perfect overnight, but it's time to focus on production workloads.
> 
> Perhaps an option here is to remove the need to specify the degraded
> flag but if the filesystem notice that it is mounting a RAID array and
> would otherwise fail it then sets the degraded flag itself and carries
> on?
> 
> That way the fact it was degraded would be visible in /proc/mounts and
> could be detected with health check scripts like NRPE for icinga/nagios.
> 
> Looking at the code this would be in read_one_dev() in
> fs/btrfs/volumes.c ?

The idea I came up elsewhere was to mount read-only, with a dmesg to the 
effect that the filesystem was configured for a raid-level that the 
current number of devices couldn't support, so mount rw,degraded to 
accept that temporarily and to make changes, either by adding a new 
device to fill out the required number for the configured raid level, or 
by reducing the configured raid level to match reality.

The read-only mount would be better than not mounting at all, while 
preserving the "first, do no further harm" ideal, since mounted read-
only, the existing situation should at least remain stable.  It would 
also alert the admin to problems, with a reasonable log message saying 
how to fix them, while letting the admin at least access the filesystem 
in read-only mode, thereby giving him tools access to manage whatever 
maintenance tasks are necessary, should it be the rootfs.  The admin 
could then take the action they deemed appropriate, whether that was 
getting the data backed up, or mounting degraded,rw in ordered to either 
add a device and bring it back to functional or to rebalance to a lower 
data/metadata redundancy level due to lack of devices.

-- 
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:[~2014-01-05 11:17 UTC|newest]

Thread overview: 40+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-01-03 22:28 btrfs raid1 and btrfs raid10 arrays NOT REDUNDANT Jim Salter
2014-01-03 22:42 ` Emil Karlson
2014-01-03 22:43 ` Joshua Schüler
2014-01-03 22:56   ` Jim Salter
2014-01-03 23:04     ` Hugo Mills
2014-01-03 23:04     ` Joshua Schüler
2014-01-03 23:13       ` Jim Salter
2014-01-03 23:18         ` Hugo Mills
2014-01-03 23:25           ` Jim Salter
2014-01-03 23:32             ` Chris Murphy
2014-01-03 23:22         ` Chris Murphy
2014-01-04  6:10           ` Duncan
2014-01-04 11:20             ` Chris Samuel
2014-01-04 13:03               ` Duncan
2014-01-04 14:51             ` Chris Mason
2014-01-04 15:23               ` Goffredo Baroncelli
2014-01-04 20:08               ` Duncan
2014-01-04 21:22             ` Jim Salter
2014-01-05 11:01               ` Duncan
2014-01-03 23:19     ` Chris Murphy
     [not found]     ` <CAOjFWZ7zC3=4oH6=SBZA+PhZMrSK1KjxoRN6L2vqd=GTBKKTQA@mail.gmail.com>
2014-01-03 23:42       ` Jim Salter
2014-01-03 23:45         ` Jim Salter
2014-01-04  0:27         ` Chris Murphy
2014-01-04  2:59           ` Jim Salter
2014-01-04  5:57             ` Dave
2014-01-04 11:28               ` Chris Samuel
2014-01-04 14:56                 ` Chris Mason
2014-01-05  9:20                   ` Chris Samuel
2014-01-05 11:16                     ` Duncan [this message]
2014-01-04 19:18             ` Chris Murphy
2014-01-04 21:16               ` Jim Salter
2014-01-05 20:25                 ` Chris Murphy
2014-01-06 10:20                   ` Chris Samuel
2014-01-06 18:30                     ` Chris Murphy
2014-01-06 19:25                       ` Jim Salter
2014-01-06 22:05                         ` Chris Murphy
2014-01-06 22:24                           ` Jim Salter
2014-01-07  5:43                         ` Chris Samuel
2014-01-06 19:31                       ` correct way to rollback a root filesystem? Jim Salter
2014-01-07 11:55                         ` Sander

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$c5d0$eef130d$a5ee78f5$e77e7cd9@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.