From: Lionel Bouton <lionel-subscription@bouton.name>
To: Anand Jain <anand.jain@oracle.com>,
Rene Castberg <rene@castberg.org>,
linux-btrfs@vger.kernel.org
Subject: Re: RAID5 Unable to remove Failing HD
Date: Mon, 18 Apr 2016 10:59:35 +0200 [thread overview]
Message-ID: <5714A1F7.3050509@bouton.name> (raw)
In-Reply-To: <56BAFC15.6080106@oracle.com>
Hi,
Le 10/02/2016 10:00, Anand Jain a écrit :
>
>
> Rene,
>
> Thanks for the report. Fixes are in the following patch sets
>
> concern1:
> Btrfs to fail/offline a device for write/flush error:
> [PATCH 00/15] btrfs: Hot spare and Auto replace
>
> concern2:
> User should be able to delete a device when device has failed:
> [PATCH 0/7] Introduce device delete by devid
>
> If you were able to tryout these patches, pls lets know.
Just found out this thread after digging for a problem similar to mine.
I just got the same error when trying to delete a failed hard drive on a
RAID1 filesystem with a total of 4 devices.
# 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 ?
Currently the kernel is 4.1.15-r1 from Gentoo. I used btrfs-progs-4.3.1
(the Gentoo stable version) but it didn't support delete by devid so I
upgraded to btrfs-progs-4.5.1 which supports it but got the same
"inappropriate ioctl for device" error when I used the devid.
I don't have any drive available right now for replacing this one (so no
btrfs dev replace possible right now). The filesystem's data could fit
on only 2 of the 4 drives (in fact I just added 2 old drives that were
previously used with md and rebalanced, which is most probably what
triggered one of the new drives failure). So I can't use replace and
would prefer not to lose redundancy while waiting for new drives to get
there.
So the obvious thing to do in this circumstance is to delete the drive,
forcing the filesystem to create the missing replicas in the process and
only reboot if needed (no hotplug). Unfortunately I'm not sure of the
conditions where this is possible (which kernel version supports this if
any ?). If there is a minimum kernel version where device delete works,
can https://btrfs.wiki.kernel.org/index.php/Gotchas be updated ? I don't
have a wiki account yet but I'm willing to do it myself if I can get
reliable information.
I can reboot this system and I expect the current drive to appear
missing (it doesn't even respond to smartctl) and I suppose "device
delete missing" will work then. But should I/must I upgrade the kernel
to avoid this problem in the future and if yes which version(s)
support(s) failed device delete?
Best regards,
Lionel
next prev parent reply other threads:[~2016-04-18 8:59 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 [this message]
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
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=5714A1F7.3050509@bouton.name \
--to=lionel-subscription@bouton.name \
--cc=anand.jain@oracle.com \
--cc=linux-btrfs@vger.kernel.org \
--cc=rene@castberg.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.