On Aug 31, 2013, at 4:12 AM, Steven Post <redalert.comman...@gmail.com> wrote: > > The system is running Debian Wheezy (kernel 3.2.0-4-amd64 #1 SMP Debian > 3.2.46-1 x86_64). > > Is this something known (and possibly resolved in a later version), or > should I open a bug report about it?
Try 3.10 or 3.11 before filing a bug on it. > Could it be that the device removal > was completed, but still shows as part of the array for some reason? Yes. It might take a few minutes after the chunks are reallocated for the device to be removed from the volume. I've had some cases where even a reboot was needed for the information in fi sh to refresh. > The reason for the remove is actually that I want to (gradually) replace > the 3TB drives with 1 TB ones, and somewhere in the middle move some of > the data of the array, to another machine, that currently has the 1 TB > drives which I intend to replace with the 3TB ones. Use a newer kernel for sure. What you suggest should work. If you're testing to see if it does work, and you're prepared for it not working (i.e. totally losing the entire file system) and prepared to find a consistent reproducer if it doesn't work, then have at it. Otherwise, create a whole new btrfs volume with recent kernel and btrfs-progs on the other machine; and then rsync everything from old to new. Rsync has a checksum option, it will take longer, but you can then be reasonably assured of file integrity. Chris Murphy-- To unsubscribe from this list: send the line "unsubscribe linux-btrfs" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
