Hello everyone, A quick note that Josef's ENOSPC work is now integrated in the master branch of the btrfs-unstable repo. There is still a small window in his accounting where ENOSPC oopsen can creep in, but the code is doing very well here and the worst case estimates he uses are conservative enough that I haven't been able to hit it yet. My plan is to push this out for 2.6.32-rc2 and fine tune any performance problems we find from there. Josef is continuing to improve the code so we'll have updates throughout the release cycle. Eric and Steve, if you could both feed this into your respective torture tests, it would be great. ENOSPC gotchas: btrfs-vol -b and device shrinking don't yet do all the checks required for proper enospc support. They do have some checks in place and most of the time they will be fine, but we need to add more. You probably won't hit 100% device utilization. Btrfs splits up the disk into metadata and data areas in relatively large chunks of about 1GB (sometimes more in multi-device setups). This means you can end up with some space dedicated to metadata that can't be used as data. -chris -- To unsubscribe from this list: send the line "unsubscribe linux-btrfs" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
