From: Austin S Hemmelgarn <ahferroin7@gmail.com>
To: Lennart Poettering <lennart@poettering.net>,
Harald Hoyer <harald@redhat.com>
Cc: linux-btrfs@vger.kernel.org, Kay Sievers <kay@vrfy.org>
Subject: Re: Extend BTRFS_IOC_DEVICES_READY for degraded RAID
Date: Mon, 05 Jan 2015 07:08:24 -0500 [thread overview]
Message-ID: <54AA7EB8.2000100@gmail.com> (raw)
In-Reply-To: <20150105113147.GA18350@gardel-login>
[-- Attachment #1: Type: text/plain, Size: 942 bytes --]
On 2015-01-05 06:31, Lennart Poettering wrote:
> On Mon, 05.01.15 10:46, Harald Hoyer (harald@redhat.com) wrote:
>
>> We have BTRFS_IOC_DEVICES_READY to report, if all devices are present, so that
>> a udev rule can report ID_BTRFS_READY and SYSTEMD_READY.
>>
>> I think we need a third state here for a degraded RAID, which can be mounted,
>> but should only after a certain timeout/kernel command line params.
>>
>> We also have to rethink how to handle the udev DB update for the change of the
>> state. incomplete -> degraded -> complete
>
> I am not convinced that automatically booting degraded arrays would be
> a good idea. Instead, requiring one manual step before booting a
> degraded array sounds OK to me.
>
> Lennart
>
I can think of half a dozen use cases where it is better to
automatically mount degraded and send a notification that this happened
than to refuse to mount without manual intervention.
[-- Attachment #2: S/MIME Cryptographic Signature --]
[-- Type: application/pkcs7-signature, Size: 2455 bytes --]
next prev parent reply other threads:[~2015-01-05 12:08 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-01-05 9:46 Extend BTRFS_IOC_DEVICES_READY for degraded RAID Harald Hoyer
2015-01-05 11:31 ` Lennart Poettering
2015-01-05 12:08 ` Austin S Hemmelgarn [this message]
2015-01-05 16:36 ` Goffredo Baroncelli
2015-01-05 17:02 ` Austin S Hemmelgarn
2015-01-05 17:57 ` Goffredo Baroncelli
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=54AA7EB8.2000100@gmail.com \
--to=ahferroin7@gmail.com \
--cc=harald@redhat.com \
--cc=kay@vrfy.org \
--cc=lennart@poettering.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).