From: Arie Peterson <ariep@xs4all.nl>
To: linux-btrfs@vger.kernel.org
Subject: ENOSPC on file deletion with 3.1.6
Date: Tue, 03 Jan 2012 14:49:07 +0100 [thread overview]
Message-ID: <24549767.TiRljH7Edl@a4> (raw)
Hi,
After upgrading my kernel from 2.6.38 (which has worked fine for months) to
3.1.6, I got ENOSPC on recompiling gcc (even though df says there is 16G free
of 50G; this is a raid1 setup, so in fact it's 8 of 25).
After this error, I tried to remove the compilation directory (with "rm -r"):
this also gives ENOSPC. I am trying to work around this by first truncating
files using "echo > $file", but this fails for some files, again with ENOSPC.
Also, removal of files is very slow even if it succeeds.
Moreover, any write operation on the file system now fails with ENOSPC.
Reverting to my old kernel does not help: it now shows the same problem.
Is this a known issue? Is there a way to make this file system unstuck? (I have
backups, but I'd like to preserve snapshot information if possible.) Should I
try upgrading to an even newer kernel?
Kind regards,
Arie
next reply other threads:[~2012-01-03 13:49 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-03 13:49 Arie Peterson [this message]
2012-01-03 14:06 ` ENOSPC on file deletion with 3.1.6 Sander
2012-01-03 14:12 ` Arie Peterson
2012-01-03 14:22 ` Sander
2012-01-03 14:44 ` Arie Peterson
2012-01-03 14:44 ` cwillu
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=24549767.TiRljH7Edl@a4 \
--to=ariep@xs4all.nl \
--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).