[...] > > Here the requested information of my fs (after removing a lot of build > > directories): > > > > franzbroetchen# uname -a > > Linux franzbroetchen 4.0.0-1-amd64 #1 SMP Debian 4.0.2-1 (2015-05-11) x86_64 GNU/Linux > > franzbroetchen# btrfs --version > > btrfs-progs v4.0 > > franzbroetchen# btrfs fi show > > Label: 'root' uuid: 57fe2100-0510-11e5-977e-0021ccb48233 > > Total devices 1 FS bytes used 182.55GiB > > devid 1 size 467.68GiB used 206.06GiB path /dev/mapper/franzbroetchen_vg-root > > Hmm. You shouldn't be seeing any kind of ENOSPC with this > allocation -- there's plenty of space for it to allocate from. I think > you've hit the horrible undiagnosed bug which prevents the FS from > allocating more space. I know josef was looking at this one but kept > getting distracted by data-corruption issues. He may be able to > comment more on it. > > Given the information above, I'm not sure that the usage=5 or > limit=3 suggestion I made above will have any benefit for you. No, I've tried this in the past without any success. I think I went up to usage=90 (without any limit) and it had no affect. I would guess that the problem is an allocation problem for the metadata because enough free space for allocation was available. -- 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
