linux-btrfs.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Rich Freeman <r-btrfs@thefreemanclan.net>
To: Suman C <schakrava@gmail.com>
Cc: Anand Jain <Anand.Jain@oracle.com>,
	linux-btrfs <linux-btrfs@vger.kernel.org>
Subject: Re: what is the best way to monitor raid1 drive failures?
Date: Tue, 14 Oct 2014 10:52:01 -0400	[thread overview]
Message-ID: <CAGfcS_nK5w+7Z70+5WMou-Z7HCVPaebFcPzOSKhGO8_=YN1oEQ@mail.gmail.com> (raw)
In-Reply-To: <CAPF83mtWrTRyfT34nNm7yjLDq+6uRegNJStkDK6+n_7fpmRTDQ@mail.gmail.com>

On Tue, Oct 14, 2014 at 10:48 AM, Suman C <schakrava@gmail.com> wrote:
>
> The new drive shows up as sdb. btrfs fi show still prints drive missing.
>
> mounted the filesystem with ro,degraded
>
> tried adding the "new" sdb drive which results in the following error.
> (-f because the new drive has a fs from past)
>
> # btrfs device add -f /dev/sdb /mnt2/raid1pool
> /dev/sdb is mounted
>
> Unless I am missing something, this looks like a bug.
>

You need to first run btrfs device delete missing /mnt2/raid1pool I
believe (missing is a keyword for a missing device in the array - if
the device were still present you could specify it by /dev/sdX).

--
Rich

  reply	other threads:[~2014-10-14 14:52 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-10-12 23:50 what is the best way to monitor raid1 drive failures? Suman C
2014-10-13  2:21 ` Anand Jain
2014-10-13 19:50   ` Suman C
2014-10-14  2:13     ` Anand Jain
2014-10-14 14:48       ` Suman C
2014-10-14 14:52         ` Rich Freeman [this message]
2014-10-14 15:05           ` Suman C
2014-10-14 19:15         ` Chris Murphy
2014-10-14 20:11           ` Suman C
2014-10-24 16:13             ` Chris Murphy
2014-10-14 22:00         ` Duncan
2014-10-15  4:11         ` Anand Jain

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='CAGfcS_nK5w+7Z70+5WMou-Z7HCVPaebFcPzOSKhGO8_=YN1oEQ@mail.gmail.com' \
    --to=r-btrfs@thefreemanclan.net \
    --cc=Anand.Jain@oracle.com \
    --cc=linux-btrfs@vger.kernel.org \
    --cc=schakrava@gmail.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 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).