Zygo Blaxell posted on Thu, 15 Oct 2015 00:39:27 -0400 as excerpted: > As others have pointed out, the raid0 allocator has a 2-disk-minimum > constraint, so any difference in size between the largest and > second-largest disk is unusable. In your case that's 73% of the raw > space. > > If the two smaller disks were almost full (no space unallocated in > 'btrfs fi usage') before you converted to raid0, then immediately after > starting a conversion to raid0 you have no space left _at all_. This is > because the space you previously had under some other data profile is no > longer considered "free" even if it isn't in use. All future > allocations must be raid0, starting immediately, but no space is > available for raid0 data chunks. > > This will cause some symptoms like huge write latency (it will not take > seconds or minutes, but *hours* to write anything to the disk) and > insanely high CPU usage.
Very nice analysis. The implications hadn't occurred to me, but you spell them out in the stark terms the reality of the situation dictates, along with offering a sane way out. Thanks. I'll have to keep this in mind for the next time something like this comes up. -- 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
