All of lore.kernel.org
 help / color / mirror / Atom feed
From: Anand Jain <anand.jain@oracle.com>
To: Duncan <1i5t5.duncan@cox.net>, linux-btrfs@vger.kernel.org
Subject: Re: RAID5 Unable to remove Failing HD
Date: Tue, 19 Apr 2016 17:13:04 +0800	[thread overview]
Message-ID: <5715F6A0.7030707@oracle.com> (raw)
In-Reply-To: <pan$d96e4$2cb56bbb$1d5f6612$721cfc21@cox.net>


>> # btrfs device delete 3 /mnt/store/
>> ERROR: device delete by id failed: Inappropriate ioctl for device
>>
>> Were the patch sets above for btrfs-progs or for the kernel ?
>
> Looks like you're primarily interested in the concern2 patches, device
> delete by devid.
>
> A quick search of the list back-history reveals that an updated patch
> set, 00/15 now (look for [PATCH 00/15] Device delete by id ), was posted
> by dserba on the 15th of February.  It was the kernel patches and was
> slated for the kernel 4.6 dev cycle.  However, the patch set was pulled
> at that time due to test failures, tho they were suspected to actually be
> from something else.

  Thanks Duncan. Yep the reported issue did not point to any
  of the patch in that set. But I am keeping a tab open for
  new users /test cases, anything that is found will help.

  By the way, For Lionel issue, delete missing should work ?
  which does not need any additional patch.

Thanks, Anand


  reply	other threads:[~2016-04-19  9:13 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-02-10  7:17 RAID5 Unable to remove Failing HD Rene Castberg
2016-02-10  9:00 ` Anand Jain
     [not found]   ` <CAKUFzr___Mc56XSu2nCuKbt11bAWdOdNo4y1LEZ47E5_TDxFGQ@mail.gmail.com>
2016-02-10 16:58     ` Rene Castberg
2016-02-11  4:52       ` Anand Jain
2016-04-18  8:59   ` Lionel Bouton
2016-04-18 14:11     ` Lionel Bouton
2016-04-19  7:35     ` Duncan
2016-04-19  9:13       ` Anand Jain [this message]
2016-04-19  9:45         ` Duncan
2016-04-19 10:49         ` Lionel Bouton

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=5715F6A0.7030707@oracle.com \
    --to=anand.jain@oracle.com \
    --cc=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.