On 4 August 2014 11:39, Hugo Mills <h...@carfax.org.uk> wrote: >> > * btrfs fi df >> > - look at metadata used vs total. If these are close to zero (on >> > 3.15+) or close to 512 MiB (on <3.15), then you are in danger of >> > ENOSPC. >> >> Hmm. It's unfortunate that this could indicate an amount of space >> which is free when it actually isn't. > > That's why the 512 MiB block reserve was split out of metadata -- > so that you don't look at metadata and say "oh, I've got half a gig > free, that's OK".
I don't quite follow this. Is it a recent development I missed? When was it "split out"? More recently than the software I'm using? Otherwise I'm having difficulty parsing this. -- 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
