From: Arie Peterson <ariep@xs4all.nl>
To: linux-btrfs@vger.kernel.org
Subject: Re: ENOSPC on file deletion with 3.1.6
Date: Tue, 03 Jan 2012 15:44:49 +0100 [thread overview]
Message-ID: <5456797.AlAK19QpzP@a4> (raw)
In-Reply-To: <20120103142258.GA22732@attic.humilis.net>
On Tuesday 03 January 2012 15:22:58 Sander wrote:
> Hm, not full.
>
> > OK, I'll keep this in mind. I'm a bit anxious to reboot, because I'm
> > afraid booting will fail if the root file system cannot be written to.
>
> But you did already reboot as you said the old kernel exposed the same
> behavior?
You are right; the full history of events was:
(- compile new kernel (3.1.6))
- boot new kernel;
- recompile gcc: problem occurs;
- solve problem by removing compilation directory;
- boot old kernel;
- recompile gcc: problem occurs for this kernel as well.
After trying to remove the problematic files for some time, I took the chance
and rebooted. After the reboot, the file system still gave ENOSPC on any write
operation. However, it was able to boot anyway, and now the removal of the
problematic files went much faster and without new ENOSPC. The compilation
directory was completely removed, and immediately afterwards, the file system
became writeable again.
Sander, thanks for your help.
I am still curious if this a known problem, and if upgrading to a newer kernel
might prevent it from reoccurring. (I was planning to wait for 3.2 to be
released and included in Gentoo's repository; maybe I shouldn't wait for
this...)
Kind regards,
Arie
next prev parent reply other threads:[~2012-01-03 14:44 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-03 13:49 ENOSPC on file deletion with 3.1.6 Arie Peterson
2012-01-03 14:06 ` Sander
2012-01-03 14:12 ` Arie Peterson
2012-01-03 14:22 ` Sander
2012-01-03 14:44 ` Arie Peterson [this message]
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=5456797.AlAK19QpzP@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).