From: Brian Rogers <brian@xyzw.org>
To: William Uther <willu.mailingLists@cse.unsw.edu.au>
Cc: linux-btrfs@vger.kernel.org
Subject: Re: Can't remove missing drive
Date: Sat, 30 Oct 2010 22:55:57 -0700 [thread overview]
Message-ID: <4CCD04ED.1020009@xyzw.org> (raw)
In-Reply-To: <096423C3-E94C-4969-95C8-42557AA41D0D@cse.unsw.edu.au>
On 10/30/2010 12:37 AM, William Uther wrote:
> Hi,
> I have a raid1 setup with a missing device. I have added a new device and everything seems to be working fine, except I cannot remove the old, missing, device. There is no error - but the 'some devices missing' tag doesn't go away.
>
> root@willvo:~# btrfs filesystem show
> failed to read /dev/sr0
> Label: none uuid: f929c413-01c8-443f-b4f2-86f36702f519
> Total devices 3 FS bytes used 578.39GB
> devid 1 size 931.51GB used 604.00GB path /dev/sdb1
> devid 2 size 931.51GB used 604.00GB path /dev/sdc1
> *** Some devices missing
>
> Btrfs Btrfs v0.19
> root@willvo:~# btrfs device delete missing /data
> root@willvo:~# btrfs filesystem show
> failed to read /dev/sr0
> Label: none uuid: f929c413-01c8-443f-b4f2-86f36702f519
> Total devices 3 FS bytes used 578.39GB
> devid 1 size 931.51GB used 604.00GB path /dev/sdb1
> devid 2 size 931.51GB used 604.00GB path /dev/sdc1
> *** Some devices missing
>
> Btrfs Btrfs v0.19
The lack of a message on the delete operation indicates success. What
you see is the expected behavior, since 'btrfs filesystem show' is
reading the partitions directly. Therefore, it won't see any changes
that haven't been committed to disk yet. The 'some devices missing'
message should go away after running 'sync', or rebooting, or
un-mounting the file system.
next prev parent reply other threads:[~2010-10-31 5:55 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-10-30 7:37 Can't remove missing drive William Uther
2010-10-31 5:55 ` Brian Rogers [this message]
2010-11-01 0:36 ` William Uther
2010-11-06 7:11 ` William Uther
2010-10-31 12:01 ` Chris Mason
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=4CCD04ED.1020009@xyzw.org \
--to=brian@xyzw.org \
--cc=linux-btrfs@vger.kernel.org \
--cc=willu.mailingLists@cse.unsw.edu.au \
/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.