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 -- To unsubscribe from this list: send the line "unsubscribe linux-btrfs" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
