From: John Wyzer <john.wyzer@gmx.de>
To: linux-btrfs@vger.kernel.org
Subject: Re: btrfsck segmentation fault + trace
Date: Thu, 17 Jun 2010 01:26:38 +0200 [thread overview]
Message-ID: <4C195DAE.6070503@gmx.de> (raw)
In-Reply-To: <AANLkTil8fnhT-ViGRV7BIyLIiKXyAjmayTeAiBWqn1Jc@mail.gmail.com>
On 17/06/10 00:45, Yan, Zheng wrote:
> On Thu, Jun 17, 2010 at 4:25 AM, John Wyzer <john.wyzer@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.
Thanks.
next prev parent reply other threads:[~2010-06-16 23:26 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-06-16 15:52 btrfsck segmentation fault + trace John Wyzer
2010-06-16 16:31 ` Chris Mason
2010-06-16 16:35 ` John Wyzer
2010-06-16 17:29 ` Chris Mason
2010-06-16 20:25 ` John Wyzer
2010-06-16 22:45 ` Yan, Zheng
2010-06-16 23:26 ` John Wyzer [this message]
2010-06-16 23:36 ` Yan, Zheng
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4C195DAE.6070503@gmx.de \
--to=john.wyzer@gmx.de \
--cc=linux-btrfs@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).