All of lore.kernel.org
 help / color / mirror / Atom feed
From: William Uther <willu.mailingLists@cse.unsw.edu.au>
To: linux-btrfs@vger.kernel.org
Subject: Re: Can't remove missing drive
Date: Sat, 6 Nov 2010 18:11:20 +1100	[thread overview]
Message-ID: <BF9D8F2E-F027-4E86-8F87-A2E085DE71A1@cse.unsw.edu.au> (raw)
In-Reply-To: <8ADD7A79-8133-4D40-B842-EB5691104905@cse.unsw.edu.au>

Hi,

  I was trying to remove a 'missing' drive from a raid1 setup.  It was suggested on this list that I update to HEAD.  I updated my kernel to Ubuntu-lts-2.6.37-2.9, which appears to have the latest BTRFS code in it.  I then tried to remove my missing drive again:

root@willvo:~# btrfs filesystem show
failed to read /dev/sr0
Label: none  uuid: f929c413-01c8-443f-b4f2-86f36702f519
	Total devices 3 FS bytes used 594.71GB
	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 v0.19-36-gcbc979b-dirty
root@willvo:~# btrfs device delete missing /data
root@willvo:~# tail -1 /var/log/syslog
Nov  6 13:36:29 willvo kernel: [ 1227.711276] btrfs: no missing devices found to remove
root@willvo:~# btrfs filesystem show
failed to read /dev/sr0
Label: none  uuid: f929c413-01c8-443f-b4f2-86f36702f519
	Total devices 3 FS bytes used 594.71GB
	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 v0.19-36-gcbc979b-dirty

This is already strange as 'btrfs device delete' cannot find the missing device that 'btrfs filesystem show' knows about.  But then things get really strange...

root@willvo:~# btrfs filesystem df /data
Data, RAID0: total=1.18TB, used=596.74GB
System: total=4.00MB, used=96.00KB
Metadata, RAID0: total=2.00GB, used=993.35MB

Why is my filesystem suddenly showing RAID0?  Note that the used space displayed still seems to suggest raid 1.  Unfortunately I didn't notice the raid0 label right away, and did:

root@willvo:~# btrfs filesystem balance /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 594.71GB
	devid    1 size 931.51GB used 298.88GB path /dev/sdb1
	devid    2 size 931.51GB used 298.88GB path /dev/sdc1
	*** Some devices missing

Btrfs v0.19-36-gcbc979b-dirty
root@willvo:~# btrfs filesystem df /data
Data, RAID0: total=596.00GB, used=593.75GB
System: total=4.00MB, used=52.00KB
Metadata, RAID0: total=1.75GB, used=979.95MB

Which seems to have believed the spurious raid0 setting and converted my setup from raid1 to raid0 - albeit still with missing devices.

Is there any way to 'convert back' to raid1?  My reading suggests that feature isn't implemented yet - although I managed to magically convert from raid1 to raid0, so who knows.

Cheers,

Will      :-}


  reply	other threads:[~2010-11-06  7:11 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
2010-11-01  0:36   ` William Uther
2010-11-06  7:11     ` William Uther [this message]
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=BF9D8F2E-F027-4E86-8F87-A2E085DE71A1@cse.unsw.edu.au \
    --to=willu.mailinglists@cse.unsw.edu.au \
    --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 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.