October 30, 201411 yr So i just removed a drive from the cache pool with hopes of adding it to the array, however, i took the array offline and unassigned the disk (it was disk1) then started the array back up. leaving the disk2 in place in hopes it will figure out i only have one cache disk.. Now in dmesg i'm seeing a bunch of this: BTRFS info (device sde1): found 930 extents BTRFS info (device sde1): found 930 extents BTRFS info (device sde1): relocating block group 161090633728 flags 17 BTRFS info (device sde1): found 1739 extents BTRFS info (device sde1): found 1739 extents BTRFS info (device sde1): relocating block group 160016891904 flags 17 BTRFS info (device sde1): found 5624 extents BTRFS info (device sde1): found 5624 extents BTRFS info (device sde1): relocating block group 158943150080 flags 17 BTRFS info (device sde1): found 7597 extents BTRFS info (device sde1): found 7597 extents BTRFS info (device sde1): relocating block group 157869408256 flags 17 Is this correct? The array hasn't mounted yet, i'm assuming it's still trying to figure out that i left a disk out? have i broken it?
October 30, 201411 yr Author For future reference - after some research it's expected behavior to balance out the renaming blocks? i think that's what it was doing anyway. So it ended up sticking to Cache2 - i stopped the array and moved it to cache1 - it all seems to work fine as expected. I'm not sure if this is hows it's supposed to be done - maybe there is a quicker way. Worked for me.
Archived
This topic is now archived and is closed to further replies.