On Fri, Oct 29, 2010 at 11:55:49AM -0700, Erik Jensen wrote:
So, I ended up just applying the relevant commit to my existing source
tree, which did allow me to successfully remove the missing drive, so
I seem to be back up and running.
Thank you very much!
Fantastic, thanks for letting us
So, I ended up just applying the relevant commit to my existing source
tree, which did allow me to successfully remove the missing drive, so
I seem to be back up and running.
Thank you very much!
-- Erik
On Thu, Oct 28, 2010 at 1:57 PM, Chris Mason chris.ma...@oracle.com wrote:
On Tue, Oct
On Tue, Oct 19, 2010 at 07:17:16PM -0700, Erik Jensen wrote:
One of my drives on my six drive btrfs setup recently died. I
initially wasn't too worried about it, since both my data and metadata
are raid1. However, I have so far not been able to remove the missing
drive after several
On Wed, Oct 20, 2010 at 05:53:34PM -0700, Erik Jensen wrote:
After some more investigation, I discovered that for some reason btrfs
is trying to write to the missing drive (devid 5) in the course of
removing it from the array. Since this drive is missing, it is
naturally not writable, leading
One of my drives on my six drive btrfs setup recently died. I
initially wasn't too worried about it, since both my data and metadata
are raid1. However, I have so far not been able to remove the missing
drive after several attempts.
After discussing my problem on IRC, Chris Mason asked me to