linux-btrfs.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Qu Wenruo <quwenruo.btrfs@gmx.com>
To: Alex Powell <alexj.powellalt@googlemail.com>,
	linux-btrfs@vger.kernel.org
Subject: Re: Unable to delete device
Date: Sun, 10 Nov 2019 11:41:59 +0800	[thread overview]
Message-ID: <d6037684-d478-493a-d428-83458dc52be6@gmx.com> (raw)
In-Reply-To: <CAKGv6CrZ6bpMFtWJ5grJ8tsuV1GehEP07QaAmyZWkhj-ixTchw@mail.gmail.com>


[-- Attachment #1.1: Type: text/plain, Size: 1024 bytes --]



On 2019/11/10 上午9:14, Alex Powell wrote:
> Hi all,
> I had a disk fail on my BTRFS RAID5 array. It is still mounting but
> there are bad sectors which will switch the array to read only mode
> when used.

Nope, regular sector shouldn't cause RO mount.

Dmesg please for the RO (transaction abort).

> 
> I used "btrfs device delete /dev/sdd /mnt/data" to remove it from the
> array. However it seems that it is only partially removing it from the
> array and when it gets to the bad sectors it fails.
> 
> localhost ~ # btrfs device delete /dev/sdd /mnt/data
> ERROR: error removing device '/dev/sdd': Input/output error

This is another different problem.
Dmesg please.

This can be caused by bad sector + failed to rebuild data.
Please keep in mind RAID5 of btrfs can't handle write hole yet, thus
it's not ensured to tolerant one corrupted disk.

Thanks,
Qu
> 
> What is best practice for removing the drive from the array in this situation?
> 
> Kind Regards,
> Alex Powell
> 


[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]

  reply	other threads:[~2019-11-10  3:42 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-11-10  1:14 Unable to delete device Alex Powell
2019-11-10  3:41 ` Qu Wenruo [this message]
2019-11-10  3:48 ` 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=d6037684-d478-493a-d428-83458dc52be6@gmx.com \
    --to=quwenruo.btrfs@gmx.com \
    --cc=alexj.powellalt@googlemail.com \
    --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).