boli posted on Tue, 14 Jun 2016 21:28:57 +0200 as excerpted: > So I was back to a 4-drive raid1, with 3x 6 TB drives and 1x 8 TB drive > (though that 8 TB drive had very little data on it). Then I tried to > "remove" (without "-r" this time) the 6 TB drive with the least amount > of data on it (one had 4.0 TiB, where the other two had 5.45 TiB each). > This failed after a few minutes because of "no space left on device". > > Austin's mail reminded me to resize due to the larger disk, which I then > did, but that device still couldn't be removed, same error message. > I then consulted the wiki, which mentions that space for metadata might > be rather full (11.91 used of 12.66 GiB total here), and to try a > "balance" with a low "dusage" in such cases. > > For now I avoided that by removing one of the other two (rather full) 6 > TB drives at random, and this has been going on for the last 20 hours or > so. Thanks to running it in a screen I can check the progress this time > around, and it's doing its thing at ~41 MiB/s, or ~7 hours per TiB, on > average.
The ENOSPC errors are likely due to the fact that the raid1 allocator needs _two_ devices with free space. If your 6T devices get too full, even if the 8T device is nearly empty, you'll run into ENOSPC, because you have just one device with unallocated space and the raid1 allocator needs two. btrfs device usage should help diagnose this condition, with btrfs filesystem show also showing the individual device space allocation but not as much other information as usage will. If you run into this, you may just have to do the hardware yank and replace-missing thing again, yanking a 6T and replacing with an 8T. Don't forget the resize. That should leave you with two devices with free space and thus hopefully allow normal raid1 reallocation with a device remove again. -- Duncan - List replies preferred. No HTML msgs. "Every nonfree program has a lord, a master -- and if you use the program, he is your master." Richard Stallman -- 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
