From: Stefan Behrens <sbehrens@giantdisaster.de>
To: Bartosz Kulicki <bartosz.kulicki@gmail.com>, linux-btrfs@vger.kernel.org
Subject: Re: Fwd: unable to delete files after kernel upgrade from 3.8.10 to 3.12
Date: Thu, 07 Nov 2013 09:49:33 +0100 [thread overview]
Message-ID: <527B541D.5000101@giantdisaster.de> (raw)
In-Reply-To: <CAMajw1O2xsqKK2VRcz1JjwaH0d9G_602snooNUpBhdDegt_yGA@mail.gmail.com>
On Wed, 6 Nov 2013 21:53:25 +0000, Bartosz Kulicki wrote:
> As per subject. Seems UUID tree creation failed after upgrade. I could
> not mount filesystem under 3.12. Going back to 3.8.10 allowed me to
> mount fs but I could no longer perform any deletes, writes etc.
>
> I've opened a bug report here.
> https://bugzilla.kernel.org/show_bug.cgi?id=64461
>
> I've included link to image captured with btrfs-image.
>
> Please CC me if further information is needed as I'm not subscribed to
> the mailing list.
>
ENOSPC means you're out of disk space. A copy-on-write filesystem needs
disk space for delete operations, that's not a bug.
What does 'btrfs fi df /mountpoint' say?
How much disk space do you have, how much is allocated?
And try the procedure that is described in the wiki:
https://btrfs.wiki.kernel.org/index.php/Problem_FAQ#I_get_.22No_space_left_on_device.22_errors.2C_but_df_says_I.27ve_got_lots_of_space
next prev parent reply other threads:[~2013-11-07 8:49 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CAMajw1N4bqFyHA4V8SkEzQFZF8adN0xQDShRq7bC2Of+nxsJGA@mail.gmail.com>
2013-11-06 21:53 ` Fwd: unable to delete files after kernel upgrade from 3.8.10 to 3.12 Bartosz Kulicki
2013-11-07 8:49 ` Stefan Behrens [this message]
2013-11-07 11:33 ` Bartosz Kulicki
2013-11-07 11:43 ` Bartosz Kulicki
2013-11-07 14:04 ` Duncan
2013-11-10 13:10 ` Russell Coker
2013-11-10 15:42 ` Duncan
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=527B541D.5000101@giantdisaster.de \
--to=sbehrens@giantdisaster.de \
--cc=bartosz.kulicki@gmail.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).