From: Duncan <1i5t5.duncan@cox.net>
To: linux-btrfs@vger.kernel.org
Subject: Re: RAID5 Unable to remove Failing HD
Date: Tue, 19 Apr 2016 09:45:59 +0000 (UTC) [thread overview]
Message-ID: <pan$15255$6fcb2fe6$40daca28$6df14af1@cox.net> (raw)
In-Reply-To: 5715F6A0.7030707@oracle.com
Anand Jain posted on Tue, 19 Apr 2016 17:13:04 +0800 as excerpted:
>>> # 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.
Were the issues with btrfs delete missing fixed? There were some issues
with it actually trying to delete a device literally named "missing" or
something the like, and of course not finding it to delete, a kernel
cycle or two ago, and AFAIK delete by ID was originally proposed as a fix
for that. If I was reading the comments correctly, however, I think the
problem there was introduced with the switch to libblockdev or some such,
however, so he might be able to get around that by using older releases,
as long as the filesystem isn't using newer features that would block
that.
So delete missing may or may not work now, I've lost track. But he was
reluctant to unmount and reboot, and of course with btrfs not yet
offlining failed devices, it doesn't know it's actually missing, yet. So
even if delete missing does work for him, it's not going to work until a
reboot and remount degraded, and he was hoping to avoid that with the
delete by ID.
--
Duncan - List replies preferred. No HTML msgs.
"Every nonfree program has a lord, a master --
and if you use the program, he is your master." Richard Stallman
next prev parent reply other threads:[~2016-04-19 9:46 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
2016-04-19 9:45 ` Duncan [this message]
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='pan$15255$6fcb2fe6$40daca28$6df14af1@cox.net' \
--to=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 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).