Re: Can't remove missing drive

2010-11-06 Thread William Uther
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: r...@willvo:~# btrfs

Re: Can't remove missing drive

2010-10-31 Thread Chris Mason
On Sat, Oct 30, 2010 at 06:37:06PM +1100, 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

Re: Can't remove missing drive

2010-10-31 Thread William Uther
Thanks to Chris and Brian for the help! On 31/10/2010, at 11:01 PM, Chris Mason wrote: On Sat, Oct 30, 2010 at 06:37:06PM +1100, William Uther wrote: [snip - issues removing a missing drive - see below for new log] Is this actually a problem, or can I just keep running as is? It seems to

Can't remove missing drive

2010-10-30 Thread William Uther
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. r...@willvo:~# btrfs filesystem show failed to read

Re: Can't remove missing drive

2010-10-30 Thread Brian Rogers
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.

Can't remove missing drive (kernel BUG)

2010-10-17 Thread Erik Jensen
I have an six-drive array I use for television recordings (4 2TB and 2 1.5TB). Yesterday, I had one of the 1.5TBs die on me, so I did a mount -o degraded /dev/sdb /mnt/media followed by a btrfs-vol -r missing /mnt/media, but the latter command almost immediately generated a kernel BUG message,