linux-btrfs.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Paul Komkoff <i@stingr.net>
To: Roy Keene <btrfs@rkeene.org>
Cc: linux-btrfs@vger.kernel.org
Subject: Re: btrfs: unable to remove the only writeable device
Date: Mon, 13 Dec 2010 14:23:50 +0000	[thread overview]
Message-ID: <AANLkTim0ZU_b68dvYrEy2rWctUhVWLND1+9XZT76LCCt@mail.gmail.com> (raw)
In-Reply-To: <Pine.LNX.4.64.1009081954310.11139@claw.oc9.org>

Hello.

Sorry if it's already fixed, but with 2.6.35.6-48.fc14.x86_64, when I
do btrfs device delete /dev/blabla /btrfs kernel moves everything
except 1 gigabyte off the device, but then fails to remove it, saying
"btrfs: unable to remove the only writeable device" to dmesg.

What's even more interesting, it does that with all 3 of my devices,
and I clearly have enough free space to eject one drive.

What am I doing wrong?
Thanks.

P.S. For reference - what seems to be the same bug but from september.

On Thu, Sep 9, 2010 at 2:04 AM, Roy Keene <btrfs@rkeene.org> wrote:
> All,
>
> =A0 =A0 =A0 =A0I am using BtrFS at home for testing on my /home files=
ystem. =A0I
> started out with one disk (mkfs.btrfs /dev/sdb1) and then added anoth=
er disk
> (btrfs device add /dev/sda2 /home; btrfs filesystem balance /home).
>
> I then wanted to remove my second disk, but was unable to do so, I go=
t:
> =A0 =A0 =A0 =A0btrfs: unable to go below two devices on raid1
>
> I was told by the members of the BtrFS IRC channel that this was beca=
use my
> metadata was RAID1'd.
>
> To resolve this situation, I added an 8GB flash drive (my metadata wa=
s
> 5.99GB) and attempted to remove the drive again. =A0It ran for a whil=
e (a long
> while) and eventually returned me to the prompt. =A0It did not remove=
 the disk
> -- so I ran it again... and again... and again...
>
> I am to the point where "btrfs device delete <blah> /home" returns
> instantly, but has no effect. =A0The following is written to my kerne=
l message
> buffer whenever I try to remove ANY device from /home:
> =A0 =A0 =A0 =A0btrfs: unable to remove the only writeable device
>
> More information can be found in the attachement.
>
> I am still on my quest to remove a device from my BtrFS pool. =A0Does=
 anyone
> have any advice ?
>
> Thanks,
> =A0 =A0 =A0 =A0Roy Keene



--=20
This message represents the official view of the voices in my head
--
To unsubscribe from this list: send the line "unsubscribe linux-btrfs" =
in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

  reply	other threads:[~2010-12-13 14:23 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-09-09  1:04 btrfs: unable to remove the only writeable device Roy Keene
2010-12-13 14:23 ` Paul Komkoff [this message]
2010-12-14 19:24   ` Paul Komkoff

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=AANLkTim0ZU_b68dvYrEy2rWctUhVWLND1+9XZT76LCCt@mail.gmail.com \
    --to=i@stingr.net \
    --cc=btrfs@rkeene.org \
    --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).