Hallo, Evert, Du meintest am 05.12.10 zum Thema Re: 800 GByte free, but "no space left":
>>>>>> devid 2 size 1.35TB used 1.35TB path /dev/sdc3 >>>>>> devid 1 size 1.81TB used 1.35TB path /dev/sdf2 >>> Here devid 2 is at 100%, and hence you are getting the no more >>> space left errors. So, the 300 TB is on the bigger disk, and not >>> usable for you right now. >> I _think_ that a balance is all that's needed at this point. It >> can't hurt, anyway (other than taking quite a long time). > I am under the impression that as soon as one of the devices in a > btrfs is out of space, and write to that file system returns ENOSPACE > This certainly does look like it from this example, and from what I > have read elsewhere. Maybe - I don't know the code. But in my case "ENOSPACE" is returned too early. "btrfs-show" tells 2*1.35 TiByte used, but "no space left" is told when 2.4 TiByte are used (2.38 TiByte is ok). That's 300 GiByte too early (or about 10% too early). Or am I wrong in interpreting the messages? Viele Gruesse! Helmut -- 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
