Hello, I have a fs with those free space parameters in a 3.6.6 arm system: from 'btrfs fi show': Total devices 1 FS bytes used 70.38GB devid 1 size 111.29GB used 93.14GB path /dev/sda1
from 'btrfs fi df /': Data: total=87.01GB, used=68.29GB Metadata, DUP: total=3.00GB, used=2.09GB And I get ENOSPC on unlink, ENOSPC on balance (-dusage=5 -musage=5 even), ENOSPC truncating files to size 0, ... The numbers show that there are ~18GB *unallocated*, isn't it? Why do I have any ENOSPC? In fact, although 'truncate' reports "couldn't truncate: ENOSPC", further 'ls -l' show the file became 0-bytes long. I could exit this deadlock situation thanks to 'btrfs fi defrag a_directory'. But I reach ENOSPC soon again. It would be very nice, if ENOSPC wrote a line in the kernel log stating the cause of ENOSPC. The kernel log, in this case, didn't report much other than "btrfs: 19 enospc during balance". Regards, Lluís. -- To unsubscribe from this list: send the line "unsubscribe linux-btrfs" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
