From: Austin S Hemmelgarn <ahferroin7@gmail.com>
To: Chris Murphy <lists@colorremedies.com>
Cc: Qu Wenruo <quwenruo.btrfs@gmx.com>,
Erkki Seppala <flux-btrfs@inside.org>,
Btrfs BTRFS <linux-btrfs@vger.kernel.org>
Subject: Re: RAID1 storage server won't boot with one disk missing
Date: Tue, 22 Sep 2015 15:45:05 -0400 [thread overview]
Message-ID: <5601AFC1.8070006@gmail.com> (raw)
In-Reply-To: <CAJCQCtSK0AyjS8WX2V0K6nMgM3AmhFjTT6s5GcPF8EW8eKFN9Q@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 916 bytes --]
On 2015-09-22 14:35, Chris Murphy wrote:
> On Tue, Sep 22, 2015 at 7:21 AM, Austin S Hemmelgarn
> <ahferroin7@gmail.com> wrote:
>
>> It's not a bad idea, except that it changes established usage, and there are
>> probably some people out there who depend on the current behavior. If we do
>> go that way, mount needs to spit out a big obnoxious warning (as in, not
>> through dmesg or mount options, but directly on stderr) if the filesystem
>> gets mounted degraded automatically.
>
> Definitely there needs to be a user space message. Even now when
> trying to mount a volume with a missing device without -o degraded the
> generic fs type unrecognized message is misleading.
I agree that it's confusing for many users, but from the point of view
of someone who's been doing system administration for a few years, the
'or incorrect mount options' bit does kind of make sense given the context.
[-- Attachment #2: S/MIME Cryptographic Signature --]
[-- Type: application/pkcs7-signature, Size: 3019 bytes --]
next prev parent reply other threads:[~2015-09-22 19:45 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-09-16 23:56 RAID1 storage server won't boot with one disk missing erpo41
2015-09-17 15:18 ` Anand Jain
2015-09-17 15:42 ` Chris Murphy
2015-09-17 17:00 ` Goffredo Baroncelli
2015-09-17 19:02 ` Roman Mamedov
2015-09-17 20:18 ` Chris Murphy
2015-09-18 13:29 ` Austin S Hemmelgarn
2015-09-21 20:00 ` Erkki Seppala
2015-09-18 1:36 ` Duncan
2015-09-18 3:02 ` Gareth Pye
2015-09-21 20:35 ` Erkki Seppala
2015-09-22 5:12 ` Duncan
2015-09-22 11:32 ` Austin S Hemmelgarn
2015-09-22 12:51 ` Qu Wenruo
2015-09-22 13:21 ` Austin S Hemmelgarn
2015-09-22 18:35 ` Chris Murphy
2015-09-22 19:45 ` Austin S Hemmelgarn [this message]
2015-09-17 15:26 ` Chris Murphy
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=5601AFC1.8070006@gmail.com \
--to=ahferroin7@gmail.com \
--cc=flux-btrfs@inside.org \
--cc=linux-btrfs@vger.kernel.org \
--cc=lists@colorremedies.com \
--cc=quwenruo.btrfs@gmx.com \
/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.