Arie Peterson wrote (ao): > 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? Maybe your snapshots take up space. Can you show 'btrfs filesystem df /' ? FWIW, I also had a disk full just a few days ago. Removed all snapshots and some big files, but to no avail. Likely the background cleanup took too much time. A reboot fixed this. Sander -- Humilis IT Services and Solutions http://www.humilis.net -- 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
