From: Goffredo Baroncelli <kreijack@libero.it>
To: Chris Mason <clm@fb.com>
Cc: "1i5t5.duncan@cox.net" <1i5t5.duncan@cox.net>,
"linux-btrfs@vger.kernel.org" <linux-btrfs@vger.kernel.org>
Subject: Re: btrfs raid1 and btrfs raid10 arrays NOT REDUNDANT
Date: Sat, 04 Jan 2014 16:23:08 +0100 [thread overview]
Message-ID: <52C8275C.8010404@libero.it> (raw)
In-Reply-To: <1388847120.23513.21.camel@ret.masoncoding.com>
On 2014-01-04 15:51, Chris Mason wrote:
> I added mount -o degraded just because I wanted the admin to be notified
> of failures. Right now it's still the most reliable way to notify them,
> but I definitely agree we can do better.
I think that we should align us to what the others raid subsystem (md
and dm) do in these cases.
Reading the man page of mdadm, to me it seems that an array is
constructed even without some disks; the only requirement is the disks
have to be valid (i.e. not out of sync)
> Leaving it on all the time? I
> don't think this is a great long term solution, unless you are actively
> monitoring the system to make sure there are no failures.
Anyway mdadm has the "monitor" mode, which reports this kind of error.
>From mdadm man page:
"Follow or Monitor
Monitor one or more md devices and act on any state
changes. This is only meaningful for RAID1,
4, 5, 6, 10 or multipath arrays, as only these have
interesting state. RAID0 or Linear never
have missing, spare, or failed drives, so there is
nothing to monitor.
"
Best regards
GB
--
gpg @keyserver.linux.it: Goffredo Baroncelli (kreijackATinwind.it>
Key fingerprint BBF5 1610 0B64 DAC6 5F7D 17B2 0EDA 9B37 8B82 E0B5
next prev parent reply other threads:[~2014-01-04 15:32 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 [this message]
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
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=52C8275C.8010404@libero.it \
--to=kreijack@libero.it \
--cc=1i5t5.duncan@cox.net \
--cc=clm@fb.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 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.