From: Josef Bacik <josef@redhat.com>
To: Hugo Mills <hugo-lkml@carfax.org.uk>, linux-btrfs@vger.kernel.org
Subject: Re: ENOSPC at 94% full -- and causing BUGs elsewhere?
Date: Sat, 3 Oct 2009 17:55:32 -0400 [thread overview]
Message-ID: <20091003215531.GG4350@dhcp231-156.rdu.redhat.com> (raw)
In-Reply-To: <20091003122109.GB3116@selene>
On Sat, Oct 03, 2009 at 01:21:09PM +0100, Hugo Mills wrote:
> I've just had the following on my home server. I believe that it's
> btrfs that's responsible, as the machine wasn't doing much other than
> reading/writing on a btrfs filesystem. The process that was doing so
> is now stuck in D+ state, and can't be killed. The timing of the oops
> at the end is also suggestive of being involved in the same incident.
> This is the only btrfs filesystem on the machine.
>
Patches have gone to Linus to fix the enospc problems. You can try running the
enospc branch of Chris's git tree and it should behave better for you. Thanks,
Josef
next prev parent reply other threads:[~2009-10-03 21:55 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-10-03 12:21 ENOSPC at 94% full -- and causing BUGs elsewhere? Hugo Mills
2009-10-03 21:55 ` Josef Bacik [this message]
[not found] ` <20091004120630.GA19916@think>
2009-10-12 14:09 ` Hugo Mills
2009-10-13 10:31 ` Chris Mason
2009-10-13 14:50 ` Hugo Mills
2009-10-13 14:58 ` Yan, Zheng
2009-10-13 16:09 ` Hugo Mills
2009-10-13 23:19 ` 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=20091003215531.GG4350@dhcp231-156.rdu.redhat.com \
--to=josef@redhat.com \
--cc=hugo-lkml@carfax.org.uk \
--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