From: Jon Nelson <jnelson@jamponi.net>
To: Josef Bacik <jbacik@fusionio.com>
Cc: linux-btrfs <linux-btrfs@vger.kernel.org>
Subject: Re: report: my btrfs filesystem failed hard today
Date: Wed, 17 Jul 2013 19:51:34 -0500 [thread overview]
Message-ID: <CAKuK5J2opbAWNmYsdSVkWAopyfPip8rypW7yKADEBCyqXb6Qxw@mail.gmail.com> (raw)
In-Reply-To: <20130717230401.GA2581@localhost.localdomain>
On Wed, Jul 17, 2013 at 6:04 PM, Josef Bacik <jbacik@fusionio.com> wrote:
> On Wed, Jul 17, 2013 at 05:44:23PM -0500, Jon Nelson wrote:
>> I had a btrfs filesystem under 3.9.8 that failed /hard/ today. So hard
>> that the filesystem could not be mounted because there wasn't enough
>> free space, unless it was mounted read only.
>>
>> This happened after I ran out of metadata space (is there a way to
>> increase the amount of metadata storage) while still having many gigs
>> free of data space, as reported by btrfs fi df. I tried balancing the
>> metadata, defrag'ing files (with -czlib) and even tried mounting with
>> -o remount,metadata_ratio={several values}, none of which worked, and
>> then it crashed hard.
>>
>> First, it killed systemd's logger (journald), which refused to
>> start.Following the crash, I was not able to mount the filesystem
>> without -o ro. -o recovery did not work.
>>
>
> Can you try btrfs-next, I did some work in this area in the last few months.
Unfortunately, I could not wait. I reaaaaly needed that system back
up, so I copied everything off, reformatted with ext4, and copied it
all back.
I (probably?) have more logs, though.
--
Jon
Software Blacksmith
prev parent reply other threads:[~2013-07-18 0:51 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-07-17 22:44 report: my btrfs filesystem failed hard today Jon Nelson
2013-07-17 23:04 ` Josef Bacik
2013-07-18 0:51 ` Jon Nelson [this message]
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=CAKuK5J2opbAWNmYsdSVkWAopyfPip8rypW7yKADEBCyqXb6Qxw@mail.gmail.com \
--to=jnelson@jamponi.net \
--cc=jbacik@fusionio.com \
--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).