On Thu, Jun 17, 2010 at 7:26 AM, John Wyzer <john.wy...@gmx.de> wrote: > On 17/06/10 00:45, Yan, Zheng wrote: >> On Thu, Jun 17, 2010 at 4:25 AM, John Wyzer <john.wy...@gmx.de> wrote: >>> btrfs: fail to dirty inode 6634 error -28 >>> [...] (nothing new coming, only error -28) >>> >>> Apart from that, I had messages that there was no space left on /, but >>> those were from userspace and not logged via netconsole. >>> >> >> looks like the fs runs out of metadata space. btrfs in 2.6.35 reserves >> more metadata space for system use than btrfs in 2.6.34. That's why >> these error message only appear on 2.6.35. > > Hmm. I've formatted with -m single because I wanted to avoid running out > of space for metadata. So if there's more then 10% of space left which > is about 40GB that seems like quite a bit of waste... ;-) > > I'll stay with 2.6.34 then for the time being. >
Spaces for data and metadata are separated even the FS was formatted with -m single. Yan, Zheng -- 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
